What to customize
- Body text for 1:1 and group SMS (default vs privacy-friendly).
- Preview and counts from
messages[]plussenderDetails/groupDetails. - Link back to your app (add in your template).
Payload shapes
Field meanings:to: recipient identifier and phone number.messages[]: unread messages that triggered the SMS; use for counts and previews.senderDetails: most recent sender; helpful for subject-style copy.groupDetails: present for group conversations.smsContent: an optional, ready-to-send string if you want to use it directly.
One-on-one
Group
Template examples
You can use the providedsmsContent field or build your own using senderDetails, groupDetails, and messages.length. Here are default and privacy-focused templates:

| Use case | Default template | Privacy template | Example result (default) |
|---|---|---|---|
| One-on-one notification | You’ve received {{messages.length}} message(s) from {{senderDetails.name}}! Read them at https://your-website.com. | You’ve received {{messages.length}} message(s) from {{senderDetails.name}}! Read them at https://your-website.com. | You’ve received 2 message(s) from Susan Marie! Read them at https://your-website.com. |
| Group notification | You’ve received {{messages.length}} message(s) in {{groupDetails.name}}! Read them at https://your-website.com. | You’ve received {{messages.length}} message(s) in {{groupDetails.name}}! Read them at https://your-website.com. | You’ve received 2 message(s) in Hiking Group! Read them at https://your-website.com. |
Tips
- Keep bodies short to respect SMS length/carrier rules; consider removing URLs in privacy mode.
- Use
messages.lengthfor counts andsenderDetails.name/groupDetails.namefor context. - Add your app link in the template; ensure it is trackable and domain-verified per provider.