Kenyan WhatsApp Automation 2026: M-Pesa Daraja, eTIMS + Kommo Alternatives

Why Kommo is often a poor fit for Kenyan small businesses

Kommo is a capable multi-channel messaging CRM with a global customer base. Three gaps limit its practical fit for most Kenyan SMBs.

No KES-native billing or KRA-compliant invoicing. Kommo bills in USD. Kenyan businesses claiming VAT input credit (16% standard rate) or reporting to KRA need vendor invoices in KES with a valid PIN. More importantly, Kommo does not integrate with the Kenya Revenue Authority Electronic Tax Invoice Management System (eTIMS), the mandatory electronic invoicing system that replaced the older Electronic Tax Register requirement in 2024. Businesses issuing invoices below the eTIMS threshold still need documented KES receipts.

Weak M-Pesa integration path. M-Pesa (Safaricom Kenya) is the dominant retail payment rail — Central Bank of Kenya statistics report over 90% of adult Kenyans using mobile money regularly. WhatsApp automation that cannot generate M-Pesa payment prompts inline via Safaricom's Daraja API or a gateway partner misses the primary conversion mechanism for consumer-facing Kenyan businesses.

Timezone and language support. Kommo operates on non-EAT hours for support. Kenya-facing BSPs handle Swahili/English code-switching in customer conversations natively — Kenyan customer messages typically alternate between the two, plus common Sheng constructs (mia moja, dala, poa), and pure English NLU misses this.

Where Kenya-specific requirements matter, a regional BSP or Africa-native platform is typically a better operational fit.

WhatsApp Business Platform providers with Kenya presence

Africa's Talking — Kenya-headquartered pan-African CPaaS. WhatsApp, SMS, USSD (still relevant for feature-phone reach in rural Kenya), and voice. Prices quoted in USD or KES depending on region. KES invoicing available. Strong developer community and documentation. Popular with Kenyan startups and mid-market businesses.

Twilio — global CPaaS with WhatsApp Business Platform access. Pay-per-message pricing with no fixed monthly BSP fee. USD billing. Popular with Kenyan businesses that have in-house developers and want to combine WhatsApp with SMS and voice under one API.

Infobip — enterprise messaging platform with strong Africa presence including offices covering East Africa. WhatsApp, SMS, voice, email. Custom pricing per volume. Suits banks, telecom, insurance and mid-market retail.

MessageBird (Bird) — European CPaaS with East Africa reach. Suits growing businesses needing omnichannel messaging beyond WhatsApp.

360dialog — European BSP with global availability including Kenya. Predictable monthly platform fee plus Meta conversation charges. Direct API access.

Gupshup — one of the largest global conversational messaging platforms with active Africa presence. Enterprise pricing quoted per volume; suits established mid-market Kenyan businesses.

All are official Meta Business Solution Providers or partners. Verify current partnership status at developers.facebook.com/docs/whatsapp/ before contracting. Africa's Talking is worth particular attention as a Kenya-founded platform with deep local integration knowledge.

Kenya-specific evaluation criteria that generic reviews miss

Beyond standard feature comparison, five criteria specifically matter for Kenyan SMBs:

KRA eTIMS integration. The Kenya Revenue Authority Electronic Tax Invoice Management System (eTIMS) became the mandatory electronic invoicing system in 2024, replacing older ETR requirements. Businesses above the VAT threshold must issue eTIMS-compliant invoices for all sales. When payment is collected via WhatsApp automation (M-Pesa link, card, cash on delivery), the business must still issue an eTIMS invoice. Few global BSPs integrate with eTIMS natively — integration typically requires custom development or a Kenyan accounting software with eTIMS API.

M-Pesa Daraja API integration depth. Safaricom's Daraja API provides the official developer interface to M-Pesa. Three integration levels: (1) manual M-Pesa Till or Paybill number shared as text (no automation, no reconciliation), (2) STK Push (Sim Toolkit Push) triggered via Daraja API — customer receives an M-Pesa prompt on their phone and confirms payment (best UX, requires Daraja app credentials), (3) payment link generated via gateway partner (Flutterwave, Kopokopo, DPO Pay) — customer taps link, completes payment, gateway webhook confirms. Level 2 (STK Push) is the gold standard for Kenya. Level 3 is the practical baseline via a gateway.

Swahili/English/Sheng code-switching. Kenyan customer messages typically mix Swahili and English, plus urban Sheng constructs. The chatbot NLU should handle common Kenyan constructs (mia moja, dala, poa, sawa, karibu). WhatsApp Business Platform templates support Swahili (sw) and English (en) as separate template languages; the chatbot flow builder needs to handle both plus code-switching.

Data Protection Act 2019 posture. The Data Protection Act 2019 (enforced by the Office of the Data Protection Commissioner, ODPC) establishes consent requirements, purpose limitation, data controller/processor registration, and cross-border transfer safeguards. Vendors should provide a Data Processing Agreement stating their role and compliance posture. Sensitive personal data requires additional safeguards. ODPC actively enforces — several fines issued in 2023-2024.

Meta conversation pricing for Kenya region. WhatsApp Business Platform charges by conversation category and billing region. Kenya is in the Africa Other tier — approximately USD 0.0387 per Marketing conversation and USD 0.0089 per Utility conversation as of 2025 (verify at developers.facebook.com/docs/whatsapp/pricing for the current fiscal year).

SME segments and platform choice

Kenya's small business landscape spans jua kali micro-enterprises, salon and hospitality SMEs, wholesale traders, medium enterprises, and large corporates. WhatsApp automation choice tracks with volume and integration depth.

Micro (single owner, up to 500 conversations/month). WhatsApp Business App (free) is usually sufficient. Manual M-Pesa Till or Paybill number sharing works. Migration to API-based automation via BSP is premature.

Small SME (1,000–15,000 conversations/month). API required. Africa's Talking or 360dialog entry tier for cost-controlled automation; Twilio if in-house developer is available for Daraja API integration. Payment link via Flutterwave, Kopokopo or direct Daraja STK Push. eTIMS integration usually via accounting software.

Medium enterprise (15,000+ conversations/month). Infobip, Africa's Talking Business, or Gupshup for enterprise account management. Deeper CRM integration (Zoho, Salesforce, HubSpot). Native eTIMS integration through a dedicated provider.

Large enterprise (banks, telecom, insurance). Direct Meta partnership plus Infobip or Gupshup. Full omnichannel — WhatsApp + SMS + USSD (still important for feature phones) + voice.

Common pitfalls Kenyan SMBs hit with WhatsApp automation

Four recurring patterns that damage account health or waste spend:

Using the owner's personal WhatsApp for business. Mixes personal and business context, no audit trail, no multi-agent access, single point of failure when the employee leaves. Also creates Data Protection Act 2019 exposure — customer data on personal devices without documented purpose or retention policy.

Skipping eTIMS invoice on WhatsApp-collected payments. When payment is collected via M-Pesa link or STK Push sent through WhatsApp, the business is still obligated to issue an eTIMS invoice under KRA rules (if above the VAT threshold or otherwise required). Failing to issue creates tax exposure and audit risk. The automation should trigger eTIMS invoice generation from the accounting system after payment confirmation.

Miscategorizing Marketing as Utility. Meta charges lower for Utility category than Marketing. Some SMBs categorize promotional broadcasts as Utility to save cost — Meta detects this and can suspend the business account.

No opt-out for Marketing conversations. WhatsApp policy requires users can unsubscribe easily. Without opt-out flow, the business number is at risk of throttling or suspension based on user report volume.

Decision matrix: which platform for which use case

The choice depends on business model, existing tech stack, and volume tier:

Small SMB needing simple automation with Daraja STK Push. Africa's Talking or Twilio — both have well-documented M-Pesa Daraja integration paths and Kenyan developer community support.

Developer-led custom integration with M-Pesa. Twilio or Africa's Talking — API-first with predictable per-message pricing. Direct Daraja API integration for STK Push flow.

Enterprise volume (banks, telecom, insurance). Infobip or Gupshup — enterprise account management, custom pricing, dedicated support.

Omnichannel needs (WhatsApp + SMS + USSD for feature-phone reach). Africa's Talking — pan-African USSD platform in addition to WhatsApp; still relevant for rural Kenyan customer segments.

Multi-agent sales team (wholesale, real estate, high-ticket B2B). WATI or Sleekflow shared inbox with agent assignment and conversation ownership.

BossBot is another option to evaluate — Kenya-market-aware WhatsApp automation with M-Pesa Daraja STK Push integration, KRA eTIMS invoice trigger via accounting integration, Data Protection Act 2019 posture, multi-agent inbox, and Swahili/English/Sheng code-switching in the NLU. Public pricing at bossbot.uk/pricing. Free 7-day trial without payment method.