SMS, Text & WhatsApp Templates with Merge Fields in Salesforce
Your lettings team sends the same “your viewing is confirmed for Saturday 11am” message 47 times a week. When one negotiator types it slightly wrong, three tenants show up on Sunday. Templates with Salesforce merge fields remove the typos and keep the voice consistent.
Why templates beat freehand typing
Your team types the same five or six message shapes over and over. “Thanks for your enquiry” and a booking link. “Your documents have been received” and a next-step note. “Your appointment tomorrow” and a confirmation. Freehand every time, each rep types it slightly differently, some drop words, some forget the link.
Your templates lock the shape, make the voice consistent, and pull personal details from the Salesforce record. Your rep picks the template, adjusts if needed, and sends. The risk of a messy or missing message drops to nearly zero.
How merge fields personalise at send time
Your template contains placeholders, {!Contact.FirstName}, {!Opportunity.Name}, {!Case.Subject}, {!Account.Name}. When the message sends, Salesforce replaces each placeholder with the live value from the record. Your template library holds one version. Every send comes out personalised.
Your lettings template reads “Hi {!Contact.FirstName}, your viewing at {!Property__c.Address__c} is confirmed for {!Viewing__c.Date_Time__c}”. Every tenant receives their own address and their own time, every negotiator sends the same clean phrasing.
Channel-specific template handling
Your SMS, text and WhatsApp each have their own formatting rules. Standard SMS has a character limit. WhatsApp requires pre-approved business-initiated templates under Meta’s rules. Your template library handles all three:
- SMS and text templates, free-form, length-aware, merge-field-enabled
- WhatsApp templates, tagged with the WhatsApp Business API template ID once approved, with the placeholder mapping Meta expects
- Channel-agnostic templates, same message, any channel, your rep picks the channel at send time
Your complexity of WhatsApp’s template rules stays behind the scenes. Your rep sees a clean template name and a personalised preview. The approval status shows at a glance.
Template governance for larger teams
Your a 40-person team, you don’t want every rep creating their own templates. You want marketing or ops to own the library and reps to use the approved ones. Template permissions sit in standard Salesforce, who can create, edit, approve, and publish templates is controlled by Permission Set.
Your marketing team owns the voice. Your ops team owns the compliance-critical wording. Your sales team uses what’s been approved. The library stays clean and on-brand.
Templates inside Agentforce AI agent replies
Your Agentforce AI agent uses templates too. When it replies to an inbound SMS, text or WhatsApp, it can pull from the same template library your reps use, with merge fields filled from the Salesforce record. Your AI stays on-brand, on-voice, and inside your approved wording.
Your Agentforce AI agent doesn’t freestyle. It speaks from your library. That’s why the output reads consistent across thousands of conversations, one source of truth for every outbound message, whether the sender is human or AI.