Prerequisites
- Create an SMS Template — Tags are inserted while writing
Smart Tags for SMS
The picker offers more than SMS substitutes. This is the list that works.
A smart tag is a placeholder such as {contacts.fname} that is replaced with a real value when the message is sent.
The tag list in the editor is shared with other parts of Zyntro and offers tags from eleven groups. SMS substitutes only a subset of them. A tag that is not substituted is left exactly as written, so the recipient receives the braces and the tag name as literal text. Nothing warns you, which makes this the most common cause of an embarrassing SMS.
Use the list below rather than the picker.
Tags that are substituted in SMS
| Tag | Replaced with |
|---|---|
| {contacts.fname} | The contact's first name |
| {contacts.lname} | The contact's last name |
| {contacts.name} | First and last name together |
| {contacts.email} | The contact's primary email address |
| {contacts.phone} | The contact's primary phone number |
| {contact.fname} | The contact's first name (singular form) |
| {contact.lname} | The contact's last name (singular form) |
| {contact.name} | First and last name together (singular form) |
| {contact.email} | Primary email (singular form) |
| {contact.phone} | Primary phone (singular form) |
| {contact.city} | The contact's city |
| {contact.country} | The contact's country |
| {members.fname} | The sending team member's first name |
| {members.name} | The sending team member's full name |
| {member.fname} | The sending team member's first name |
| {member.name} | The sending team member's full name |
| {member.email} | The sending team member's email address |
Warning: Note the singular and plural forms. {contacts.email} and {contact.email} both work, but for the team member only {member.email} is substituted — the plural {members.email} offered by the picker is not replaced in an SMS and will arrive as literal text.
Groups in the picker that SMS does not substitute
Organizations
— Including {organizations.name}. Type your business name into the message instead.
Entities
— Company and entity fields are not available to SMS substitution.
Contact custom fields
— Only the standard contact fields in the table above are substituted. Custom fields are not, however they appear in the picker.
Member job title, role, department, signature
— Only the member name and email tags listed above work.
Schedules and appointments
— Appointment details must be passed in by whatever triggers the message, not pulled by a tag.
Webinars and registrations
— Listed in the picker because the same list serves email.
Testimonials, Offers, Pages, Posts
— These need a specific record chosen, which SMS substitution does not do.
Important: Substitution also depends on how the message is sent. A template used by a form action, a workflow or webinar registration has its tags replaced. A template chosen manually in Send SMS to Contact is pasted into the message box exactly as written — including the tags — and you are expected to edit them before sending. Always read the box before you send.
Where substitution happens
| Sent from | Tags replaced? |
|---|---|
| Form actions | Yes — contact and member tags from the table above |
| Workflows and automated sends | Yes — same set |
| Webinar registration settings | Yes — same set |
| Send SMS to Contact (manual) | No — the raw template text is placed in the box for you to edit |
Tip: Test before relying on a tag. Send the template to yourself from the same place it will really be sent from — a tag that works in a form action is not proof it works in a manual send.
