SMS messages have stricter length and data requirements than email messages. Review these limits before composing an SMS campaign so that personalization, URLs, and encoding do not create unexpected segments or delivery failures.
| Requirement | Details |
|---|---|
| Sender | A Treasure AI-provisioned short code assigned to the workspace |
| Recipient phone number | A phone number in E.164 format, such as +12125551234 |
| GSM-7 message | Up to 160 characters per segment |
| Unicode message | Up to 70 characters per segment |
| Long message | Uses multiple SMS segments; review the segment count because each segment adds delivery cost |
| Personalization | Liquid variables must reference mapped audience columns |
| URL | Use an HTTPS URL for Treasure AI link shortening |
GSM-7 messages support up to 160 characters per segment. A message containing characters outside the GSM-7 character set, including many emojis, can use Unicode encoding and support up to 70 characters per segment.
Engage Studio displays the segment count while you compose the message. Check the count again after adding Liquid values, UTM parameters, or links because rendered values can change the final message length.
For link-specific limits, see Shorten Links in SMS Campaigns.
Use Liquid to insert profile attributes at send time. For example:
Hi {{ profile.first_name }}, your offer is ready.Every variable in the message must have a corresponding output mapping. A message that references profile.first_name therefore requires a first_name mapping.
Map the following values in the campaign activation:
phone_numberis required for delivery and must contain a phone number in E.164 format.- Additional columns are required for each Liquid variable used in the message.
- Use the same column names in the mapping and the Liquid expression.
If a variable is not mapped, the rendered message may be incomplete or the activation may fail. See Create an SMS Campaign for the activation steps.