Insurance broker software in South Africa: adding WhatsApp next to your broker management system

Most South African brokerages already run broker management software for policies and commission; what it rarely does well is the WhatsApp conversation with clients, and the records the FAIS Act and POPIA expect from it. ORIS is a WhatsApp CRM built for brokerages in Southern Africa that sits next to your broker management system: a shared inbox on the brokerage's number, campaigns on Meta-approved templates, lapse-risk tracking and an audit log, with CSV files linking the two.

Broker management system, CRM or WhatsApp CRM?

Searching for insurance broker software in South Africa usually means one of three things. Most brokerages already run a broker management system (BMS): client and policy records, insurer statements, commission reconciliation, sometimes a client portal. Many also use a generic CRM for leads and pipeline. What neither does well is the day-to-day WhatsApp conversation with clients: several handlers on one number, templates approved by Meta for messages outside the 24-hour window, opt-in and opt-out per client, a record of who said what.

That is what a WhatsApp CRM like ORIS covers. It does not replace your BMS; it sits next to it. Clients and policies come in by CSV (or a connection scoped during the project), conversations and campaigns happen in ORIS, and clients, opportunities and campaign results go back out by CSV. Our comparison generic CRM vs WhatsApp CRM for brokers sets out when each category is the right choice.

The compliance frame a South African CRM has to respect

FAIS record-keeping. Section 18 of the Financial Advisory and Intermediary Services Act requires an authorised financial services provider, unless exempted, to maintain records for a minimum of five years regarding known premature cancellations of transactions or products by clients, complaints received and whether they were resolved, and continued compliance by the FSP and its representatives. A WhatsApp conversation in which a client says they want to cancel, or complains, belongs to those records. Advisers' personal phones do not keep them for the FSP; a shared, exportable history does. We go further in FAIS record-keeping for WhatsApp conversations.

POPIA and direct marketing. Section 69 of the Protection of Personal Information Act prohibits processing personal information for direct marketing by any form of electronic communication unless the data subject has consented or is a customer of the responsible party. The customer route only covers the brokerage's own similar products or services, with contact details obtained in the context of a sale, and a reasonable, free opportunity to object both when the details were collected and in each marketing message. Every marketing message must identify the sender and give a contact for opting out. Our guide to POPIA's eight conditions for brokers covers the rest of the Act.

Meta's rules. WhatsApp's Business Messaging Policy only allows a business to contact people who gave opt-in permission, requires every opt-out request to be respected, and asks for clear escalation paths to a person when automation answers within the 24-hour window. A CRM that runs campaigns on WhatsApp has to apply all three.

How a South African brokerage uses ORIS day to day

One number, one inbox. The brokerage's WhatsApp number is connected through Meta's Embedded Signup; every handler works the same inbox, each conversation is attached to the client record, and the history stays with the brokerage when an adviser leaves. Setting up the account is covered in WhatsApp Business setup for a South African brokerage.

A book segmented for WhatsApp. Clients and policies are imported by CSV: policy type (life, health, motor, home, travel, business), status, renewal date, premium. Segments filter on risk score, engagement score, WhatsApp opt-in and days since inception; see how to segment a South African book for renewals.

Campaigns that respect consent. Campaigns are tagged service or marketing, use Meta-approved templates, go only to opted-in clients, and check consent again at the moment of sending. STOP, typed or tapped, removes the client from queued messages and running journeys. Opt-in links and QR codes let clients sign up from your website, email footer or office.

Lapse risk on one screen. The AI classifies every incoming reply; signs that a client may cancel raise their risk score and create an attrition-risk opportunity in Opportunities & Risks, with a notification to the adviser. Drafts are suggested; auto-reply follows your rules and never answers a negative message on its own.

What ORIS covers, and what stays in your other systems

The table below maps what a South African brokerage typically needs against what ORIS does and what remains in the broker management system, with the insurer or with the debit order provider.

Which brokerages ORIS suits

ORIS fits a personal-lines, funeral or SME brokerage of roughly 3 to 50 people whose clients already message advisers on WhatsApp, and whose problems are the ones above: personal phones, renewals and failed debit orders chased by hand, no consent register, replies lost between colleagues. It fits less well a commercial-lines broker whose renewals are negotiated by email and meetings, or a firm whose urgent need is commission reconciliation, which belongs in a BMS.

Before a demo, read the South Africa country profile for the regulators and payment habits, and the use cases for failed debit orders and renewals, which show the journeys ORIS runs.

A working day with ORIS

1. Start of day. Handlers open the shared inbox: overnight replies are classified, clients asking for a call or signalling cancellation are flagged, and each conversation sits on the client's record.
2. Unpaid debit orders. The unpaid report is imported as CSV and a Quick Campaign sends the approved utility template with the policy reference to opted-in clients only.
3. Renewals. Lifecycle triggers prepare renewal reminders for policies entering the chosen window; client replies that ask for changes feed cover-review opportunities for an adviser.
4. At-risk clients. An adviser works the Opportunities & Risks list by highest risk, calls the clients who need a conversation and records the outcome on the client.
5. Month end. Clients, opportunities and campaign performance are exported as CSV and reconciled in the BMS with collections, lapses and complaints.

What ORIS does not do

• Run debit orders, collect premiums or send payment links.
• Issue policies, endorsements or certificates, or collect e-signatures.
• Send SMS or email, or make phone calls: ORIS works on WhatsApp only.
• Connect out of the box to a named broker management system or insurer portal: CSV in standard, connection scoped per project.
• Give financial advice: AI drafts never promise cover or price, and advice stays with your representatives.

Frequently asked questions

Is ORIS a broker management system?

No. ORIS is a WhatsApp CRM: conversations, consent, campaigns, opportunities and lapse risk. Policies, commission and insurer statements stay in your broker management system, with CSV files moving data between the two.

Does ORIS help with FAIS record-keeping?

It keeps the WhatsApp side of the record: every conversation per client, consent and opt-outs, and an audit log, all exportable as CSV. Your FSP remains responsible for its overall records and for keeping them at least five years as section 18 requires.

Can we send marketing messages to existing clients without new consent?

POPIA section 69 allows marketing of your own similar products to existing customers if they could object when their details were collected and can opt out in every message. WhatsApp separately requires opt-in to receive messages from your business. ORIS tags each campaign as service or marketing and applies opt-outs automatically.

Where is client data hosted?

ORIS runs on a self-hosted Supabase stack on a Google Cloud virtual machine, with nightly backups copied off the machine; WhatsApp messages travel through Meta's Cloud API. Ask for the details that matter for your POPIA operator agreement during the demo.