Approvals and content screening

Who approves what, what approvers see, and how the hate-speech screen works.

When a send needs approval#

A send waits for approval when any of these apply:

• it exceeds your organisation's recipient or cost threshold (Settings › Organization);
• it exceeds the sender's role recipient cap;
• the content screen flags it for compliance review (see below).

Sends that use a manager's pre-approved template, where only the merge fields vary, can skip the per-send approval.

Approving a send#

Open Messaging › Approvals. Each waiting send shows:

• who requested it and when;
• the recipient count and estimated cost;
• content screen categories, if any;
• up to five masked previews with parts.

Write a decision reason, then Approve or Reject. You cannot approve your own send: a different person with approval permission must release it. Recent decisions are listed below the queue.

The content screen#

Every outgoing message is checked against a curated lexicon of hate speech, incitement and ethnic slurs in English, Kiswahili, major local languages and Sheng, maintained by the Sauti compliance team. This supports compliance with the National Cohesion and Integration Act.

• A hit blocks the send and routes it to Sauti's compliance review. Your organisation cannot override it.
• The compliance team may also use an AI classifier as a second opinion. Its result is advisory; a person always decides.
• If a send is held, you will see the reason. Reword the message and submit a new send, or wait for the compliance decision.

Important: The content screen is a safety net, not a substitute for judgement. Read every message before you approve it.