Instead of typing a person’s name, appointment time, account phone number, invoice total, or booking details manually, you can insert a merge field. When the message sends or the document is generated, Kyrios replaces the merge field with the matching value from the related contact, user, account, appointment, invoice, or booking record.
For example, a message that says:
Hi {{contact.first_name}}, your appointment is scheduled for {{appointment.start_time}}.
may send as:
Hi Taylor, your appointment is scheduled for Wed, Nov 5, 2025 3:30 PM.
Merge fields help keep your communication consistent, accurate, and easier to manage across Kyrios.
When to Use Merge Fields
Use merge fields when you want Kyrios to automatically insert saved information into a message, page, document, invoice, or workflow.
Common uses include:
Greeting a contact by first name
Adding appointment dates and times to confirmation messages
Inserting account details into standard templates
Adding assigned user contact information
Including invoice totals or payment links
Personalizing follow-up messages
Referencing service booking details
Tracking attribution details from lead sources
How Merge Fields Work
Each merge field uses a shortcode wrapped in double curly brackets.
Example: {{contact.first_name}}
When the message or document is created, Kyrios looks for the matching saved value and replaces the shortcode with that information.
If the field has a saved value, the value appears in the final message. If the field is empty, the merge field may appear as a blank space unless a fallback value is used.
Where Merge Fields Can Be Used
Merge fields may be available in several areas of Kyrios, depending on the tool, record type, and context.
They are commonly used in:
Emails
SMS messages
Workflow messages
Campaigns
Appointment confirmations
Calendar reminders
Invoices
Receipts
Documents
Forms
Funnels
Service booking messages
Course-related messages
Available merge fields can vary based on the feature you are using. For the most accurate option, use the merge field picker inside the editor whenever possible.
Important Note About Context
Merge fields only work when Kyrios has access to the record connected to that field.
For example:
Contact fields need a contact record.
Appointment fields need an appointment record.
Invoice fields need an invoice record.
Service booking fields need a service booking record.
User fields need an assigned or sending user.
If a merge field does not populate, the message may not have been sent from the correct context, or the related record may not contain that information.
Note About Raw Phone Format
Some phone merge fields include a raw format option. Raw phone fields remove spaces, parentheses, and dashes.
Example:
Standard phone format: (512) 555-0148
Raw phone format: +15125550148
Raw phone format is helpful when using phone numbers in links, tracking parameters, integrations, or international formats.
Merge Field Shortcode List
Use the tables below to find standard merge field shortcodes by category.
Contact Merge Fields
Name | Merge Field | Example |
Full name |
| Taylor Morgan |
First name |
| Taylor |
Last name |
| Morgan |
| ||
Phone |
| (512) 555-0148 |
Phone (raw format) |
| +15125550148 |
Company name |
| Morgan Home Services |
Full address |
| 1842 Cedar Bend Dr, Austin, TX 78704 |
Address line 1 |
| 1842 Cedar Bend Dr |
City |
| Austin |
State/Region |
| Texas |
Postal code |
| 78704 |
Time zone |
| GMT-06:00 America/Chicago |
Date of birth |
| Feb 14, 1985 |
Source |
| Website form |
Website |
| |
Contact ID |
| C8mR4pLq92TnX7VbK3sA |
User Merge Fields
Name | Merge Field | Example |
Full name |
| Jordan Lee |
First name |
| Jordan |
Last name |
| Lee |
| ||
Phone |
| (512) 555-0199 |
Phone (raw format) |
| +15125550199 |
Email signature |
| Jordan Lee[email protected](512) 555-0199 |
Booking link |
| |
Appointment user phone (raw) |
| +15125550199 |
External calling number |
| (512) 555-0167 |
External calling number (raw) |
| +15125550167 |
Appointment Merge Fields
Name | Merge Field | Example |
Title |
| Consultation with Taylor |
Start date/time |
| Wed, Nov 5, 2025 3:30 PM |
Start date only |
| Nov 5, 2025 |
Start time only |
| 3:30 PM |
End date/time |
| Wed, Nov 5, 2025 4:00 PM |
End date only |
| Nov 5, 2025 |
End time only |
| 4:00 PM |
Day of week |
| Wednesday |
Month number |
| 11 |
Time zone |
| CST |
Cancellation link |
| |
Reschedule link |
| |
Meeting location |
| 1842 Cedar Bend Dr, Austin, TX 78704 |
Notes |
| Please bring the project estimate. |
Add to calendar link |
| |
Google Calendar link |
| |
iCal/ICS link |
| |
Recurring repeats |
| 0 |
Recurring times to repeat |
| 1 |
Assigned user name |
| Jordan Lee |
Assigned user email |
| |
Assigned user phone |
| (512) 555-0199 |
Assigned user phone (raw) |
| +15125550199 |
Assigned user signature |
| Jordan Lee[email protected](512) 555-0199 |
Calendar Merge Fields
Name | Merge Field | Example |
Calendar name |
| Service Consultation Calendar |
Campaign Merge Fields
Name | Merge Field | Example |
Event date/time |
| Nov 5, 2025 3:30 PM |
Event date |
| Nov 5, 2025 |
Event time |
| 3:30 PM |
Message Merge Fields
Name | Merge Field | Example |
Message body |
| Hi Taylor, this is a reminder about your consultation tomorrow. |
Message subject |
| Consultation Reminder |
Account Merge Fields
Name | Merge Field | Example |
Account name |
| Brightside Home Services |
Full address |
| 2400 Lakeview Rd, Austin, TX 78703 |
Address line 1 |
| 2400 Lakeview Rd |
City |
| Austin |
State/Region |
| Texas |
Country |
| US |
Postal code |
| 78703 |
| ||
Phone |
| (512) 555-0123 |
Phone (raw format) |
| +15125550123 |
Website |
| |
Logo URL |
| |
Owner first name |
| Riley |
Owner last name |
| Carter |
Owner email |
| |
Account ID |
| L9xP2rQm74VnB6ZdT8kH |
Right Now Merge Fields
Name | Merge Field | Example |
Second |
| 9 |
Minute |
| 10 |
Hour (24h) |
| 14 |
Hour (AM/PM) |
| 2 |
AM/PM |
| PM |
Day of week |
| Tuesday |
Month name |
| November |
Day |
| 4 |
Month (number) |
| 11 |
Year |
| 2025 |
Date (MM/DD/YYYY) |
| 11/04/2025 |
Date (DD/MM/YYYY) |
| 04/11/2025 |
First Attribution Merge Fields
Name | Merge Field | Example |
Session source |
| Direct traffic |
Landing URL |
| |
Campaign |
| spring_service_campaign |
UTM source |
| newsletter |
UTM medium |
| |
UTM content |
| service_cta |
Referrer |
| |
Campaign ID |
| 48290173561028492 |
Ad click ID |
| CLICK123ABC |
UTM keyword |
| home_service_quote |
UTM match type |
| phrase |
Ad group ID |
| 735190 |
Ad ID |
| 86420 |
Latest Attribution Merge Fields
Name | Merge Field | Example |
Session source |
| Referral |
Landing URL |
| |
Campaign |
| fall_maintenance_campaign |
UTM source |
| partner |
UTM medium |
| referral |
UTM content |
| booking_button |
Referrer |
| |
Campaign ID |
| 59281746038291573 |
Ad click ID |
| CLICK789XYZ |
UTM campaign |
| fall_checkup |
UTM keyword |
| maintenance_plan |
UTM match type |
| broad |
Ad group ID |
| 246810 |
Ad ID |
| 97531 |
Invoice Merge Fields
Name | Merge Field | Example |
Invoice name |
| Service Visit |
Invoice number |
| 10482 |
Issue date |
| 2025-04-05 |
Due date |
| 2025-04-19 |
Subtotal |
| $500.00 |
Discount amount |
| $50.00 |
Tax amount |
| $25.00 |
Total amount |
| $475.00 |
Invoice title |
| Service Visit Invoice |
Invoice link |
|
Invoice Company Details
Name | Merge Field | Example |
Company name |
| Brightside Home Services |
Company phone |
| (512) 555-0123 |
Company address |
| 2400 Lakeview Rd |
Company city |
| Austin |
Company state |
| Texas |
Company country |
| US |
Company website |
| |
Company logo URL |
|
Invoice Customer Details
Name | Merge Field | Example |
Customer name |
| Taylor Morgan |
Customer first name |
| Taylor |
Customer last name |
| Morgan |
Customer phone |
| (512) 555-0148 |
Customer email |
| |
Customer company |
| Morgan Home Services |
Customer address |
| 1842 Cedar Bend Dr |
Customer city |
| Austin |
Customer state |
| Texas |
Customer postal code |
| 78704 |
Invoice Sender Details
Name | Merge Field | Example |
Sender name |
| Jordan Lee |
Sender email |
|
Invoice Card Information
Name | Merge Field | Example |
Card brand |
| Visa |
Card last 4 |
| 1234 |
Course Merge Fields
Name | Merge Field | Example |
Category title |
| Getting Started |
Product title |
| Home Service Basics |
Post title |
| Preparing for Your First Service Call |
Service Booking Merge Fields
Name | Merge Field | Example |
Title |
| Maintenance Consultation |
Start time |
| 3:30 PM |
End time |
| 4:30 PM |
Start date |
| March 6, 2026 |
End date |
| March 6, 2026 |
End time only |
| 4:30 PM |
Day of week |
| Friday |
Month (number) |
| 3 |
Month name |
| March |
Time zone |
| CST |
Total price |
| $125 |
Meeting location |
| 2400 Lakeview Rd, Austin, TX 78703 |
Meeting location name |
| Consultation Room 2 |
Reschedule link |
| |
Cancellation link |
|
Service Line Items and Assigned User
Name | Merge Field | Example |
Service name |
| Maintenance Plan Review |
Service price |
| $125 |
Service duration |
| 45 mins |
Service start date |
| March 6, 2026 |
Service start time |
| 3:30 PM |
Service time zone |
| GMT-06:00 America/Chicago |
Addon name |
| Priority Scheduling |
Addon price |
| $25 |
Addon duration |
| 15 mins |
Addon quantity |
| 1 |
Assigned user name |
| Jordan Lee |
Assigned user email |
| |
Assigned user phone |
| (512) 555-0199 |
Assigned user phone (raw) |
| +15125550199 |
Assigned user signature |
| Jordan Lee[email protected](512) 555-0199 |
Default or Fallback Values for Empty Fields
Some merge fields may be blank if the saved data is missing from the related record.
For example, if a contact does not have a first name saved, this message: Hi {{contact.first_name}},
may display as: Hi ,
Fallback values help prevent awkward blank spaces by giving Kyrios an alternate value to use when the original field is empty.
For example, a fallback could allow the message to say: Hi there, instead of leaving the name blank.
Fallback values can usually be set by selecting the merge field inside the editor and adding the fallback value where available.
Best Practices for Using Merge Fields
Before sending a message or publishing a template, check that the merge fields fit the context.
Use these best practices:
Use the merge field picker when possible instead of typing shortcodes manually.
Preview or test messages before sending them to real contacts.
Use fallback values for important fields like first name.
Avoid placing required meaning inside a field that may be empty.
Keep sentence structure natural if a field does not populate.
Use raw phone fields only when the phone number needs to be passed into a link, parameter, or technical format.
Check that appointment, invoice, booking, or course fields are only used where those records exist.
Example of a Good Merge Field Message
This message uses contact, appointment, user, and account merge fields:
Hi {{contact.first_name}}, this is a reminder that your appointment with {{user.name}} is scheduled for {{appointment.start_time}}. If you need help, you can contact us at {{location.phone}}.
When sent, Kyrios replaces each merge field with the correct saved value.
What to Check If a Merge Field Does Not Populate
If a merge field does not show the expected value, check the following:
Make sure the related record contains the information.
Confirm the message is being sent from the correct context.
Check that the merge field was inserted correctly.
Use the merge field picker to confirm the shortcode is available.
Test the message using a record that has the needed information saved.
For example, an invoice merge field will not populate correctly if the message is not connected to an invoice. An appointment merge field needs an appointment record. A contact field needs a contact record.
Frequently Asked Questions
What happens if a merge field has no value?
If the related field is empty, the merge field may be replaced with a blank space. This can make a message look unfinished. Use fallback values where available to keep the message readable.
What is the difference between a standard phone field and a raw phone field?
A standard phone field is formatted for people to read. A raw phone field removes spaces, parentheses, and dashes so it can be used in links, tracking parameters, integrations, or international formats.
Can I use merge fields in automated workflows?
Yes. Merge fields are often used in workflow emails, SMS messages, reminders, internal notifications, and follow-up sequences.
Can merge fields be used in invoices and payment messages?
Yes. Invoice merge fields can insert invoice numbers, issue dates, due dates, totals, customer details, sender details, and invoice links when the message is connected to an invoice.
Why do I see different merge fields than another account?
Available merge fields may vary based on your account setup, enabled tools, integrations, and the type of editor or record you are using.
How do I avoid blank greetings?
Use a fallback value when available. You can also write your greeting in a way that still reads naturally if the first name is missing.
For example: Hi there,
is safer than:
Hi {{contact.first_name}},
when the first name may not always be saved.
Need Help?
If merge fields are not populating as expected, first confirm that the related record contains the information you want to insert.
Then check that the message, workflow, invoice, appointment, or booking is using the right context.
If you still need help, use the in-app support options available in your account. Include the merge field shortcode, where you are using it, and an example of the output you are seeing.
