Dynamic fields

Dynamic fields help personalize the messages by applying values from the matching fields in the data source for each record.

For example, you can use the message text like below.

When the above message is sent, {{BUSINESS_NAME}}, {{CUSTOMER_NAME}}, {{appointment_date}}, {{appointment_time}}, and {{location}} get replaced with applicable values for each recipient.

Predefined fields

Below fields are prefilled, and you can always use them in your message text.

• {{BUSINESS_NAME}} - Your business name.
• {{CUSTOMER_NAME}} - Name of the recipient.
• {{PHONE_NUMBER}} - Phone number of the recipient starting with the country dial code (e.g., 16317471111).
• {{SENDER_NAME}} - Name of the person sending the bulk messages.

Fields from your data source

You can use column headers from your CSV/Excel or extra fields from your contact as dynamic fields.

CSV/Excel

When sending bulk messages using a CSV or an Excel file, you can use the column header as the dynamic field within the message text.

For example, if you have a CSV or Excel like below,

You can use FirstName column header from the file as a dynamic field like this Hello {{FirstName}}. Nice to see you today.... When the message is sent to the first record in the file, it is sent as Hello Charles. Nice to see you today....

Contact list

When sending bulk messages using a contact list, you can use the extra field as the dynamic field within the message text.

For example, if you have a contact list like below,

You can use email_address extra field as a dynamic field like this Hello {{CUSTOMER_NAME}}. We tried to get in touch with you on this email address {{email_address}} .... When the message is sent to the first record in the file, it is sent as Hello Charles Clark. We tried to get in touch with you on this email address charles@example.com ....

Advanced handling

You can do more with the dynamic fields than just replacing the values from your data source. We have created a few helper functions which you can use along with the dynamic fields to get more out of the dynamic fields.

Date formatting

Convert the date into a different format of your choice.

• Function name: dateFormat
• Usage: {{#dateFormat "Format-string"}}{{your-dynamic-date-field}}{{/dateFormat}}

Example

• "appointment_date" value in your data source is "2023-06-15",
• You would like to add it in the message as "Thursday, June 31, 2023",
• You can do so by using dateFormat like this {{#dateFormat "dddd, mmmm d, yyyy"}}{{appointment_date}}{{/dateFormat}}.

Format-string options

Value | Description ---|--- d | Day of the month as digits; no leading zero for single-digit days. dd | Day of the month as digits; leading zero for single-digit days. ddd | Day of the week as a three-letter abbreviation. DDD | "Ysd" (for Yesterday), "Tdy" (for Today) or "Tmw" (for Tomorrow), if date lies within these three days. Else fall back to ddd. dddd | Day of the week as its full name. DDDD | "Yesterday", "Today" or "Tomorrow" if date lies within these three days. Else fall back to dddd. m | Month as digits; no leading zero for single-digit months. mm | Month as digits; leading zero for single-digit months. mmm | Month as a three-letter abbreviation. mmmm | Month as its full name. yy | Year as last two digits; leading zero for years less than 10. yyyy | Year represented by four digits. h | Hours; no leading zero for single-digit hours (12-hour clock). hh | Hours; leading zero for single-digit hours (12-hour clock). H | Hours; no leading zero for single-digit hours (24-hour clock). HH | Hours; leading zero for single-digit hours (24-hour clock). M | Minutes; no leading zero for single-digit minutes. MM | Minutes; leading zero for single-digit minutes. N | ISO 8601 numeric representation of the day of the week. o | GMT/UTC timezone offset, e.g. -0500 or +0230. p | GMT/UTC timezone offset, e.g. -05:00 or +02:30. s | Seconds; no leading zero for single-digit seconds. ss | Seconds; leading zero for single-digit seconds. S | The date's ordinal suffix (st, nd, rd, or th). Works well with d. l | Milliseconds; gives 3 digits. L | Milliseconds; gives 2 digits. t | Lowercase, single-character time marker string: a or p. tt | Lowercase, two-character time marker string: am or pm. T | Uppercase, single-character time marker string: A or P. TT | Uppercase, two-character time marker string: AM or PM. W | ISO 8601 week number of the year, e.g. 4, 42 WW | ISO 8601 week number of the year, leading zero for single-digit, e.g. 04, 42 Z | US timezone abbreviation, e.g. EST or MDT. For non-US timezones, the GMT/UTC offset is returned, e.g. GMT-0500

Content based on condition

Add content based on specified condition.

• Function name: ifeq
• Usage: {{#ifeq "value-to-compare" dynamic-field}}content{{else ifeq "different-value-to-compare" dynamic-field}}different-content{{else}}another-content{{/ifeq}}

Example 1

• "location_code" value in your data source can be "LOC1", or "LOC2",
• You would like to add the content for "LOC1" as "Deer Park Location", and for "LOC2" as "Dix Hills Location",
• You can do so by using ifeq like this {{#ifeq "LOC1" location_code}}Deer Park Location{{else}}Dix Hills Location{{/ifeq}}.

Example 2

• "location_code" value in your data source can be "LOC1", "LOC2", or "LOC3",
• You would like to add the content for "LOC1" as "Deer Park Location", for "LOC2" as "Dix Hills Location", and for "LOC3" as "Brentwood Location",
• You can do so by using ifeq like this {{#ifeq "LOC1" location_code}}Deer Park Location{{else ifeq "LOC2" location_code}}Dix Hills Location{{else}}Brentwood Location{{/ifeq}}.

Same conditional content for multiple values

There are times when you would like to add same content for multiple values of the dynamic field. You can either repeat "ifeq" and "else ifeq" as mentioned above, or use a different function available just for that purpose.

• Function name: contains used with arr
• Usage: {{#contains (arr "value1-to-compare" "value2-to-compare" "value3-to-compare" ...) dynamic-field}}content{{else}}different-content{{/contains}}

Example 1

• "location_code" value in your data source can be "LOC1", "LOC2" or "LOC3",
• You would like to add the content for "LOC1" & "LOC2" as "Deer Park Location", and for "LOC3" as "Dix Hills Location",
• You can do so by using contains like this {{#contains (arr "LOC1" "LOC2") location_code}}Deer Park Location{{else}}Dix Hills Location{{/contains}}.