Skip to main content
Design the subject/body your users see in unread-message emails. No sounds apply to email. Providers like SendGrid can consume these fields—map them into Dynamic Template variables or assemble the subject/body in your service before sending.

What to customize

  • Subjects and bodies for 1:1 and group emails (default vs privacy-friendly).
  • Preview content from messages[] (unread list) and senderDetails/groupDetails.
  • Deep links back to the conversation (add in your provider template).

Payload shapes

Field meanings:
  • to: recipient identifiers and optional email.
  • messages[]: the unread messages that triggered the notification (use for counts and previews).
  • senderDetails: most recent sender; map to subjects or hero text.
  • groupDetails: only present for group conversations.
  • subject: ready-to-use subject if you do not build it in the provider.

One-on-one

Group

Subject examples

You can use the provided subject field or build your own using senderDetails.name and groupDetails.name. Here are default and privacy-focused subject templates:

Tips

  • Keep privacy variants generic to avoid leaking message content.
  • Use messages[0].message for a short preview; use the length for unread counts.
  • If you use SendGrid Dynamic Templates, map the payload into dynamic_template_data (subject, recipient name, sender name, unread count, preview, and the messages array).