Merge Tags Reference (Complete List by Channel)

Remindax uses hash-style merge tags — #field_name#, not curly braces. The variables you can use differ by channel — email has the fullest list, SMS supports a narrower set, and WhatsApp uses its own (with some abbreviated names like #doc_type# instead of #document_type#). Type tags manually — there's no click-to-insert picker in the template editor.

Syntax

The Remindax merge tag syntax is:

#field_name#

Examples:

#title#
#exp_date#
#contact_first_name#
#cf.policy number#

Hash signs (#) wrap the field name on both sides. Curly braces ({{}}), square brackets ([[]]), and percent signs (%) do NOT work in Remindax — only #.

The template editor shows a Template Variables table for reference. There's no click-to-insert variable picker — you type tags manually. Care with spelling matters (see "Unsupported tags" below).

Email template variables (complete list)

Variable	Inserts
`#title#`	Reminder title
`#document_type#`	Document Type label
`#folder_name#`	Folder name
`#contact_first_name#`	First name of the recipient
`#contact_last_name#`	Last name of the recipient
`#company#`	Company name
`#department#`	Department name
`#exp_date#`	Expiration date
`#due_date#`	Due date
`#start_date_time#`	Start date and time (Appointment/Event)
`#end_date_time#`	End date and time (Appointment/Event)
`#location#`	Location field
`#notes#`	Notes field
`#attachments#`	Attached files list
`#custom_fields#`	ALL custom field values, formatted as a list
`#cf.field_name#`	One specific custom field (case-insensitive name match)

Vehicle-specific variables (when the reminder is linked to a vehicle)

Variable	Inserts
`#vehicle.license_plate#`	License plate
`#vehicle.vin#`	VIN
`#vehicle.make#`	Vehicle make
`#vehicle.model#`	Vehicle model
`#vehicle.year#`	Vehicle year
`#vehicle.assigned_driver#`	Assigned driver
`#vehicle.department#`	Vehicle's department

SMS template variables (smaller list)

SMS templates support a narrower set than email. Contact name, company, department, custom fields are NOT available in SMS — only the fields below.

Variable	Inserts
`#title#`	Reminder title
`#document_type#`	Document Type label
`#folder_name#`	Folder name
`#exp_date#`	Expiration date
`#due_date#`	Due date
`#start_date_time#`	Start date and time
`#end_date_time#`	End date and time
`#location#`	Location field
`#notes#`	Notes field

Vehicle variables also work in SMS templates where supported.

If you need to convey a custom field value to SMS recipients, put it in the Notes field on the reminder — Notes IS available in SMS via #notes#.

WhatsApp template variables (different names)

WhatsApp templates use abbreviated names that don't match the email naming. This is by design — WhatsApp templates are Meta-approved with fixed placeholder names.

Variable	Inserts
`#title#`	Reminder title
`#doc_type#`	Document Type (note: NOT `#document_type#`)
`#exp_date#`	Expiration date
`#start_date_time#`	Start date and time
`#notes#`	Notes field
`#attachments#`	Attached files list
`#cust_fields#`	Custom fields (note: NOT `#custom_fields#`)

WhatsApp templates are read-only and pre-approved — you can't add new merge tags to WhatsApp templates. The variables above are what's available; the chatbot/AI must use exactly these names for WhatsApp content.

Custom fields

For email templates only:

#custom_fields# — inserts ALL custom fields on the item, formatted as a list
#cf.field_name# — inserts one specific custom field. The name match is case-insensitive (#cf.Department# and #cf.department# both work).

Custom fields are NOT supported in SMS templates via the #cf.field_name# syntax. Workaround: put the value in the Notes field.

For WhatsApp, the equivalent is #cust_fields# (NOT #custom_fields#) — and it's controlled by the pre-approved WhatsApp template, not freely editable.

What happens when a tag has no value

Most fields: the tag renders as blank/empty string.
WhatsApp #notes# when the reminder has no notes: may render as the literal word none.

This is the difference between "the field exists but is empty" and "the field doesn't exist at all" — see below.

Unsupported tags stay visible (critical to understand)

If you type a tag that Remindax doesn't recognise — typically a typo or wrong format — the tag remains as-is in the final message.

Examples of what goes wrong:

What you type	What happens
`#title#`	Replaced with the reminder title ✓
`#contact_first_name#`	Replaced with first name ✓
`{{title}}`	NOT replaced — appears literally as `{{title}}`
`#contact_firstname#`	NOT replaced — typo, no underscore. Appears as `#contact_firstname#`
`#contact.first_name#`	NOT replaced — wrong format. Appears as `#contact.first_name#`
`#policynumber#` for a custom field	NOT replaced — should be `#cf.policy_number#` or `#cf.Policy Number#`. Appears as `#policynumber#`

This means tag typos go straight to recipients. Test templates carefully — sample-send (via Send Test Email) shows you the raw tags, but a real send to a real reminder shows whether your tags are correct (or visible as bugs).

Recommended workflow when building templates

Open the Template Variables reference table in the template editor as a checklist.
Type the exact tag from the table — don't guess at the name.
For custom fields, use exactly #cf.field_name# (with the underscore-separated or space-separated name matching the custom field's label).
Send a test (Send Test Email) — confirms layout and that you didn't typo.
For final verification, manually send to a real reminder and inspect the received email — Send Test Email doesn't merge real data, so tags appear raw in the test. A real send is the only way to verify merge worked.

Edge cases & gotchas

Syntax is #field#, not {{field}} or anything else.
Available variables differ by channel. Email has the most; SMS has fewer; WhatsApp uses abbreviated names.
WhatsApp uses #doc_type# (not #document_type#) and #cust_fields# (not #custom_fields#).
Unsupported tags appear literally in messages. Test carefully.
No click-to-insert picker — type tags manually.
No SMS support for custom fields via #cf.name#. Workaround: put values in Notes.
Case-insensitive matching for custom field names — #cf.Department# and #cf.department# both work.
WhatsApp templates themselves are read-only. You can't add new merge tags to a WhatsApp template — only the pre-approved variables are usable.