Instance · CMS
SMS Introduction
Last updated 1 November 2026
The text message templates your site sends, kept in the CMS with a recipient and a short body.
The CMS keeps the text messages your site sends, such as a booking reminder or a delivery notice. Each SMS is a template with a recipient and a short body. Your code or a form sends it, filling in the details for each message.
Where to find SMS templates
In the admin, open CMS and choose SMS. The docs.insites.io instance had no SMS templates on 1 November 2026.
What an SMS template holds
| Field | Meaning |
|---|---|
| To | The recipient phone number. Can use Liquid, such as a number from a form |
| From | The sender: a number, a short code or a name |
| Body | Plain text, with Liquid for details such as a name or a reference |
Example template
app/smses/order_shipped.liquid
---
to: '{{ data.phone }}'
---
Your order {{ data.order_id }} has been shipped. Track it at {{ data.tracking_url }}Keep messages short. A message over 160 characters is split into several messages, and each part is charged.
Note
The example follows the Insites Logic Engine email and SMS reference. It was not sent, because sending is a write.
Check which SMS templates exist
A developer can list the templates on an instance with a read-only query:
Query
{
admin_sms_notifications(per_page: 3) {
total_entries
results { name }
}
}Response on the docs instance
{
"data": {
"admin_sms_notifications": {
"total_entries": 0,
"results": []
}
}
}Templates you add live in app/smses/. Insites modules keep theirs inside the module and send them from module code.
Common mistakes
- Writing HTML in the body. SMS is plain text.
- A phone number without the country code. Store numbers in full international form.
- Long messages built from Liquid. A long name or address can push the text over 160 characters.