Skip to content
Tubonge logoTubonge WhatsAppBiashara Yako, Simu MojaChat
Kenya guide Last updated 2026-11-05

WhatsApp CRM with M-Pesa for Kenyan businesses

For many Kenyan businesses, the sale does not end when the customer says yes. It ends when the M-Pesa message arrives, the payment is confirmed, and the order moves forward. If those steps live in a different app from the conversation, someone has to reconcile them by hand.

A WhatsApp CRM with M-Pesa is meant to close that gap. This guide explains what the workflow should look like, what to ask a vendor, and which parts of the Tubonge M-Pesa workflow are confirmed today.

Key takeaways

  • The value of M-Pesa inside a CRM is not the payment itself. It is keeping the payment confirmation attached to the customer, conversation and deal.
  • Ask for a live demonstration of the payment flow, not just an API reference or a feature tick.
  • Tubonge lists M-Pesa payment workflows as a verified feature. The exact STK push, Paybill/Till and reconciliation details are still being confirmed with the owner.
  • Meta message fees and M-Pesa transaction charges are separate costs. Budget for both.
  • Start with the payment flow you actually use today, then check whether the CRM supports it without manual work.

What a WhatsApp CRM with M-Pesa should mean

A WhatsApp CRM combines a shared inbox, contact records, conversation history and a sales pipeline. Adding M-Pesa should connect the payment event to that record, so an agent can see that a customer paid, what they paid for, and what should happen next.

That can happen in a few ways. A CRM may initiate a payment request, receive a confirmation callback from M-Pesa, match the payment to an order or invoice, and update the deal stage. The useful version removes a manual step and leaves an audit trail.

  • The payment is linked to the right customer, not just a phone number in a statement.
  • The agent can see the status without asking a colleague to check a separate phone.
  • The order or deal moves forward automatically, or with one clear action.
  • There is a record of who requested the payment and when it was confirmed.

How M-Pesa payments usually work inside a chat

M-Pesa integrations are built on Safaricom's Daraja API. The exact product depends on whether you are collecting money, sending money or reconciling a Paybill or Till number. A CRM may support one or several of these flows.

General M-Pesa integration patterns. Not every CRM supports every flow.
FlowWhat it doesWhat to confirm with the vendor
STK pushSends a payment prompt to the customer's phone from inside the conversation.Is it live in the CRM, which shortcode is used, and what happens if the customer ignores the prompt?
Paybill / Till (C2B)Customer pays using your business number and account reference.Can the CRM receive the confirmation callback and match it to the right customer?
B2C payoutsBusiness sends money to a customer, for example a refund or payout.Is this supported, and what approval controls exist?
Manual confirmationAn agent checks the M-Pesa message or statement and marks the order paid.What is the audit trail, and who can change a payment status?

What to check before you buy

  • Ask for a live demonstration with a real test number. A screenshot is not a workflow.
  • Confirm whether the integration is native or depends on a third-party middleware.
  • Ask how a payment is matched when the customer pays from a different phone number.
  • Check who owns the Daraja credentials and what happens if you leave the vendor.
  • Confirm how refunds, failed payments and duplicate confirmations are handled.
  • Ask where the payment record is stored and who can export it.
  • Check the reconciliation report. Can your accountant use it without rebuilding it in Excel?

What Tubonge does today

Tubonge is a WhatsApp CRM for Kenyan SMEs with a shared inbox, broadcasts, sales pipeline, M-Pesa payment workflows and AI replies, starting from KSh 3,500/month. M-Pesa payment workflows are a verified feature.

The exact feature set is still being confirmed with the owner. That includes which M-Pesa flow is live (STK push, Paybill, Till or a combination), how automatic reconciliation works, and which shortcode or paybill number public pages should reference.

Not confirmed yet

Do not assume a specific M-Pesa feature from a generic claim. Ask Tubonge for a live demonstration of the flow you need, and confirm the Daraja credentials, reconciliation process and audit trail before you commit.

A simple workflow for a Kenyan shop

The goal is not to remove the human from the sale. It is to remove the copy-paste step between the conversation, the payment and the order record.

  1. 1A customer asks about a product or service on WhatsApp.
  2. 2The agent confirms the price and delivery details in the shared inbox.
  3. 3The agent sends an M-Pesa payment request or shares the Paybill/Till details.
  4. 4The customer pays, and the confirmation is received by the CRM or entered by the agent.
  5. 5The payment is matched to the customer and order, and the deal moves to paid.
  6. 6The agent sends the receipt or next-step message, and the order enters fulfilment.

Costs to budget

  • The CRM subscription. Tubonge starts at KSh 3,500/month.
  • Meta WhatsApp message fees, which depend on message category and volume. See the WhatsApp Business API guide for the October 2026 rules.
  • M-Pesa transaction charges, which depend on the Safaricom tariff and the payment product you use. Check the current Safaricom tariff; do not estimate from old blog posts.
  • Any setup or integration fee charged by the vendor.
  • Staff time for reconciliation if the integration is not automatic. This is a real cost even when it does not appear on an invoice.

Common mistakes

  • Keeping the business WhatsApp on a personal phone, so only one person can see the payment conversation.
  • Reconciling M-Pesa manually from a personal message inbox with no audit trail.
  • Assuming a payment API integration is the same as a working reconciliation workflow.
  • Ignoring failed, reversed or duplicate payments in the design.
  • Mixing marketing messages and payment confirmations without checking Meta's template rules and fees.

WhatsApp CRM with M-Pesa for Kenyan businesses: frequently asked questions

Does Tubonge integrate with M-Pesa?
Tubonge lists M-Pesa payment workflows as a verified feature. The exact flows (STK push, Paybill, Till, reconciliation) are still being confirmed with the owner. Ask for a live demonstration of the specific flow your business uses.
Can I confirm M-Pesa payments inside the WhatsApp chat?
That is the intended workflow: keep the payment conversation and confirmation next to the customer record. Confirm the exact screens and automation with Tubonge before you rely on it.
Do I need a Paybill or Till number?
It depends on how you collect money today. A Paybill or Till is common for businesses, but some vendors support STK push or other Daraja flows. Bring your current M-Pesa setup to the demo.
Are M-Pesa fees included in the Tubonge subscription?
No. M-Pesa transaction charges are separate from the software subscription, and Meta WhatsApp message fees are separate again. Budget for all three.
Can I reconcile payments automatically?
Automatic reconciliation depends on the integration. Ask Tubonge whether a payment callback is matched to the customer and order automatically, or whether an agent still has to mark it paid.
Is M-Pesa integration safe for customer data?
Ask the vendor where payment and customer data is stored, who can access it and how it is exported. Also confirm the vendor's current position on Kenya's Data Protection Act and ODPC registration.

See the M-Pesa workflow before you decide

Ask us to walk through the payment flow you use today. Tubonge plans start at KSh 3,500/month.

Pre-filled WhatsApp message includes this page as the source.

Last updated 2026-11-05. Confirm current pricing, product limits and legal requirements with the relevant provider or professional.