Step 1 · Template manager
Create the template
Name it, set Use on to an object such as Contact, or to any record for a quick reply, and add a category and description so people can find it.
Templates
Write a message once, insert Salesforce fields from a picker, add fallbacks for empty values and preview it with a real record. Your team inserts it in a click from a record, the inbox or an outreach.
What are ConnectSMS templates? Reusable text messages kept in one org-wide library in Salesforce. They use merge fields such as {!Contact.FirstName|there}, which are filled in from the record when the message is sent, with a fallback for empty values. Campaign managers and admins maintain the library, and everyone with ConnectSMS User can use the active templates.
Tip: Add a fallback after a vertical bar to use when a field is empty, for example
{!Contact.Name|there}. Without a fallback, an empty field blocks sending.
All merge fields were filled.
Recreated from the ConnectSMS interface with sample data.
How it works
Step 1 · Template manager
Name it, set Use on to an object such as Contact, or to any record for a quick reply, and add a category and description so people can find it.
Step 2 · Template manager
Insert fields from the picker, add fallbacks, watch the segment meter, and preview the result with a sample record before making it active.
Step 3 · Everyone
Choose Use template in the composer on a record or in the inbox, or start an outreach message from it. Merge fields are filled in when the message is sent.
Fallbacks
Pick a record to see what the recipient would receive. A fallback fills an empty field; a field with no fallback blocks the send instead of leaving a gap.
{!Contact.FirstName|there}{!Contact.Appointment_Date__c} shows as 10/12/2026 for English (United States)All merge fields were filled.
Recreated from the ConnectSMS interface with sample data.
Merge-field picker
Choose Insert field and pick from the fields you can read on the template's object, its related records one lookup away, and the sending user and your organization.
| You write | What the recipient gets |
|---|---|
{!Contact.FirstName} | A field on the record the message is sent from |
{!Case.Contact.FirstName} | A field one lookup away, such as the Contact on a Case |
{!$User.FirstName} | The sending user's first name, last name, full name, email, title or phone |
{!$Organization.Name} | Your company name from Salesforce |
{!Contact.FirstName|there} | The first name, or "there" when the field is empty |
Contact
Sending user
Organization
Recreated from the ConnectSMS interface with sample data.
Checked before it's saved
The editor measures the message as you type and tests it against a real record, so mistakes are caught by the template manager instead of by customers.
This text contains characters (such as emoji or accented letters) that switch the message to Unicode, so each segment holds 70 characters instead of 160.
Recreated from the ConnectSMS interface with sample data.
One library
Templates live on the Templates tab. There are no personal copies to drift out of date: everyone works from the same list.
Recreated from the ConnectSMS interface with sample data.
In daily use
Templates show up where people write messages, with your recently used ones at the top.
Recently used
Other templates
Recreated from the ConnectSMS interface with sample data.
Permissions
ConnectSMS User
Finds and inserts active templates and quick replies on records and in the inbox.
ConnectSMS Campaign Manager
Creates, edits, duplicates, activates, deactivates and deletes templates, and uses them in outreach.
ConnectSMS Admin
Has every template permission, alongside numbers, access, policies and operations.
FAQ
Salesforce-style merge fields with the object name first, such as {!Contact.FirstName}, one lookup such as {!Case.Contact.FirstName}, and sending-user and company fields such as {!$User.FirstName} and {!$Organization.Name}. Add a fallback after a vertical bar, as in {!Contact.FirstName|there}. A field without its object, such as {!FirstName}, isn't supported.
If the merge field has a fallback, the fallback is used. If it doesn't, ConnectSMS names the field and blocks the send until the record is filled in or the template gets a fallback, so a message never goes out with a gap in it.
People with the ConnectSMS Campaign Manager or ConnectSMS Admin permission set create, edit, duplicate, activate, deactivate and delete templates. Everyone with ConnectSMS User can find and use the active ones.
A template whose Use on setting is Any record (quick reply). It can be inserted on any record or conversation, so it can only use the sending user's and the organization's fields, such as {!$User.FirstName} and {!$Organization.Name}.
In the Salesforce locale of the person sending. A date field such as {!Contact.Appointment_Date__c} shows as 10/12/2026 for a user with the English (United States) locale.
Yes. The Message step of an outreach can start from a template, and the Send Text Message action in Flow accepts the ID of an active template and fills in its merge fields from the record.
Send, preview and schedule messages from Contacts, Leads, Accounts and Cases.
Send one template to a report, a Salesforce Campaign or filtered records.
Why one emoji can double the cost of a text, and how to avoid it.
Try it now: every feature, free for 14 days
Install ConnectSMS from AgentExchange, connect your Twilio account and give your team the numbers they should text from.
ConnectSMS is published by WorkBridge Solutions. Twilio bills your Twilio account directly for messaging, including during the trial.