Home › Glossary

Insurance broking and WhatsApp Business glossary

Broking, regulatory and WhatsApp Business vocabulary, explained in a few lines with links to the guides that go further.

By FCB.ai, ORIS editorial teamUpdated on

Where to start: a brokerage's core journeys

24-hour customer service window

The 24-hour customer service window is the period during which a business may reply freely to a person on the WhatsApp Business Platform. It opens whenever the client sends a message (text, button tap, reaction or attachment) and closes 24 hours after the last inbound message. Inside the window the business can send any free-form message: text, documents, images, interactive lists, with no template or prior approval. Once it closes, only an approved template can restart the conversation, and a reply from the client opens a fresh window. Under the per-message pricing Meta introduced in 2025, free-form messages inside the window are not charged, and utility templates sent while a window is open are free as well.

The window sets the operating tempo of a brokerage on WhatsApp. A client query received at 6 pm on Friday must be answered before 6 pm on Saturday to stay in free-form mode; after that the handler has to use a template, which is more formal and rarely suits a servicing conversation. The first practical consequence is organisational: a shared inbox with assigned conversations and a visible window indicator (ORIS shows Window Open, Awaiting Reply or Window Closed on each thread) prevents queries from slipping.

The second consequence is how follow-ups are designed. A renewal notice sent as a template with a "I have a question" button opens the window the moment the client taps it, so the handler can continue in plain language, send the policy schedule as a PDF and answer objections without another template. Reminder sequences are built around that mechanism: template, reply, free-form exchange, then a new template only if silence persists.

The third consequence is cost. A firm that answers quickly stays inside the window and pays nothing for the exchange; a firm that lets 24 hours pass pays for every template it has to send. The use cases describe the sequence for each journey, and the WhatsApp Business hub tracks Meta's pricing changes, which are worth checking against the official documentation before budgeting.

ACAPS (Morocco)

ACAPS, the Autorité de Contrôle des Assurances et de la Prévoyance Sociale, is Morocco's independent authority supervising insurance and reinsurance companies, insurance intermediaries (agents and brokers) and social welfare bodies such as pension and health coverage schemes. Created by Law 64-12 and operational since 2016, it replaced a directorate of the Ministry of Finance. ACAPS licenses intermediaries, monitors their solvency and conduct, handles policyholder complaints and issues sector regulation, including circulars on distribution and policyholder protection. The underlying statute is Morocco's Insurance Code (Law 17-99) and its implementing texts. Morocco is not part of the CIMA zone that governs fourteen Francophone African countries, so its rules on premiums, cancellation and distribution are its own.

For an English-speaking broker or insurer looking at Morocco, the first point is that the market operates in French and Arabic under a Moroccan code, with ACAPS as licensing authority for brokers: professional training and examination, suitable premises and a financial guarantee are among the conditions, and continuing obligations cover reporting, conduct of business and anti-money-laundering. The market is one of Africa's largest, with compulsory motor, life and savings distributed largely through bancassurance, and growing demand for complementary health cover since universal health insurance was extended.

Data protection is handled separately by the CNDP under Law 09-08: collecting and using phone numbers for WhatsApp messages must follow its notification and consent rules, especially for prospecting. ACAPS focuses on the fairness of information given to clients, the traceability of advice and the clear identification of the intermediary in all communications.

A brokerage deploying WhatsApp in Morocco therefore identifies the firm and its licence in its messages, keeps conversations at firm level, separates service messages (renewal notices, certificates, claims) from prospecting messages subject to consent, and handles complaints traceably. ORIS provides the shared inbox, Meta-approved templates and CSV export that support this. The relevant contrast for a Southern African reader is with FAIS and the FSCA: similar goals, a civil-law framework and no equivalent of the RE5 exam. See the country pages and the compliance hub.

Bancassurance

Bancassurance is the distribution of insurance products through a bank, either under a partnership between a bank and an insurer or through an insurance subsidiary owned by the bank. Customers are offered credit life, funeral cover, life and savings policies and sometimes motor or household insurance at the point where they open an account, take a loan or use the banking app. The model relies on volume, simple products and the bank's existing relationship with the customer. For a broker, bancassurance is a structural competitor: many clients hold a bank-sold policy they never compared, often because it was bundled with a loan. It is also a source of business, because bank-sold cover tends to be generic and is frequently unsuitable once the client's situation changes.

In South Africa, the major banks sell funeral, credit life and short-term cover through branches and apps, and the Policyholder Protection Rules and credit life regulations under the National Credit Act give consumers the right to substitute a credit life policy of their choice, which brokers can use to win that business. In Kenya and Nigeria, bancassurance is licensed and regulated by the IRA and NAICOM respectively, and the banks' reach into mobile banking makes them a formidable distributor for simple cover. In the UK, banks retreated from most general insurance advice after the payment protection insurance scandal, so the competitive overlap with brokers is smaller and concentrated in protection and home cover.

The broker's answer is service: being reachable, explaining the cover, comparing, and staying present after the sale. WhatsApp is where that presence lives for most African clients. A brokerage that identifies clients with a financed vehicle or a home loan, offers a review of the attached cover at the right moment and follows the substitution through to the end recovers policies the bank will not fight for. In ORIS, segments built on policy type and engagement score feed a cover-review campaign, and replies land in the shared inbox where the team can follow up. See the sales and prospecting hub and our use cases.

Binder agreement and UMA

A binder agreement is a contract under which an insurer delegates to a third party the authority to perform some of its own functions: entering into, varying or renewing policies on its behalf, determining policy wording, setting premiums or the value of benefits, and settling claims. The party holding that authority is a binder holder. An underwriting management agency (UMA) is a business that performs binder functions for one or more insurers in a specialist niche, such as fleets, marine, agriculture, cyber or microinsurance products, without carrying the risk itself. A broker may also hold a binder, but South Africa's Binder Regulations restrict which functions a non-mandated intermediary may perform and cap the binder fees it may earn on top of commission, to limit conflicts of interest. The UK equivalent is delegated authority held by a managing general agent (MGA) or a broker with a binding authority, including at Lloyd's.

In South Africa, the Binder Regulations under the insurance legislation and the FSCA's conduct standards define who may hold a binder, which functions may be delegated to a non-mandated intermediary, what must be reported to the insurer and how binder fees are limited; check the current regulations on the FSCA site rather than relying on remembered percentages, as they have been amended more than once. Namibia and Botswana follow similar practice with less detailed rules, and NAMFISA and NBFIRA expect the insurer to remain responsible for the outsourced function.

Operationally, a binder or UMA arrangement changes the client relationship. The brokerage issues the policy schedule itself, handles endorsements and, within its mandate, settles smaller claims. Clients therefore come to the brokerage for everything, which raises WhatsApp volumes and raises the bar on traceability, since the brokerage acts for the insurer and will be audited on its decisions.

In the UK, MGAs and brokers with delegated authority work under the same logic: underwriting and claims authority within agreed limits, bordereaux reporting, insurer audits and evidence of every decision. ORIS does not issue policies or settle claims; it organises the conversations around those acts (endorsement requests, claim notifications, document exchange), keeps them at firm level in the shared inbox and exports them as CSV to the policy administration system. See the running the brokerage hub and our comparisons.

Broker CRM

A broker CRM is customer-relationship software designed for an insurance brokerage: it centralises client and prospect records, their policies, interactions (messages, calls, meetings), upcoming follow-ups and sales opportunities. It is distinct from a broker management system (BMS) or policy administration system, which handles production, accounting, commission statements and insurer bordereaux, and from insurer portals used to quote and bind. A WhatsApp-centred CRM adds inbound and outbound messaging inside the client record, campaigns built on approved templates, segmentation of the book, and engagement and attrition-risk indicators derived from the conversations.

Most brokerages with three to fifty staff run a BMS or a spreadsheet alongside WhatsApp conversations scattered across personal phones. The broker CRM fills the gap between the two: who spoke to whom, when to follow up, and which clients need attention now.

The everyday functions are a unified client record (policies, renewal dates, consents, message history), segments (policy type, tenure, renewal window, risk score, opt-in status), reminder campaigns and lifecycle triggers (renewal, birthday, lapsed engagement, policy anniversary), and data export back to the BMS or the insurer.

Two honest caveats. Most WhatsApp CRMs, ORIS included, have no native integration with broker management systems or insurer portals; data moves by CSV import and export, which is enough to refresh the book monthly but does not replace the production system. And a CRM is not a payment or e-signature tool: a quote sent on WhatsApp is a message, and the policy is bound afterwards through the usual channel.

The spreadsheet-versus-CRM comparison helps decide at what size the tool pays for itself, the use cases show the journeys covered, and the running the brokerage hub deals with implementation. Seeing the workflow in a demo is quicker than reading about it.

CIMA Code

The CIMA Code is the single insurance code of the fourteen member states of the Conférence Interafricaine des Marchés d'Assurances, established by the Yaoundé Treaty of 10 July 1992: Benin, Burkina Faso, Cameroon, Central African Republic, Chad, Comoros, Congo, Côte d'Ivoire, Equatorial Guinea, Gabon, Mali, Niger, Senegal and Togo. In force since 1995, it governs insurance contracts, insurers and their supervision by the regional control commission (CRCA), and, in Book V, agents, brokers and other intermediaries. Its Article 13, amended by Regulation 0001/CIMA/PCMA/PCE/2011 of 11 April 2011, makes the policy effective only once the premium is paid and prohibits renewing a policy whose premium is outstanding: a strict cash-before-cover regime.

English-speaking brokers encounter the CIMA Code when they serve clients or partners in francophone West and Central Africa, or when a pan-African group standardises processes across both zones. The main difference from South African, Kenyan or Nigerian practice lies in premium collection.

In common-law markets, an unpaid premium typically triggers a grace period and then a lapse, with reinstatement procedures; in CIMA states there is no cover until the premium has been received, and a policy unpaid at renewal terminates automatically. The broker's premium reminder is therefore not a retention exercise but a condition of cover. Brokers in Abidjan, Dakar or Douala send reminders on WhatsApp ten to fifteen days before the due date, list the local payment options (Orange Money, Wave, MTN MoMo, bank transfer, cash at the branch) and send the certificate of insurance as a PDF in the same thread once payment is confirmed.

Book V of the Code sets out intermediary licensing: brokers are approved by the minister in charge of insurance in each state, must hold a financial guarantee and keep registers. Detailed rules vary by country and are summarised on the country pages. The follow-ups and renewals hub covers reminder sequences, and the policy lapse entry explains the contrasting grace-period regimes of anglophone markets.

Commission clawback

Commission clawback is the insurer's right to recover some or all of the commission already paid to a broker when the policy that earned it lapses, is surrendered or is cancelled within a set period. It applies mainly to recurring-premium products where commission is paid upfront on the strength of future premiums: life and funeral cover, credit life, income protection, savings plans with monthly contributions. If the client stops paying, cancels or the policy is voided for non-disclosure during the clawback period, the insurer deducts the unearned commission from future statements or bills the brokerage. Clawback turns every early lapse into a direct loss and makes persistency a financial concern for the brokerage, not only a service metric.

In South Africa, clawback is written into the regulations under the Long-term Insurance Act: on recurring-premium risk policies, commission is paid in two instalments over two years and remains recoverable if the policy lapses or is surrendered during that period. Brokerages with a large book of funeral or credit life policies and a high rate of failed debit orders in the first months feel this directly on their commission statements. Namibia, Botswana and Kenya have their own rules, so check the regulator's guidance and each product agreement rather than assuming the South African pattern applies.

In the UK and Ireland, clawback on protection business is contractual rather than statutory, with indemnity commission typically subject to recovery over the first years of the policy, on a reducing scale; the terms are set by each provider's agency agreement.

For a brokerage working on WhatsApp, the clawback period is the window where servicing pays for itself. A welcome message confirming the first premium, an immediate message when a debit order fails, a reminder before each collection date and a quick answer to questions about the policy all reduce early lapses. ORIS surfaces this in the Opportunities & Risks view: the risk score, the attrition flags and the lifecycle triggers point the team to recently written policies whose engagement is falling. Our guide to lapse risk on WhatsApp for South African brokers walks through the sequence, and the retention and loyalty hub covers the wider approach.

Consumer Duty (FCA)

The Consumer Duty is the FCA's overarching requirement that firms act to deliver good outcomes for retail customers. Introduced through Principle 12 and the rules in PRIN 2A, it came into force on 31 July 2023 for open products and services and on 31 July 2024 for closed books. It rests on three cross-cutting rules (act in good faith, avoid foreseeable harm, enable and support customers to pursue their financial objectives) and four outcomes: products and services, price and value, consumer understanding, and consumer support. Firms must monitor and evidence these outcomes, and boards must review an annual report on them. For insurance brokers, the Duty goes further than Treating Customers Fairly: it asks for data showing that clients understand what they buy and can get help, make changes or cancel as easily as they can purchase.

The Duty binds FCA-regulated firms, including brokers placing business for retail and small-business customers, and it reaches along the distribution chain: a wholesale broker or MGA must consider the outcomes of end customers it never meets. Irish brokers fall under the Central Bank of Ireland's Consumer Protection Code instead, and EU brokers under IDD and national rules, which pursue similar aims through documentation rather than outcome monitoring.

For a brokerage that uses WhatsApp, two outcomes dominate. Consumer understanding requires communications that are clear, tested and tailored to the audience, including customers with characteristics of vulnerability; a renewal message that buries a price rise or a coverage change fails that test. Consumer support requires that a client can reach the firm to ask a question, claim or cancel as easily as to buy, without unreasonable delay or friction, and that the firm can show response times and outcomes. Client conversations scattered across personal phones cannot produce that evidence.

Record-keeping under SYSC and the Duty's monitoring expectations push brokers towards a shared, firm-owned channel. ORIS provides the shared WhatsApp inbox with full history per customer, visible response times, AI classification of incoming requests so that cancellations and complaints are not missed, and CSV export to feed the outcomes dashboard the board reviews. Our guide to a shared WhatsApp inbox under Consumer Duty sets out the workflow, and the compliance hub covers related rules.

Credit life insurance

Credit life insurance is cover attached to a loan, vehicle finance, store account or home loan that settles the outstanding balance or the instalments if the borrower dies, becomes disabled, or in many products loses employment. The lender usually offers its own policy when the credit is granted, but in South Africa the consumer has the right to substitute a policy of their choice with equivalent benefits, and the credit life regulations under the National Credit Act cap the cost of cover on most consumer credit agreements. Similar products exist under the names credit protection or loan protection in Kenya, Nigeria and Ghana, and as mortgage protection or payment protection in the UK, where the PPI mis-selling scandal reshaped the market and the rules. For a broker, credit life is both a protection need to check and a policy that can be won from the lender.

In South Africa, a brokerage can approach clients who took finance with the lender's credit life and offer a substitute policy, provided the benefits are at least equivalent and the FAIS record of advice documents the comparison. The regulations also oblige the credit provider to accept a compliant substitute. In Namibia and Botswana, check the position with NAMFISA and NBFIRA before running a substitution campaign, as the consumer credit rules differ. In the UK, anything resembling payment protection insurance is sold with great care under ICOBS and Consumer Duty, with a focus on eligibility and value; many brokers prefer standalone income protection.

Credit life also needs servicing. A policy that lapses because a debit order failed leaves the borrower's family exposed to the debt, and the lender may force-place cover at a higher cost. A retrenchment claim is time-sensitive and paperwork-heavy.

On WhatsApp, a brokerage uses the channel for both sides: a cover-review campaign aimed at clients with vehicle finance or a home loan, and a servicing routine that reacts to failed collections and walks a retrenched client through the claim documents. ORIS lets the team build a segment on policy type and engagement score, launch the review campaign from a Meta-approved template, then handle replies and claims from the shared inbox. The sales and prospecting hub and our use cases cover the practical steps.

Cross-sell and upsell

Cross-selling means offering an existing client a policy in a line they do not yet hold: household cover to a motor client, income protection to a client with funeral cover, commercial cover to a tradesperson insured for their vehicle. Upselling means improving the cover the client already has: moving from third party to comprehensive, adding a legal expenses extension, raising a sum insured, adding a spouse or children to a funeral plan. For a brokerage, both are the main growth lever with no acquisition cost, because the client is already there and trust exists. They are only legitimate when they answer a real, identified need, which brings the duty to advise back in: a proposal must be motivated and recorded, not pushed.

In South Africa, cross-sell and upsell messages on WhatsApp are direct marketing under POPIA section 69 unless they concern the client's existing policy, so the brokerage needs consent or a qualifying existing relationship, an opt-out in every message, and a FAIS record of advice for any recommendation; TCF outcome 2 adds that the product must suit the segment it is offered to. In the UK, UK GDPR and PECR govern the message, ICOBS and Consumer Duty govern the advice and the value of what is sold. Everywhere, Meta's rule applies: a promotional message goes out as a marketing-category template, and the client can opt out at any time.

The right moments are well known: policy anniversary, a life event mentioned in conversation (marriage, birth, moving house, a new car, starting a business), the annual review, a claim that was handled well. In ORIS, those moments surface in three ways. The analysis of incoming messages classifies replies that contain an opportunity (UPSELL_CROSSSELL_OPPORTUNITY) and detects life events; an opportunity is then created with a type of upsell, cross_sell, coverage_review or attrition_risk, a status of new, in_progress, won or lost, and AI fields for source, confidence, sentiment, urgency and reasoning. The "Cover review / upsell" campaign goal and the coverage_gap_score help start the conversation deliberately; the Opportunities & Risks view, sorted by Fastest to Convert, opens the conversation with the Quote Builder, which sends a quote as a WhatsApp text (insurance type, covers, premium, valid-until date, personal note). The quote is a message, not a contract: binding happens in the brokerage's own systems.

See the sales and prospecting hub and our use cases.

Customer segment

A customer segment is a subset of a brokerage's client book defined by one or more shared criteria: policy type held, renewal date, tenure, risk of lapse or cancellation, engagement level, consent to receive messages, location or life stage. Segmenting exists so that a message reaches the people it is relevant to rather than the whole book, so that results can be measured by group, and so that advisers' time goes where it matters. In a brokerage, the useful segments are operational more than promotional: policies renewing in the next thirty days, single-policy clients who could need additional cover, clients with no contact in six months, clients with an active WhatsApp opt-in. A segment can be dynamic, recalculated from its criteria, or a fixed list picked by hand.

Segmentation is also how a WhatsApp campaign stays within the rules. It excludes clients without an opt-in or who have opted out, separates servicing messages from marketing, and lets the tone fit the audience: a renewal reminder to a long-standing client reads differently from a re-engagement message to someone who has gone quiet. In South Africa, POPIA shapes what may be used as a criterion and for what purpose, and direct marketing segments must respect section 69; in the UK, UK GDPR and PECR apply the same way, with the added expectation under Consumer Duty that vulnerable customers are identified and handled appropriately.

In ORIS, the Customers & Segments module offers two ways to build a segment: filters on Risk Score, Engagement Score, Status, WhatsApp Opt-In and Days Since Inception, combined with Equals, Greater than and Less than operators; or Manual Selection of individual customers. Customers enter the book by manual entry or CSV import. When a campaign is created, the "Who to contact" step attaches a saved list or filters by policy type, tenure and renewal window. Campaign sends go only to customers with a WhatsApp opt-in, and opt-outs are excluded at send time. Segments then appear in the campaign list and in Analytics, where cohorts can be compared.

For segments used in practice, see our use cases and the POPIA and WhatsApp consent guide for the consent side.

Debit order

A debit order is a payment instruction that allows an insurer, or a broker with collection authority, to draw the premium directly from the client's bank account on an agreed date under a signed or electronically confirmed mandate. It is the dominant collection method for monthly premiums in South Africa, Namibia, Botswana, Eswatini and Lesotho, and common in Kenya, Zambia and Zimbabwe alongside mobile money. In South Africa, the DebiCheck system introduced by the Payments Association and the banks requires the client to authenticate the mandate with their bank, replacing the older NAEDO and AEDO early debit orders and limiting unfair disputes. A returned debit order (insufficient funds, closed account, disputed mandate) is the earliest warning of a lapse. The European equivalent is the SEPA direct debit.

For a brokerage in Southern Africa, the debit order is where retention is won or lost. Most funeral, life and personal-lines motor policies are paid monthly, usually on payday, and rejection rates climb at month end when salaries run short. Insurers send brokers lists of unpaid debit orders, and the broker has to reach each client to arrange a re-presentation, an EFT payment or a mobile-money payment where that is common, before the grace period runs out. Under the Policyholder Protection Rules, the insurer must also notify the policyholder of the missed premium, but the broker's call or message is what usually gets the premium paid.

DebiCheck added a step at inception: the client must approve the mandate in their banking app, at an ATM or by USSD, and many mandates fail or expire at this stage, delaying the policy start. A short WhatsApp message explaining what to approve, with a screenshot of the bank prompt, resolves most of these.

WhatsApp suits both moments. At inception, confirm the mandate and the first collection date. After a rejection, send the amount, the reason returned by the bank and a quick-reply choice of re-presentation date. In ORIS these go out as utility templates, and the client's reply opens a conversation to settle the case; the payment category of templates exists for exactly this purpose. The lapse-risk guide walks through a full monthly cycle, the policy lapse entry covers what happens next, and the country pages list the collection methods that dominate each market.

Durable medium

A durable medium is any instrument that lets a client store information addressed personally to them, in a way that is accessible for future reference for as long as the information is relevant, and that allows the unchanged reproduction of that information. The definition comes from the Insurance Distribution Directive and is mirrored in the FCA Handbook glossary for UK firms. Paper is the benchmark; a PDF attached to an email, a secure client portal with downloadable documents or a USB key also qualify. The concept matters because contract terms, the insurance product information document, demands-and-needs statements and other pre-contractual information must be provided on paper or, subject to conditions, on another durable medium. A web page the firm can alter, or a message that can be deleted by the sender, does not meet the test.

For UK and Irish brokers, ICOBS allows information to be provided on a durable medium other than paper where it is appropriate to the business conducted and the client has chosen it. Dutch and Nordic firms apply the same IDD test through their national rules. South Africa does not use the term in the same way, but the FAIS General Code requires that disclosures and records of advice be provided in a form the client can keep, and POPIA requires that personal information in those documents be kept securely and not for longer than needed.

Is WhatsApp a durable medium? Partly. A PDF sent in a conversation is downloadable and can be reproduced unchanged by the client, so that file meets the criteria. The chat thread itself does not: messages can be deleted, disappearing messages exist, and the firm cannot control what the client retains. A careful brokerage sends contractual documents as attachments on WhatsApp and by email, logs the evidence of delivery, and never treats a "yes" in the thread as a signature or as acceptance of terms.

ORIS sends documents from the shared inbox through the WhatsApp Business API, which gives the brokerage the timestamp, the delivered and read receipts, and a complete history attached to the customer record. See our note on a shared WhatsApp inbox and Consumer Duty record-keeping, and the compliance hub for other markets.

Duty to advise

The duty to advise is the obligation on an insurance intermediary to establish the client's demands and needs, to give objective information about the product and, where advice is given, to explain why the recommended policy is suitable. In the EU it comes from the Insurance Distribution Directive (IDD), which requires a personalised recommendation before the contract is concluded; in the UK the same principles sit in the FCA's ICOBS rules and, since 2023, under the Consumer Duty. In South Africa, the FAIS Act and its General Code of Conduct impose a comparable suitability analysis and a record of advice on every financial services provider. The duty is distinct from disclosure, which covers the features of the product, and it survives the sale: a client can challenge unsuitable advice years later, and the brokerage must be able to produce what was recommended and on what basis.

For a South African brokerage, the record of advice under the FAIS General Code is the document the FSCA and the Ombud for Financial Services Providers will ask for in a complaint. For a UK broker, the demands-and-needs statement and the file note serve the same purpose, and Consumer Duty adds the expectation that the firm can show the client understood the advice. Namibia and Kenya have their own codes, so confirm the local requirement with the regulator rather than copying the South African template.

WhatsApp is a good channel for gathering needs and a poor one for evidencing advice unless the brokerage controls the conversation. Advice that lives on an adviser's personal phone cannot be retrieved for a complaint, an FSCA inspection or a Lloyd's audit. The practical split: ask questions and collect documents on WhatsApp, deliver the recommendation as a document the client can keep, and retain the full conversation at firm level.

ORIS keeps every WhatsApp conversation in a shared inbox owned by the brokerage, with the history attached to the customer record, so the exchange that led to a recommendation is still there when needed. AI drafts suggest service replies; they do not give advice. Our guide to a shared WhatsApp inbox under Consumer Duty covers record-keeping for UK firms, and the compliance and regulation hub covers the other markets.

Embedded Signup

Embedded Signup is Meta's onboarding flow for connecting a WhatsApp number to the WhatsApp Business Platform from inside a third-party application, without going through Business Manager by hand. It relies on Facebook Login for Business: the user signs in with a Facebook account, selects or creates a Meta Business portfolio and a WhatsApp Business Account (WABA), registers the phone number, verifies it by SMS or voice call and authorises the software to manage the account. At the end, the software receives an access token and subscribes to the account's webhooks. The number must not be in use on the WhatsApp or WhatsApp Business app, or must be released first, and a six-digit PIN protects the registration.

For a brokerage, Embedded Signup is the point at which the number stops being someone's phone and becomes a company asset. A little preparation removes most of the friction.

Use the Facebook account of a principal or a long-term administrator, not a junior employee: that person becomes an admin of the Meta Business portfolio. The portfolio should carry the firm's legal name and, ideally, have completed business verification (company registration document, proof of address), which unlocks higher messaging tiers and the permanent display name.

Choose the number deliberately. A landline of the brokerage works, verified by voice call, and avoids depending on a SIM card in someone's drawer. If the firm wants to keep a number already used in the WhatsApp Business app, it must export the chat history, delete the account from the app and only then run Embedded Signup: app conversations do not migrate to the API.

In ORIS the WhatsApp screen guides these steps in seven stages, shows the connection state (not connected, pending verification, connected), then the display name, the number's quality rating and the synchronised templates. The South African setup guide covers portfolio preparation in detail, and the WABA entry explains what the flow creates behind the scenes.

Engagement score

An engagement score measures how actively and regularly a client interacts with the brokerage: whether they reply to messages and how quickly, whether they ask questions, report changes or request quotes on their own initiative, whether they open documents sent to them. Unlike the risk score, which looks for signs of leaving, the engagement score describes the level of interaction, whether warm or absent. A highly engaged client is not necessarily loyal and a silent one is not necessarily leaving, but engagement is the best predictor of whether the brokerage can act at all: cover reviews, cross-sell proposals and lapse prevention all require a client who responds. The score is therefore used to pick the right moment, the right message and the right level of human attention.

On WhatsApp, engagement is measurable in a way no other channel allows: delivery and read receipts, time to reply, buttons tapped, response to a template. A brokerage uses it for three decisions. What to send: an engaged client can receive a cover review or a proposal, a silent client a short re-engagement message. When: a reply from the client opens the 24-hour customer service window for free-form conversation; outside it, only an approved template can be sent. Who gets human time: an engaged client asking questions deserves a call, a client who never replies belongs in an automated routine. In Southern and East Africa, where clients change SIM cards more often, a sudden drop in engagement sometimes means a dead number rather than lost interest, and the first action is to confirm the number.

In ORIS, each customer carries an engagement_score shown in the Engagement column of the Customers & Segments table, displayed on a four-level scale: none, low, medium, high. Engagement Score is one of the segment filters (Equals, Greater than, Less than), so a re-engagement campaign can target clients with low or no engagement, or a cover proposal can be reserved for engaged ones. A lifecycle trigger of type lapsed_engagement prepares a draft campaign for clients who have gone quiet. The Dashboard's Hottest Leads table surfaces clients whose recent exchanges point to an opportunity.

See the retention and loyalty hub and our re-engagement templates.

FAIS Act

The FAIS Act (Financial Advisory and Intermediary Services Act 37 of 2002) regulates anyone in South Africa who gives financial advice or renders intermediary services, which includes insurance brokers. A firm needs a Financial Services Provider licence from the FSCA, with key individuals responsible for management and oversight and representatives recorded on the FSP's representative register. All must meet the fit-and-proper requirements set out in Board Notice 194 of 2017: honesty and integrity, competence (qualifications, regulatory examinations, class of business and product-specific training), continuous professional development and operational ability. The General Code of Conduct adds disclosure, needs analysis, record of advice and a minimum five-year record-keeping duty. Complaints go to the FAIS Ombud.

The FAIS framework shapes a brokerage's WhatsApp operation in three concrete ways.

Authorisation follows the person, not the phone. A representative may only advise on the categories and sub-categories shown on the register; conversations about a product outside that scope must be handed to an authorised colleague. A shared inbox with assignment by product line makes that visible, whereas personal phones hide it.

Records must be complete and retrievable. Section 18 of the General Code requires records of advice, client instructions and communications to be kept for at least five years and to be available to the FSCA on request. A WhatsApp thread in which a representative discusses cover, premiums or exclusions is such a record. Exporting each client's history and attaching it to the client file is the minimum; keeping the conversation inside the CRM is simpler.

Supervision must be demonstrable. Key individuals are accountable for representatives under supervision, and the FSCA expects evidence of oversight. Read access to all conversations, with audit logs of who replied, provides that evidence without extra paperwork. The competence requirements, including the RE5 examination, and the Treating Customers Fairly outcomes have their own glossary entries. See setting up WhatsApp Business for a South African brokerage and the compliance hub.

Funeral cover

Funeral cover is a life policy that pays a lump sum, or provides funeral services directly, when the policyholder or a covered family member dies, usually within days of a valid claim so that the family can hold the funeral. It is the most widely held insurance product in South Africa and much of Southern Africa: low monthly premiums, cover for spouse, children and extended family, short waiting periods for natural causes and none for accidental death. Policies are sold by insurers, brokers, funeral parlours, retailers and banks, and a large share of them fall under the microinsurance regime introduced by the Insurance Act of 2017. In the UK, the nearest equivalent is the over-50s plan or the funeral plan, which has been regulated by the FCA since 2022 and serves a very different, older market.

For a South African, Namibian or Botswana brokerage, funeral cover is a volume book with three regulatory anchors: the Policyholder Protection Rules on disclosure and claims handling, the microinsurance product standards on benefits, waiting periods and exclusions, and the FAIS General Code on advice and record-keeping. NAMFISA and NBFIRA apply their own rules, so confirm waiting periods and claims timelines locally rather than quoting the South African standard.

The commercial challenge is persistency. Premiums are collected by debit order from accounts that run empty before month-end, collections fail, the policy lapses after a set number of unpaid months and the commission is clawed back. The brokerages that keep their funeral book alive are the ones that react on the day a collection fails, not at the end of the month.

On WhatsApp, that means three routines: a welcome message confirming covered members and the end of the waiting period; a reminder before each collection date; and an immediate message when a debit order bounces, with the retry date and alternative payment options. At claim stage, families often notify the brokerage on WhatsApp with a photo of the death certificate; the reply has to be fast and humane, and the documents list clear. ORIS handles the routines with Meta-approved utility templates and the shared inbox, flags clients whose engagement has dropped, and keeps the claim conversation attached to the customer record. Our guide to stopping lapses with WhatsApp is built around a funeral book, and the retention hub goes further.

GDPR

The GDPR is Regulation (EU) 2016/679 on the protection of personal data, in force since 25 May 2018 across the EU and EEA; the UK retained it as UK GDPR alongside the Data Protection Act 2018, supervised by the ICO. A brokerage is a controller: it must have a lawful basis for each processing activity (Article 6), inform clients about what it does with their data (Articles 13 and 14), honour rights of access, rectification, erasure and objection (Articles 15 to 21), keep records of processing (Article 30) and report certain breaches. Health data, common in life, income-protection and private medical insurance, is special-category data under Article 9 and needs an additional condition.

On WhatsApp the regulation bites in four places.

Lawful basis for each message type. Servicing messages about an existing policy rest on contract performance or legitimate interests. Marketing messages to individuals are governed in the UK by PECR regulation 22 and in EU states by the ePrivacy rules: prior consent, or the soft opt-in for existing customers being offered similar products with an opt-out at every message. That is why a broker CRM separates opt-in for marketing from service contact.

Right to object. Article 21 gives every person the right to stop direct marketing at any time, and the brokerage must apply the opt-out across all senders, including individual account handlers.

Retention and security. Chats contain identity documents, bank details and sometimes medical information. They belong in a system the firm controls, with named user access and a retention schedule consistent with FCA record-keeping rules, not on personal phones. The ICO has also published guidance on the use of messaging apps for business, stressing that firms remain accountable for business messages sent through them.

International transfers. Using the WhatsApp Business API means Meta processes message metadata; the brokerage should document the processor relationship and the transfer mechanism in its records. The compliance hub and the POPIA entry compare the European and South African approaches.

IDD (Insurance Distribution Directive)

The Insurance Distribution Directive is Directive (EU) 2016/97 of 20 January 2016, applied across the EU since 1 October 2018 and retained in UK law after Brexit through the FCA Handbook (ICOBS, SYSC and the training and competence rules). It replaced the 2002 Insurance Mediation Directive and covers every distributor, including insurers selling direct. Its core requirements: act honestly, fairly and professionally in the customer's best interests; establish the customer's demands and needs before proposing a product; provide a standardised Insurance Product Information Document for non-life products; disclose the nature of remuneration; complete at least fifteen hours of professional training per year; and apply product oversight and governance rules.

For a European brokerage using WhatsApp, the IDD matters at three moments of the client journey.

Before the sale, the demands-and-needs assessment (Article 20) must be documented. If a client asks for a quote on WhatsApp and the broker replies with a recommendation, the questions and answers are part of the advice file. Keeping them in a client record rather than on a personal handset is what makes the file complete.

At the point of information, Article 23 sets the rules on the medium: paper by default, or a durable medium or website when the client has chosen it and can retrieve the document later. Sending the IPID as a WhatsApp attachment is acceptable only within those conditions, and the brokerage should be able to prove the document was sent.

After the sale, the duty to act in the client's best interests shapes renewals and cross-sell messages. A campaign that offers a product without any link to the client's situation sits uneasily with the directive; a segmented message based on a known gap in cover does not. In the UK, Consumer Duty reinforces the same logic with its consumer-understanding and fair-value outcomes, as discussed in the Consumer Duty inbox guide. The compliance hub covers related rules.

Insurance broker

An insurance broker is an independent intermediary who acts for the client rather than for the insurer: the broker assesses needs, obtains quotes from several insurers, places the cover and usually services the policy afterwards. In South Africa a broker operates as a financial services provider licensed under the FAIS Act, with key individuals and representatives who must meet fit-and-proper requirements. In the UK a broker is authorised by the FCA for insurance distribution and bound by ICOBS and Consumer Duty; across the EU the Insurance Distribution Directive applies. Brokers are distinct from tied agents, who represent one insurer, and from underwriting agencies, which carry delegated underwriting authority on behalf of insurers.

Being independent cuts both ways for a brokerage that talks to clients on WhatsApp.

The broker owns the advice. Under FAIS the record of advice, the disclosures and the client's instructions must be kept and retrievable; under Consumer Duty the FCA expects evidence that communications were understood. A recommendation typed into WhatsApp counts. The shared inbox guide for UK brokers shows how teams keep that evidence without exporting chats by hand.

The broker also owns the relationship across many insurers and many policies. A single client may hold motor and household cover with one insurer, funeral cover with another and a retirement annuity with a third. Renewals, debit-order failures and claims updates all converge on the broker, which is why a shared inbox and a consolidated client record matter more to brokers than to insurers.

Finally, in Southern and East Africa the broker is often the person who spots a missed premium first. Reaching the client on WhatsApp within days, not weeks, is the difference between a reinstated debit order and a lapsed policy, as described in the lapse-risk guide. Country specifics are on the country pages.

Insurance intermediary

An insurance intermediary is any person who, for remuneration, carries out insurance distribution without being an insurer: advising on, proposing or concluding insurance contracts, or assisting in their administration and performance. The EU Insurance Distribution Directive (Directive 2016/97) uses that definition; the UK kept it after leaving the EU. In South Africa the FAIS Act speaks of financial services providers rendering intermediary services, with key individuals and representatives acting under a licence, while the Insurance Act and the Policyholder Protection Rules refer to independent intermediaries. In Kenya, Nigeria and Ghana, agents and brokers are registered separately by the IRA, NAICOM and the NIC respectively.

The practical point for a brokerage is that the duties attach to the activity, not to the job title. A representative under supervision, a tied agent and a licensed broker all owe disclosure, suitability and record-keeping obligations when they discuss cover with a client on WhatsApp.

In the UK, the FCA requires firms to state their authorised status and registration details; the FCA register number belongs in the brokerage's WhatsApp profile and opening message. In South Africa, representatives must be listed on the FSP's representative register and act within the categories and sub-categories they are authorised for; a representative who discusses a long-term product on WhatsApp while only authorised for short-term cover creates a compliance breach. A brokerage number on the WhatsApp Business API makes it easier to check who said what, because each conversation is tied to a named user.

In other African markets, intermediaries are frequently agents working for one insurer or small brokerages registered with the national regulator; the country pages list each regulator and the registration rules. The compliance hub goes deeper into each regime.

Lifecycle trigger

A lifecycle trigger is a rule that links a dated event in the life of a client or a policy to a communication action: an approaching renewal, the client's birthday, the anniversary of the policy, a period without interaction, the end of a waiting period, a closed claim. The idea comes from marketing automation and suits broking well, because most useful contacts can be predicted from dates the brokerage already holds. A trigger has three parts: the event, the lead time (for example thirty days before renewal) and the action (prepare or send a message, create a task). Done well, it replaces the renewals spreadsheet and makes sure no client is forgotten; done badly, it produces automated messages that miss the context, such as a renewal reminder sent to a client who cancelled last week.

For a brokerage, the useful triggers are few and recurring: the renewal or premium reminder (the most valuable, since it prevents lapses and, in Southern Africa, commission clawback), the policy anniversary (the natural moment for a cover review), the client's birthday (a relationship message, not a sales one) and re-engagement after a period of silence. On WhatsApp, each trigger must rely on a Meta-approved template, because the message is sent outside a 24-hour customer service window, and must reach only clients with an opt-in. In the UK, a birthday message is relationship contact, but a birthday message carrying an offer is direct marketing under PECR; in South Africa the same line is drawn by POPIA section 69.

In ORIS, triggers are configured in Settings, under the Automation tab, in the Lifecycle triggers section, with four types: renewal_reminder, birthday, lapsed_engagement and policy_anniversary, each with a days_before lead time. The lifecycle-check function runs through active triggers and creates a draft campaign named "Auto: …", together with a "Lifecycle trigger fired" notification. The team reviews the draft, checks the template and the audience, then launches it: the trigger prepares the work and does not send messages behind the team's back. Template variables (first name, broker name, renewal date, policy type, premium) are filled at send time.

See our use cases on premium reminders and the follow-ups and renewals hub.

Microinsurance

Microinsurance is insurance designed for low-income or unbanked people: small premiums, simple benefits, few exclusions, and simplified underwriting and claims. Typical products cover funeral expenses, hospital cash, personal accident, crops, livestock or the stock of a small trader. South Africa created a dedicated microinsurance licence under the Insurance Act of 2017, with product standards that cap benefits and limit waiting periods and exclusions; Kenya, Ghana and Nigeria have their own microinsurance frameworks set by the IRA, the NIC and NAICOM. The economics depend on volume and very low distribution costs, which is why microinsurance is sold through mobile money operators, retailers, cooperatives, funeral parlours and messaging channels rather than through conventional advice meetings.

For a brokerage in Southern or East Africa, microinsurance is a volume business with specific compliance: the South African product standards fix what a microinsurance policy may contain, the Policyholder Protection Rules apply, and in some markets a separate microinsurance agent category exists for distributors who are not full intermediaries. Confirm with the FSCA, the IRA or the NIC what licence the brokerage and its sub-agents need before launching. The CIMA zone in Francophone Africa has a 2012 microinsurance regulation that sets its own premium and benefit ceilings, a different regime from the Anglophone ones.

Operationally, the difficulty is not selling but collecting premiums and keeping policies alive. Premiums are paid in small amounts through M-Pesa, MTN MoMo or Airtel Money, or collected by debit order from low-balance accounts; clients rarely have email and reply on WhatsApp, often with a voice note. The brokerage needs short, repeatable messages: a reminder before the collection date, a confirmation of payment, the policy schedule as a PDF in the thread, claims by photo.

ORIS fits that pattern: CSV import of the book, campaigns from Meta-approved utility templates, AI classification of replies in the shared inbox, and CSV export to the insurer. Our message templates include short premium reminders written for this segment, and the lapse-risk guide shows how the reminder sequence works.

Mobile money

Mobile money is an electronic wallet tied to a mobile phone number that lets people deposit, withdraw, transfer money and pay merchants or bills without a bank account. Mobile operators such as Safaricom (M-Pesa), MTN (MoMo) and Airtel Money, together with specialist providers, have made it the dominant retail payment method across East Africa and much of West Africa; in South Africa it remains marginal next to debit orders and cards. For insurance, mobile money is used to pay premiums, to receive claim payouts and, increasingly, to buy simple policies directly from the phone. Because the wallet is identified by the same number a client uses on WhatsApp, the conversation and the payment sit naturally side by side, which is what makes it relevant to a brokerage's messaging workflow.

In Kenya, Tanzania, Uganda, Rwanda and Ghana, a brokerage that wants low-income or informal-sector clients to stay insured has to accept mobile money, usually through a paybill or merchant number, and reconcile payments against policies by phone number. The IRA in Kenya and other regulators have licensed mobile-distributed products, and many insurers run their own paybill numbers; check the agreement with each insurer on who collects and who remits. In South Africa, Namibia and Botswana, debit orders remain the norm and mobile money is rarely part of the picture, so the glossary entry on debit orders is the relevant one there.

The practical traps: transaction fees and daily limits vary by operator and country, so a large annual premium may need splitting; payments arrive without a usable reference, so reconciliation depends on the client's phone number and confirmation; and a client who changes SIM card breaks the link between wallet, WhatsApp number and policy record. Ask for the transaction reference or screenshot in the WhatsApp thread, store it against the customer, and reply with the policy schedule or receipt as a PDF.

ORIS does not move money and has no connection to mobile money operators; it organises the conversation around the payment. The premium reminder template carries the amount and the paybill number, the client's reply lands in the shared inbox, the AI classifies it as a payment confirmation or a question, and the adviser confirms and sends the receipt. See our message templates for premium reminders and the follow-ups and renewals hub.

Opt-out

An opt-out is a person's request to stop receiving certain messages. In the EU and UK it flows from the right to object to direct marketing in Article 21 of the GDPR and from PECR's requirement that every marketing message offer a simple way to refuse further contact. In South Africa, section 69 of POPIA requires an opt-out opportunity in every direct-marketing communication. On WhatsApp an opt-out usually arrives as a reply containing a keyword (STOP, UNSUBSCRIBE, CANCEL) or a quick-reply button; the client may also block the number, which Meta counts against the sender's quality rating. A marketing opt-out does not, on its own, prevent servicing messages about an existing policy.

The hard part for a brokerage is applying the opt-out everywhere, at once. A client who replies STOP to one account handler and receives an offer from another handler a week later is both a compliance breach and a likely block.

Three operating rules solve it. First, the opt-out belongs to the client record, not to a conversation: in ORIS the WhatsApp webhook recognises STOP, UNSUBSCRIBE, REMOVE, OPTOUT and CANCEL automatically, adds the number to the opt-out list and excludes it from every campaign. Second, the brokerage separates marketing opt-out from service opt-out: a client who refuses offers should still receive renewal notices and claim updates, unless they ask to stop all WhatsApp contact, in which case the firm falls back to post or email for regulatory notices. Third, every marketing template carries an unsubscribe line, as required by POPIA and PECR and encouraged by Meta's marketing-message guidance.

A high opt-out rate on a campaign is a targeting signal: too broad, too frequent or poorly worded. It is worth reading before the quality rating moves. POPIA and WhatsApp: what a broker may send walks through the South African rules message by message, and the use cases show where the unsubscribe line fits in each journey.

ORIAS (France)

ORIAS is the body that keeps France's single register of intermediaries in insurance, banking and finance: insurance brokers and tied agents, mandated agents, credit intermediaries and financial investment advisers. Every insurance broker must be registered before doing business, under criminal penalty, and must renew the registration each year. Registration requires evidence of good repute, professional competence, professional indemnity insurance and, for brokers who handle client money, a financial guarantee. The ORIAS number must appear on the firm's documents and communications, and the register is public, so clients can check that a broker is authorised. Conduct supervision sits with the ACPR, the prudential and resolution authority, and since the broking reform with ACPR-approved professional associations that brokers must join. ORIAS is the French equivalent of the FCA register in the UK or the FSP register in South Africa.

For a UK, Irish or Dutch broker dealing with France, the practical points are these. A French broker can be verified on the public ORIAS register by name or number; an EU broker passporting into France under IDD freedom of services appears there too. Since Brexit, UK brokers cannot passport and need a locally authorised partner or entity for French business. Belgium (FSMA), Luxembourg (Commissariat aux Assurances) and Switzerland (FINMA) keep their own registers.

The comparison with Africa is instructive: South Africa's FSP register under FAIS plays a similar role, with the key individual and representatives listed; in the CIMA zone and Morocco, broker licences come from ministries or ACAPS without a single searchable register of this kind.

On WhatsApp, ORIAS comes down to identification. A message from an employee's personal phone without the firm's name does not identify the intermediary as French rules require. The firm's WhatsApp Business profile (name, address, website, description) and first-contact templates should name the brokerage and point to the legal notice page where the ORIAS number appears. ORIS runs on the WhatsApp Business API with a number in the firm's name, Meta-approved templates that name the firm, and history retained at company level. See the compliance hub and the country pages for France and its neighbours.

Persistency

Persistency is the proportion of policies still in force after a given period, most often measured at 13 and 25 months from inception for long-term business with recurring premiums (life, funeral, credit life, income protection) and year on year for renewable short-term policies. It can be calculated by policy count or by premium. Insurers track it per intermediary because a book that lapses in the first months never recovers its acquisition cost or the upfront commission paid. In South Africa, Namibia, Botswana, Kenya and Nigeria, persistency therefore drives commission terms, clawback exposure and sometimes whether a broker code stays open with an insurer.

Persistency is a relationship metric more than a pricing one, and almost every lever sits with the brokerage. The first month matters most: a welcome message, the policy documents, confirmation of the first debit-order date and a check-in at thirty days cut early cancellations. After that, a reminder before each premium, a fast reaction to unpaid debit orders and contact at each life event (house move, new child, new car) keep the policy relevant. Listening for weak signals in conversations (complaints about price, mention of a competitor, unusual silence) lets the handler act before the client decides.

Measuring persistency by representative is also a supervision tool: a representative whose business lapses early may be selling on price or to clients who cannot afford the premium, which raises suitability questions under FAIS and the Treating Customers Fairly outcomes.

A WhatsApp CRM makes these levers measurable. ORIS derives a risk score and an engagement score from each client's exchanges, lists at-risk clients in Opportunities & Risks and lets the firm target retention campaigns at segments that are drifting. The retention hub and the policy lapse entry go further; the lapse-risk guide gives a month-by-month sequence for South African brokers.

Policy lapse

A policy lapse is the termination of cover because premiums have stopped being paid. In most anglophone African and UK contracts, a missed premium starts a grace period during which cover continues and the outstanding amount can still be collected; if it is not paid, the policy lapses and cover ends, sometimes with a reinstatement option subject to conditions. In South Africa the Policyholder Protection Rules for long-term insurance require insurers to allow a period of grace for recurring premiums and to notify policyholders before cover ends; short-term policies follow their own rules and policy wording. Lapse is the main driver of poor persistency and of commission clawback on long-term business, and the first thing brokers try to prevent with WhatsApp follow-ups.

For a brokerage a lapse is a triple loss: the client is uninsured, the recurring commission stops, and on long-term business written with upfront commission the insurer may claw back part of what was paid. Preventing lapses is therefore the most valuable use of WhatsApp in Southern and East African brokerages.

The warning signs are well known: a returned debit order, a monthly premium in arrears, silence after a renewal notice, or a life change mentioned in conversation (job loss, relocation, separation). A CRM that links messages to the client record surfaces these signals; in ORIS the conversation analysis raises a High Churn Risk flag and the risk score moves, so the handler calls or messages before the grace period runs out rather than after.

Timing differs by market. In South Africa the window is between the unpaid debit order and the end of the grace period, typically a few weeks, and the PPR require the insurer to tell the policyholder about the missed premium and the consequences. In Kenya, Nigeria or Ghana the grace period is set by the policy and the regulator's market conduct rules, so the broker should check each insurer's practice. In CIMA states there is no grace period at all, as the CIMA Code entry explains. The article on lapse risk and WhatsApp for South African brokers sets out a week-by-week sequence, and the follow-ups hub gathers related guides.

POPIA

POPIA is South Africa's Protection of Personal Information Act 4 of 2013, fully enforceable since 1 July 2021 after a one-year compliance period. It sets eight conditions for lawful processing (accountability, processing limitation, purpose specification, further-processing limitation, information quality, openness, security safeguards and data subject participation), establishes the Information Regulator as supervisory authority and requires every responsible party to register an Information Officer. Section 69 deals specifically with direct marketing by unsolicited electronic communications: it is prohibited unless the data subject has consented, or is an existing customer whose details were obtained in the context of a sale, for similar products, with a chance to opt out at collection and in every message. The Act also protects juristic persons.

For a brokerage the first question is which messages count as direct marketing. A premium-reminder, a request for a claim document or a renewal notice on an existing policy is servicing, governed by the general conditions of the Act. An offer of funeral cover, a retirement annuity or an add-on the client does not hold is direct marketing under section 69, and the brokerage needs either recorded consent or the existing-customer exemption, which only covers similar products.

The Information Regulator's enforcement has focused on unsolicited marketing, so the brokerage should be able to show, for each recipient, when and how opt-in was obtained and when any opt-out was recorded. A broker CRM that stores the WhatsApp opt-in flag and the marketing opt-out separately, and excludes opted-out clients from every campaign automatically, turns that into an ordinary control.

POPIA also interacts with FAIS record-keeping: advice given on WhatsApp must be retained for at least five years under the General Code of Conduct, so the firm needs a retention policy that satisfies both regimes. Read what a broker may send a client under POPIA for a message-by-message breakdown, and the compliance hub for related rules.

RE5 regulatory exam

The RE5 is the level 1 regulatory examination for representatives of financial services providers (FSPs) licensed under South Africa's FAIS Act. It tests knowledge of the FAIS Act, the General Code of Conduct, the FIC Act and the representative's duties towards clients, not product knowledge; class-of-business training and product-specific training are separate requirements. It is distinct from the RE1, the exam for key individuals who manage or oversee an FSP. The exam is delivered by bodies appointed by the FSCA, in multiple-choice format, and a newly appointed representative must pass it within the period set by the Fit and Proper Requirements (Board Notice 194 of 2017) or stop rendering financial services. Until then, and until other competency requirements are met, the representative works under supervision.

For a South African brokerage, the RE5 is an organisational obligation. Every person who advises or sells must appear on the FSP's representative register, pass the exam within the prescribed period, complete class-of-business and product-specific training, meet continuous professional development hours each cycle, and work under supervision until the competency requirements are met. The key individual is accountable to the FSCA for all of it, and the representative register must be kept current. Namibia and Botswana set their own competency requirements through NAMFISA and NBFIRA; Kenya's IRA recognises professional qualifications such as those of the Insurance Institute of Kenya. In the UK, there is no single exam; firms certify competence under the FCA's Training and Competence sourcebook and the Senior Managers and Certification Regime.

Supervision is where WhatsApp comes in. A representative under supervision must have client interactions overseen by the key individual or an experienced representative, which is impossible when those conversations live on a personal phone. ORIS's shared inbox lets the brokerage assign conversations, see what each representative sends, and review a supervised representative's exchanges before signing off supervision; AI drafts are service suggestions approved by a human and do not constitute advice. Our guide to setting up WhatsApp Business for a South African brokerage covers the number and team setup, and the running the brokerage hub covers supervision and team workflow.

Risk score (attrition)

An attrition risk score is an indicator estimating, for each client, how likely they are to cancel, not renew or let a policy lapse in the coming months. It is built from observable signals: failed debit orders or unpaid premiums, no reply to messages, a recent complaint, a request for a competing quote, falling activity, negative language in a conversation, a renewal date approaching with no contact. Its value is not perfect prediction but ranking: a brokerage that cannot call every client calls the ones the score puts at the top first. A usable score is also explainable, so that the adviser can see why a client is rated as at risk and override the rating when reality differs from the model.

For a brokerage, the risk score is the operational side of retention. In South Africa and Namibia, where a lapsed life or funeral policy triggers commission clawback, the score identifies who to contact on the day a debit order fails. In the UK, where personal lines renewals are contested every year and Consumer Duty expects firms to act on signs of disengagement, it points to the clients to review before a comparison site does. In both markets it complements persistency and renewal rate, which measure the outcome after the fact.

In ORIS, each customer has a risk_score from 0 to 100, shown in the Risk column of the Customers & Segments table and displayed as five levels: Very Low (up to 20), Low (up to 40), Medium (up to 60), High (up to 80) and Critical above that. The score is updated by the analysis of incoming WhatsApp messages: when the classifier detects a high churn risk (HIGH_CHURN_RISK), the score rises, an opportunity of type attrition_risk is created or updated, and a "High Churn Risk Detected" notification alerts the team. The Dashboard shows the At-Risk KPI and the Highest Risk table; the Opportunities & Risks view sorts by Highest Risk and opens the conversation with a Best Next Action suggestion and the client's mood. Risk Score is also a filter for building segments. The score does not replace the adviser's judgement, and ORIS neither collects premiums nor detects failed collections on its own: that information comes from conversations and imported data.

See the lapse-risk guide and the retention and loyalty hub.

Shared inbox

A shared inbox is a single mailbox in which every WhatsApp conversation received on the brokerage's number is visible to, and workable by, several people, each signed in with their own user account. Conversations can be assigned to a handler, marked as waiting or resolved, annotated with internal notes and linked to the client record. It requires a number connected to the WhatsApp Business API, since the WhatsApp Business app only allows limited sharing across a few devices, with no assignment or central history. It is not an internal WhatsApp group, which holds no client messages, and not the personal chat of each handler, which the firm cannot see.

A shared inbox addresses three recurring problems in brokerages. Continuity: when a handler is away or leaves, their conversations remain available and a colleague picks up without asking the client to start again. Workload: inbound requests are distributed, 24-hour windows about to close are visible, and nobody discovers a claim query three days late. Evidence: every exchange is timestamped, attributed and retained, which is what the FCA expects under Consumer Duty and SYSC record-keeping, what FAIS section 18 requires in South Africa, and what a complaints handler or ombudsman will ask for.

It also requires some team discipline: someone triages and assigns each morning, a labelling convention (waiting on client, waiting on insurer, resolved) is agreed, and internal notes capture context so it does not live in one person's head.

In ORIS the inbox is tied to Customers & Segments and to the Opportunities & Risks view: a conversation in which a client mentions a house move or a new baby is flagged as an opportunity, a tense one as a risk, and a suggested draft is offered to the handler. The shared inbox guide for UK brokers covers team workflow and record-keeping in depth, and the running the brokerage hub gathers related practices.

Short-term vs long-term insurance

Short-term insurance and long-term insurance are the two legal categories of the Southern African market. Short-term, now also called non-life, covers motor, household, commercial property, liability, travel and other damage or loss policies that run for a year or month to month. Long-term, or life, covers life, funeral, credit life, disability, income protection and savings policies that run for years and lapse if premiums stop. The names come from South Africa's Short-term Insurance Act and Long-term Insurance Act of 1998; the Insurance Act of 2017 introduced the non-life and life labels, but brokers, insurers, FAIS licence categories and product agreements still use the older terms. Namibia, Botswana, Eswatini and Lesotho use the same vocabulary under their own statutes, while Kenya and Nigeria split the market into general and life business.

The split shapes a brokerage's operations. A FAIS licence lists the categories and sub-categories the FSP may advise on, and representatives must hold the regulatory exam and class-of-business training for each; a brokerage licensed for short-term personal lines cannot simply start selling funeral cover. Commission works differently: regulated and recoverable on recurring-premium life business, capped as a percentage of premium on short-term business. Policyholder Protection Rules exist in two versions, one for each category, and claims practices differ: a motor claim involves assessors and repairs, a funeral claim involves a death certificate and a payout within days.

Servicing follows two rhythms. On the short-term side, the work is renewals, risk updates and claims: a reminder before renewal, an annual cover review, a quick response when a client reports an accident. On the long-term side, the work is persistency: failed debit orders, beneficiary updates, policy anniversaries, and keeping the client engaged so that a policy written two years ago does not fall away quietly.

A brokerage that runs both books on WhatsApp should separate its routines by policy type rather than by client. In ORIS, policy type (life, health, auto, home, travel, business) is a segment filter and a template variable, so the motor renewal reminder and the life premium reminder are different campaigns with different Meta-approved templates and timing. Our lapse-risk guide covers the long-term side, and the country pages summarise each regulator.

Treating Customers Fairly (TCF)

Treating Customers Fairly (TCF) is an outcomes-based regulatory framework requiring financial services firms to show that fair treatment of customers is embedded in their culture and operations. It originated with the UK's Financial Services Authority and was adopted in South Africa by the Financial Services Board in 2011; it remains the backbone of the FSCA's market conduct supervision and is reflected in the FAIS General Code of Conduct and the Policyholder Protection Rules. TCF sets six outcomes: customers are confident the firm's culture is fair; products are designed for identified customer groups; customers receive clear information before, during and after the sale; advice is suitable; products perform as the firm led customers to expect; and customers face no unreasonable post-sale barriers to changing product, switching provider, claiming or complaining. The outcomes apply to brokers as much as to insurers.

In South Africa, every FSP is expected to be able to explain how it delivers each outcome and to produce evidence, from product selection to complaints handling; the FSCA's conduct standards and the planned Conduct of Financial Institutions framework build on the same six outcomes. NAMFISA, NBFIRA, Kenya's IRA and Nigeria's NAICOM have adopted similar market conduct principles with local variations. In the UK, TCF was superseded by the Consumer Duty in 2023, which demands harder evidence of outcomes; EU brokers work under IDD, which pursues comparable goals through documented processes rather than outcome monitoring.

For a brokerage on WhatsApp, three outcomes are directly in play. Outcome 3, clear information, requires messages in plain language, in the client's language where possible, with no ambiguous promises on cover or price. Outcome 5, products and service performing as expected, means questions, endorsement requests and claims received on WhatsApp must be handled within measurable times. Outcome 6, no unreasonable barriers, means a client who writes "I want to cancel" or "I want to complain" must get a reply and a procedure, not silence because the message sat on a representative's personal phone.

ORIS supports that evidence: a shared inbox with per-customer history, AI classification of incoming messages so that complaints and cancellations surface, visible response times, and CSV export for TCF reporting. See the POPIA and WhatsApp guide for the consent side, and the compliance hub for the wider framework.

WABA (WhatsApp Business Account)

A WABA (WhatsApp Business Account) is the account inside a Meta Business portfolio that groups everything a business uses on the WhatsApp Business Platform: one or more phone numbers with their display names, message templates and their approval status, messaging limits, billing and privacy settings. Business verification and official-business status apply at WABA level, while the quality rating is measured per phone number. A WABA is created during Embedded Signup or manually in Business Manager. It belongs to the business, not to the software vendor connected to it, which only holds delegated access that the business can revoke.

For a brokerage the WABA question comes down to ownership and contents. The Meta Business portfolio and the WABA must be in the firm's name, with at least two administrators (a principal plus a director or operations lead), so that nothing depends on one individual or on a supplier. A vendor such as ORIS operates as an authorised application on the WABA; the brokerage can remove that access and keep its number, templates and billing history.

The WABA holds the templates. A firm serving several markets or languages manages one template set per language, since the language code is part of a template's identity. It also holds the numbers: a multi-branch brokerage can attach one number per branch to the same WABA and keep a single governance, or run separate WABAs when the branches are distinct legal entities, as is common with group structures in South Africa or Kenya.

Business verification happens at portfolio level and governs the climb through messaging-limit tiers and the display of the firm's name instead of a bare number. It requires official documents (company registration, proof of address, sometimes a utility or phone bill) and takes from a few days to several weeks. The South African setup guide lists the documents accepted in practice, and the quality rating entry explains what is measured per number.

WhatsApp Business API (Cloud API)

The WhatsApp Business API, now branded WhatsApp Business Platform and delivered through Meta's hosted Cloud API, is the interface that lets a business connect a WhatsApp number to software rather than to a handset. It provides approved template sending, inbound messages through webhooks, delivery and read statuses, buttons and interactive messages, and multiple users on one number. It has no user interface of its own: it is used through a CRM or messaging platform, or a custom integration. It differs from the free WhatsApp Business app, which is limited to a handful of devices and offers no automation, and from the former On-Premises API, which Meta has retired in favour of the Cloud API.

The decision for a brokerage is organisational rather than technical: at what size and volume does the WhatsApp Business app stop being enough. The usual signs are a book that several account handlers must service, premium reminders sent by the hundred each month, the need to keep conversations when a handler leaves, and the obligation to retrieve an exchange for a client file, a complaint or a regulator's visit.

With the API, the number belongs to the firm and sits in a WhatsApp Business Account attached to its Meta Business portfolio. Conversations land in the chosen tool, where they can be assigned, annotated and tied to the client record. Reminders go out as templates within Meta's messaging limits, and replies come back classified. In return, Meta charges for each business-initiated message according to its category, the business must be verified through its Meta portfolio, and templates must be approved before use.

ORIS is built on the Cloud API: number connection through Embedded Signup, a shared inbox, campaigns from approved templates, AI classification of replies, suggested drafts and rule-based auto-reply with human escalation. The site's comparison of the app and the API sets out the cases where the app remains the right choice, and the South African setup guide walks through a first deployment.

WhatsApp message template

A WhatsApp message template is a pre-written message submitted to Meta through the WhatsApp Business Platform and approved before use. It is the only kind of message a business may send on its own initiative, meaning outside a customer service window opened by the client. Each template has a name, a language, a category (marketing, utility or authentication), a body with numbered variables, and optionally a header, footer and buttons (quick replies, URL, call). Meta reviews the content, may reject it, and keeps monitoring it afterwards: a template that draws blocks or reports can be paused or disabled. Since Meta moved to per-message pricing in 2025, the category also sets the price of each send.

For a brokerage, templates carry all outbound communication: premium reminders, debit-order failure notices, document requests, renewal notices, claim updates, policy anniversaries and cover-review invitations. The category decision is the sensitive one. A message about an existing policy that does not promote a purchase is utility; any promotional wording pushes Meta to classify it as marketing, which costs more and is monitored more closely. Meta sometimes recategorises a utility submission as marketing during review; the fix is to strip the sales language and resubmit.

Variables ({prenom}, {contrat}, {montant}, {date}, {conseiller} in this site's templates) personalise the message while keeping the approved wording fixed. Quick-reply buttons ("Paid", "Call me", "Send documents") are the most reliable way to get an answer, and an answer opens a 24-hour window for free-form conversation.

In ORIS, templates are created and synchronised with Meta from the WhatsApp screen, with the approval status shown (Awaiting Meta approval, Template Rejected); a campaign only goes out with an approved template to opted-in clients. The template library on this site offers variants by tone and timing, and the South African setup guide explains how the first ten templates get approved.

WhatsApp opt-in

A WhatsApp opt-in is a person's explicit agreement to receive messages from a business on WhatsApp. The WhatsApp Business Platform policies require a business to obtain it before sending any business-initiated message, which in practice means any template sent outside a customer service window opened by the client. Meta expects the opt-in to be clear, to name the business and to state that messages will arrive on WhatsApp; it may be collected on a website form, in a branch, over the phone, through a tick box in an application form or inside a conversation. It is separate from the marketing consent required by POPIA, PECR or the GDPR, although brokerages usually collect both at once.

Two layers of rules meet here. Meta enforces opt-in through behaviour: a number that sends templates to people who did not expect them collects blocks and reports, its quality rating drops and its messaging limit can be reduced. The law enforces consent for direct marketing (section 69 of POPIA in South Africa, PECR regulation 22 in the UK, ePrivacy rules in the EU) but generally allows servicing messages about an existing policy on other grounds.

A brokerage therefore tracks two things: a channel opt-in ("you may contact me on WhatsApp about my policies") and a marketing opt-in ("you may send me offers"). In ORIS the WhatsApp Opt-In field on the client record gates every campaign send, and segments can filter on it, so a client without a recorded opt-in is never targeted.

The easiest moment to collect it is onboarding or the first inbound message: the client writes to the brokerage, the 24-hour window opens and the adviser asks whether the client agrees to receive premium notices and documents on this channel. The reply sits in the conversation with a timestamp, which is the proof. Welcome message templates include that question, and the South African setup guide covers the number, opt-in and templates together.

WhatsApp quality rating

The quality rating is the score Meta assigns to every phone number connected to the WhatsApp Business Platform. It reflects recipient feedback over the previous seven days: blocks, reports and the reasons people give when they block. It has three levels, shown as green (high), yellow (medium) and red (low) in Meta Business Manager and as High, Medium, Low or Not Rated in ORIS. A low rating first triggers a warning, then can reduce the number's messaging limit (the ceiling of business-initiated conversations per 24 hours, typically 1,000, 10,000 or 100,000 unique recipients) to a lower tier and, if it persists, restrict the number. Templates carry their own quality score and can be paused or disabled independently of the number.

For a brokerage the quality rating is the reputation of its business number, and it is shared: one poorly targeted campaign by one account handler slows down the premium reminders of the entire firm. Meta does not publish the formula, but the known drivers are consistent: messages to people without a recorded opt-in, high frequency, promotional wording in utility templates, no opt-out path and sends at unsuitable hours.

The protective rules are straightforward. Send marketing campaigns only to clients who have explicitly agreed to offers, and rarely more than once or twice a month. Keep servicing messages (renewals, documents, claims) as short, factual utility templates. Watch the block rate after every campaign and stop one that is going wrong rather than letting it run. Respect a sending window that fits the country and client base; ORIS applies a send window and a daily limit per campaign to smooth volumes.

The rating also interacts with messaging-limit tiers: a new number starts on a low tier that Meta raises as volume and quality are demonstrated, and business verification speeds that up. A brokerage that launches a first campaign to its whole book hits the ceiling; ramping up over a few weeks works better. The WhatsApp Business hub follows Meta's rule changes, and the South African setup guide explains how to warm up a new number.

Book a demo