Variables & Personalisation
Personalise every message with the contact's name, company, and more.
Variables let you personalise messages automatically. Instead of "Hi Customer", your contact gets "Hi Rahul Ji" — pulled from their contact record.
Named variables
Use double curly braces with the field name:
| Variable | Inserts |
|---|---|
{{name}} | Contact's full name |
{{address_as}} | How you greet them (e.g. "Rahul Ji") — set per contact |
{{company}} | Their company name |
{{phone}} | Their phone number |
With a fallback:
If the contact has no name, it becomes "Hi there" instead of "Hi ". Always add a fallback for safety.
{{address_as}} does NOT fall back to {{name}} automatically. Set a fallback explicitly: {{address_as|there}}.
Custom field variables
Any custom field you've defined for your workspace can also be used as a variable — just use its field_key (not its display label):
If a contact has no value set for that field, the placeholder is left blank — same as a named variable with no fallback. Add a fallback the same way: {{bni_date|TBD}}.
Setting the value via the API: when sending a template through POST /api/v1/templates/:id/send, you can pass the custom field's value directly in the same request instead of requiring it to already be on the contact:
This merges into the contact's existing custom fields — other custom fields already set on the contact are left untouched.
Positional variables (Business WhatsApp)
Business WhatsApp templates use numbered placeholders:
When sending, you map each number to a contact field or fixed value.
Spintax — message variations
Add variety to avoid repetition. SalesByte picks one option randomly per contact:
Each contact gets a slightly different version. Useful for large campaigns.
Preview before sending
The template editor shows a live preview on the right with sample values filled in. In a campaign, click Preview message to see exactly what a specific contact will receive.