WhatsApp Business API for insurance brokers in Kenya: shared inbox, M-Pesa reminders and consent

For a Kenyan insurance brokerage, the WhatsApp Business API is what turns advisers' phones into one shared, recorded channel, and ORIS is the layer that makes the API usable day to day: a shared inbox, premium reminders with the M-Pesa reference the insurer expects, renewals on Meta-approved templates, and consent kept the way the Data Protection Act 2019 requires, without taking payments or issuing policies.

WhatsApp Business app or API: what changes for a Kenyan brokerage

The WhatsApp Business app runs on one phone and suits a sole adviser. The WhatsApp Business Platform, which most people call the API, is the version built for teams: the brokerage's number lives in the cloud, several handlers answer from it through software such as ORIS, and every message is stored per client rather than on someone's handset.

The API comes with Meta's rules. When a client messages you, a 24-hour customer service window opens, and inside it handlers can reply freely. Outside that window the brokerage can only reach clients with templates approved by Meta. Each template has a category: utility when it relates to the client's existing policy or request, marketing when it promotes something; Meta recategorises a utility template that contains promotional content as marketing. Meta charges per message according to its own price list; the app vs API comparison sets out the trade-offs.

ORIS connects the brokerage's number to the Platform through Meta's Embedded Signup, then handles templates, the window indicator, opt-in and opt-out per client, and the queue that sends approved messages.

What a Kenyan brokerage needs once it is on the API

In many Kenyan brokerages the client relationship already runs on WhatsApp: quotes requested by voice note, logbooks and IDs sent as photos, motor certificates and medical cover documents returned as PDFs, premium reminders followed by an M-Pesa confirmation message pasted back into the chat. The weak points are familiar: conversations live on advisers' personal phones, reminders depend on someone remembering, and nobody can show later what the client was told or whether they agreed to receive offers.

A CRM worth having fixes those three things before anything else. It puts conversations on the brokerage's number and in a shared inbox, it starts reminders from policy dates rather than memory, and it keeps consent, messages and replies attached to the client. Generic sales CRMs with a WhatsApp add-on rarely handle Meta's template rules, the 24-hour window or per-client opt-in well; our comparison generic CRM vs WhatsApp CRM sets out the criteria.

The rules that shape a CRM in Kenya

The insurance regulator. Brokers and agents are licensed by the Insurance Regulatory Authority, which supervises intermediaries under the Insurance Act. The Kenya country profile summarises the framework, including the premium payment rules that make reminders a compliance task.

Commercial use of personal data. Section 37 of the Data Protection Act 2019 provides that a person shall not use personal data for commercial purposes unless they have sought and obtained express consent from the data subject, or are authorised to do so under a written law and informed the data subject of that use when collecting the data. For a brokerage, that draws a clear line: a reminder about the client's own policy serves the contract; a message promoting a new product is commercial use and needs express consent. Our article on M-Pesa, IRA rules and premium reminders shows what a reminder may contain.

Automation and AI. When software classifies replies or drafts answers, the brokerage should know which decisions remain human. ORIS keeps an adviser in the loop: negative replies are never answered automatically. We discuss the ODPC angle in AI in a Kenyan brokerage: automated decisions and the ODPC.

WhatsApp's policy. Meta only allows businesses to message people who gave opt-in permission, requires every opt-out to be respected, and expects a clear path to a human when automation replies.

How a Kenyan brokerage uses ORIS

The brokerage's number in a shared inbox. The WhatsApp number is connected through Meta's Embedded Signup. All handlers see the conversations, each attached to the client record, and the history stays with the brokerage when someone leaves.

Opt-in collected at the source. ORIS generates sign-up links and QR codes for each channel: the office counter, a business card, the website, an email footer. The client opens WhatsApp and sends the first message; their record is created with the source of their opt-in.

Reminders from policy dates. Clients and policies are imported by CSV with policy type, status, renewal date and premium. Lifecycle triggers prepare renewal reminders a set number of days ahead; one-off reminders go out as a Quick Campaign. The template carries the policy reference and the payment details the insurer uses; payment happens on M-Pesa or by bank, outside ORIS.

Replies that get handled. The AI classifies each incoming message (opportunity, re-engagement, neutral or high churn risk) and reads its sentiment and urgency. Clients at risk rise in Opportunities & Risks with a notification to the adviser, and reply drafts are suggested for a person to approve.

What ORIS does and does not do for a Kenyan brokerage

The table below sets common needs against what ORIS covers and what stays with the insurer, your management system or your payment channel.

A working day with ORIS

1. Morning. Handlers open the shared inbox; overnight messages are classified and attached to each client record, and clients asking about a claim or a payment are answered first.
2. This week's renewals. Renewal triggers prepare reminders for policies entering the window, each with the policy reference and the payment details the insurer uses.
3. A new client at the counter. A walk-in client scans the opt-in QR code; their record is created with the source of consent and the handler requests documents in the same chat.
4. Clients at risk. An adviser reviews Opportunities & Risks, calls the clients who said they might cancel and notes the outcome on their record.
5. Week end. Campaign results and opportunities are exported as CSV and reconciled with M-Pesa and bank collections in the brokerage's own system.

What ORIS does not do

• Take M-Pesa, card or bank payments, or send payment links.
• Issue policies, motor certificates or endorsements, or collect e-signatures.
• Send SMS or email, or place calls.
• Connect out of the box to a named management system or insurer portal: CSV import and export in standard, connection scoped per project.
• Answer negative messages automatically: those always become drafts for an adviser.

Frequently asked questions

Do we need express consent to remind a client about their premium on WhatsApp?

WhatsApp requires opt-in before a business messages anyone. Under section 37 of the Data Protection Act 2019, express consent is the condition for commercial use of personal data, such as promoting a new product; a reminder about the client's own policy serves the contract. Keep the two kinds of message separate.

Can ORIS confirm that a client has paid by M-Pesa?

No. ORIS has no payment connection. The client often sends the M-Pesa confirmation in the chat, which stays in the history, but the payment is confirmed in your own system or with the insurer.

Can messages be sent in Swahili?

Yes. Swahili is on Meta's list of supported template languages, so reminders can be written and approved in Swahili as well as English. Only the ORIS interface, used by your team, is in English.

Does ORIS work with the WhatsApp Business app on our office phone?

ORIS uses the WhatsApp Business Platform (Meta's API), not the app. The number is connected through Embedded Signup; our app vs API comparison explains what changes for the brokerage.