Skip to content

Messaging ​

The messaging area sends SMS to policyholders: onboarding notes, premium reminders, trigger watches, and payout alerts. It has three parts: Broadcasts, Templates, and SMS providers.

Broadcasts ​

The home of messaging, the history of SMS campaigns, and where you compose a new one.

The list shows each broadcast's audience, a preview of the message, its category, its status (draft, queued, sending, completed, or cancelled), and its sent and failed counts. You can search and filter by status and category. Below it, a message log shows per-recipient delivery across the whole project.

Compose a broadcast ​

  1. Start from a template (optional): pick one and it fills the message body and category.
  2. Pick an audience: all policyholders, a single area, or a mobile-money provider. A live count shows how many policyholders match.
  3. Write the message: the editor shows the character count and the number of SMS segments, and lets you insert merge fields (like {name}, {phone}, {uai}, {provider}) as chips that personalise each message.
  4. Preview: the platform renders sample messages for a few real recipients and warns you about any merge fields that won't fill (so nothing sends as raw {...} text).
  5. Send to the matched policyholders.

Delivery tracking: each broadcast shows queued, sent, and failed counts, and the per-recipient message log records each message's status (pending, processing, sent, or failed) with a resend action for failures.

TIP

You can also send to one person from their policyholder record, the same composer opens, pinned to that individual.

Templates ​

Reusable message bodies that speed up composing and back operational messages. Each template has a name, a short code, a category (onboarding, premium, trigger, payout, reminder, or general), a scope (this project only, or global), and an active flag.

Templates use the same merge fields: {name}, {phone}, {uai}, {sum_insured}, {premium}, {amount} (a payout amount), {provider}, and {season}. Some fields only fill when the message carries that context, for example {amount} fills on a payout message but not on a plain broadcast.

NOTE

Template editing is still being finalised: the templates screen and its editor exist and you can browse templates, but saving a new or edited template may error until the backend support lands.

SMS providers ​

The outbound SMS account the project actually sends through. You configure one or more providers from the available gateway types; each needs a label, a country, and its credentials (kept secret). One provider is the active default, used for all broadcasts and alerts.

NOTE

Until a provider is configured, sends fall back to a server default account. Configure the project's own provider before relying on messaging in production.

How messaging connects ​

  • Policyholders are the audience: target everyone, an area, or a provider, or one person from their record.
  • Payout and trigger alerts carry context (a payout amount, a season), so the context-gated merge fields fill in. These messages are generated when the event happens and appear in the same message log.