Kommo for insurance brokers? Wrong tool — 8 BMS alternatives

Bottom line: why Kommo mismatches UK insurance broking + FCA regulation

Direct answer: A UK insurance broker's real workflow is a 6-stage policy-lifecycle — client enquiry + fact-find → quotation across insurer panel → policy bind + documents → mid-term adjustments → annual renewal → claims support. Kommo's sales-pipeline model with deal stages + sales bots is wrong tool category — insurance broking is policy-administration + FCA-regulated finance handling.

Why the mismatch is structural, not just cosmetic:

• Wrong operational model. Kommo optimized for teams where sales pipeline (lead → prospect → deal → won/lost) is primary work structure. Insurance broking has policy inception + ongoing policy administration + annual renewal cycle + claims support + CASS 5 client money handling — none of which Kommo's deal stages model.
• Broker Management System (BMS) is the operational core. UK broker operations run on Acturis, Open GI, SSP, or IBS. These integrate with insurer panel via Polaris or direct insurer APIs. Kommo has no BMS + no insurer feed integration.
• FCA financial promotion rules apply broadly. Per FCA Handbook, any invitation or inducement to engage in insurance contract is financial promotion. Sending 'your motor insurance quote is £450/year' via Kommo WhatsApp without FCA-approved promotion approval risks regulatory breach.
• Client Money Handling (CASS 5). Brokers holding client money must comply with FCA CASS 5 — separate client bank account, monthly reconciliation, statutory trust rules. BMS handles this; Kommo doesn't touch client money.
• GDPR + PECR consent. Marketing messages need PECR consent; transactional messages (renewal reminders, mid-term adjustment notices) can be sent under legitimate interest or contract performance.

The practical outcome: no UK insurance broker should use Kommo as primary tool. The alternatives below split into broker management systems (BMS handling policy administration + insurer integration + client account) and horizontal WhatsApp BSPs (for FCA-compliant administrative client messaging).

The 8 alternatives: 6 broker management systems + 2 WhatsApp Business Platform

Direct answer: 6 broker management systems (BMS) — Acturis, Open GI, SSP, Insurance Broking Systems (IBS), Applied Epic (US), Vertafore AMS360 (US), HawkSoft (US), EZLynx (US), NowCerts (US) — combine policy administration + insurer integration + client account + FCA-compliant workflow. 2 WhatsApp BSPs — WATI, Callbell — for administrative client comms within FCA rules.

Bucket 1 — UK broker management systems (pricing typically quoted on request):

• Acturis (acturis.com): UK-dominant BMS used by many UK independent brokers + broker networks. Multi-insurer quote engine + policy administration + accounting + reporting.
• Open GI (opengi.co.uk): UK BMS with strong personal lines focus.
• SSP (sspworldwide.com): UK BMS + insurance software. Personal + commercial lines.
• Insurance Broking Systems (IBS) (ibsuk.net): UK BMS for smaller independent brokers.

US broker management systems (for US brokers reading this teardown):

• Applied Epic (appliedsystems.com/epic): US-dominant BMS for mid-to-large independent agencies.
• Vertafore AMS360 (vertafore.com): US-focused agency management system.
• HawkSoft (hawksoft.com/pricing): US small-to-mid agency BMS with public pricing typically ~$150-300/user/mo.
• EZLynx (ezlynx.com): US small agency BMS.
• NowCerts (nowcerts.com): US agency management system.

Bucket 2 — Horizontal WhatsApp Business Platform tools:

• WATI (wati.io/pricing): Growth ~$29/mo (~£23), Pro ~$79/mo (~£62). WhatsApp inbox for client comms — administrative messages only within FCA financial promotion rules.
• Callbell (callbell.eu/pricing): ~€30/user/mo (~£26). EU-hosted for UK GDPR-strict setups.

Practical stacking pattern: Acturis or Open GI (BMS) + WATI Growth (~£23/mo) for WhatsApp administrative client comms (appointment reminders, document requests, renewal date reminders — NOT specific price quotes without FCA approval). Combined stack ~£300-1,500+/mo depending on BMS tier. Kommo Base $15/user × 4 users = $60/mo (~£47) covers chat but no broker workflow — additive without replacement value.

How Kommo's sales-pipeline model specifically breaks for insurance broking

Direct answer: Kommo's core value proposition — 'lead → prospect → deal → won/lost pipeline stages with sales bot automation' — technically applies to insurance sales conversion. But insurance broking operations are fundamentally about policy administration + annual renewal + claims support over multi-year client relationships, not one-shot deal closes. Kommo covers ~10-15% of the operational surface at best.

Where Kommo's design specifically breaks for insurance brokers:

1. Deal stages don't cover the workflow. Kommo pipeline stages fit: new lead → contacted → quotation → policy bound. Fine for policy inception piece. But broker operations continue: mid-term adjustments (MTAs) + annual renewal (typically 12 months later + every year after) + claims support + policy amendments. Kommo has no ongoing policy-administration workflow.

2. No insurer panel integration. Broker value proposition is comparing quotes across insurer panel (Aviva, AXA, Zurich, Allianz, LV, Direct Line for Business, etc). UK BMS integrates via Polaris; Kommo has zero insurer integration.

3. No CASS 5 client money handling. Brokers holding client money must maintain separate client bank account per FCA CASS 5. BMS handles this; Kommo has no financial handling infrastructure.

4. FCA financial promotion compliance. Any message with specific premium quote is financial promotion requiring FCA approval. Kommo WhatsApp is not FCA-approved channel for financial promotions without additional approval workflow.

5. No renewal transparency compliance (GIPP). FCA GIPP (General Insurance Pricing Practices) which came into force January 2022 requires consumer renewal notices with last year's premium disclosed + shopping-around encouragement + renewal price no higher than equivalent new-business price. BMS handles this compliance automatically; Kommo has zero GIPP-compliant renewal capability.

Practical implication: if reason for evaluating Kommo is 'we need better WhatsApp for client comms,' get WATI Growth (~£23/mo) — dedicated WhatsApp BSP without unnecessary sales-CRM overhead. Fund BMS separately for actual broker workflow.

Stage 1 — Client enquiry + fact-find (compliant capture)

Direct answer: FCA rules require appropriate fact-find covering client circumstances + needs + priorities before recommending insurance. BMS structures fact-find in policy record; WhatsApp captures initial enquiry but formal fact-find belongs in BMS.

Stage 1 scorecard:

Acturis, Open GI, SSP, IBS (UK); Applied Epic, Vertafore AMS360, HawkSoft, EZLynx, NowCerts (US): 🟢 fact-find template + client record structure + FCA/US-equivalent-compliant data capture.

WATI, Callbell: 🟢 for initial enquiry chat channel — client WhatsAppes 'I need buildings insurance for my rental property' — chatbot flow captures name + property details + coverage needs.

Kommo: 🟡 workable for basic WhatsApp enquiry capture into sales pipeline but no formal fact-find structure + no compliance-appropriate documentation.

Winner for Stage 1: BMS for structured fact-find + client record; WhatsApp BSP for initial enquiry conversation.

Stage 2 — Quotation across insurer panel (multi-insurer quote engine)

Direct answer: Broker value proposition is comparing quotes across insurer panel. UK BMS integrates with Polaris + individual insurer feeds. Kommo has no insurer integration + no quote engine.

Stage 2 scorecard:

Acturis, Open GI, SSP: 🟢 multi-insurer quote engine via Polaris + direct insurer APIs. Personal lines + commercial lines.

Applied Epic, HawkSoft, EZLynx: 🟢 US equivalent with US insurer integration.

WATI, Callbell: 🟡 CANNOT send specific quote figures without FCA financial promotion approval. Workable for: 'Your quotes are ready — please visit [portal / office / call us on [number]]'.

Kommo: 🔴 no quote engine, no insurer integration.

FCA financial promotion note critical here: any message with specific premium quote is financial promotion. Per FCA rules, financial promotions require approval by authorised firm before communication. Kommo WhatsApp sending 'Your motor quote is £450 with Aviva' without prior approval is regulatory breach.

Winner for Stage 2: BMS uniformly for quote engine; WhatsApp BSP for notification only.

Stage 3-4 — Policy bind + mid-term adjustments (ongoing administration)

Direct answer: Policy binding involves final quote + payment + document generation. Mid-term adjustments (MTAs) generate premium adjustments + insurer notifications. BMS handles the full workflow with CASS 5 client money handling. Kommo has zero policy administration capability.

Stage 3 scorecard (policy bind):

Acturis, Open GI, SSP, IBS: 🟢 policy bind workflow — client confirms quote, payment collected, insurer notified electronically, policy documents generated (schedule + wording + IPID + statement of demands + needs).

WATI, Callbell: 🟢 for administrative delivery — 'Your policy is now active. Documents attached: [portal link]'.

Kommo: 🔴 no policy binding, no document generation, no CASS 5.

Stage 4 scorecard (MTAs):

BMS uniformly handles MTAs — client requests change, broker processes in BMS, insurer notifies premium adjustment, updated documents generated.

WATI, Callbell: 🟢 for MTA request capture + administrative confirmation.

Kommo: 🔴 no MTA workflow, no BMS integration.

Winner for Stages 3-4: BMS uniformly. WhatsApp BSP for administrative delivery only.

Stage 5 — Annual renewal (FCA GIPP transparency, retention challenge)

Direct answer: Annual renewal is where broker retention is won or lost. FCA GIPP transparency rules require renewal notices with last year's premium + shopping-around encouragement. BMS handles renewal workflow with rebroking across insurer panel; Kommo has no renewal capability.

Stage 5 scorecard:

Acturis, Open GI, SSP, US BMS: 🟢 renewal workflow — auto-generated renewal list ~60 days before expiry, rebroking across insurer panel, renewal terms comparison, renewal invitation with FCA-compliant transparency.

WATI, Callbell: 🟢 for renewal reminder delivery — 'Your policy renews [date]. Please review your renewal terms in the portal: [link]'.

Kommo: 🔴 no renewal workflow, no GIPP compliance.

FCA GIPP note: per FCA GIPP in force January 2022, consumer renewal notices must include last year's premium + encourage shopping around. Renewal price for renewing customers must be no higher than equivalent new-business price for the same policy. BMS handles this compliance automatically; Kommo doesn't.

Winner for Stage 5: BMS uniformly for renewal workflow + FCA compliance; WhatsApp BSP for renewal reminder delivery.

Stage 6 — Claims support (moment where broker value is proven)

Direct answer: Claims are where clients most need broker support. Broker guides client through insurer's claims process, chases progress, escalates disputes. BMS records claim history; WhatsApp is practical client-facing channel for claim status updates.

Stage 6 scorecard:

Acturis, Open GI, SSP, US BMS: 🟢 claim log per policy — first notification of loss (FNOL) capture, insurer claim reference, progress notes, financial settlement tracking.

WATI, Callbell: 🟢 for client-facing claim status updates.

Kommo: 🔴 no claim workflow, no BMS integration.

Winner for Stage 6: BMS for claim record; WhatsApp BSP for client-facing claim status delivery.

Situational winners by UK insurance broker profile

Direct answer: Sole trader broker → Acturis or Open GI + WATI. Small independent broker (2-5 staff) → Acturis or Open GI or SSP + WATI Growth. Mid-size (5-20 staff) → Acturis or Open GI + WATI Pro or Callbell. Network member broker → BMS mandated by network + WhatsApp BSP. Never Kommo as primary for any broker profile.

Profile A — Sole trader broker (1 person, personal lines focus)

• Winner: IBS or Open GI entry-tier BMS + WATI Growth (~£23/mo).
• Total stack: ~£300-600/month depending on BMS tier.
• Don't buy Kommo: ~£12/mo for 1 user delivers WhatsApp + sales pipeline you don't need + zero FCA compliance.

Profile B — Small independent broker (2-5 staff, personal + commercial mix)

• Winner: Acturis or Open GI + WATI Growth (~£23/mo).
• Acturis widely-adopted in UK market; Open GI strong on personal lines.
• Total stack: ~£500-2,000/month depending on BMS tier.

Profile C — Mid-size independent broker (5-20 staff)

• Winner: Acturis or SSP + WATI Pro (~£62/mo) or Callbell (~£26/user/mo scaled).
• Total stack: ~£1,500-5,000/month.

Profile D — Network member broker (e.g., Broker Network, Cobra, Movo)

• Winner: BMS mandated by network + WhatsApp BSP + network-provided compliance support.

Profile E — Specialty broker (commercial risk, high net worth, specific trade)

• Winner: Acturis or specialty BMS + WATI Pro or Callbell + specialty-specific integrations.

Common mismatch (avoid): buying Kommo because 'we need WhatsApp CRM' — Kommo delivers sales pipeline + WhatsApp inbox but zero FCA compliance, zero BMS, zero client money handling. For WhatsApp alone, WATI at ~£23/mo is cheaper and more focused. Fund BMS first; add WhatsApp BSP second.

FCA compliance disclaimer: this teardown is editorial guidance, not FCA compliance advice. UK insurance brokers should confirm FCA financial promotion rules + FCA CONC + CASS 5 client money handling + FCA GIPP + FCA ICOBS + FCA COBS compliance with qualified compliance officer + broker network compliance support. Verify current FCA rules at handbook.fca.org.uk. No undisclosed commercial relationship with any vendor listed.