You have hit the SaaS ceiling
Your team is on WATI, AiSensy, or Interakt and needs custom logic, deep CRM integration, or enterprise volume that the SaaS cannot handle. You want to keep WhatsApp but leave the SaaS.
Service · WhatsApp Business
WhatsApp Business, done properly.
KUMO builds custom WhatsApp Business systems for revenue stage teams. WABA setup, custom AI agents, deep CRM integration, industry specific automations. We ship what SaaS platforms cannot.
11Countries
MetaTech Provider
AWSPartner
4.6/5G2
Our owned proof
KUMO runs its own WhatsApp platform at production scale.
CampaignHQ
KUMO's own productAWS Partner
CampaignHQ is KUMO's own WhatsApp, email, and SMS platform. It runs at production scale for NxtWave, YuppTV, Volopay, Riwayat, Affixious, and SmashHouse. Every custom WhatsApp build KUMO ships for a client benefits from what we already know from running our own platform.
"CampaignHQ unified our WhatsApp and email programs. We cut vendor costs and finally see which journeys drive revenue."Rajesh Raikwar, CTO, Volopay (YC)
"3x journey completion rate. Automations run end to end without us babysitting five tools."Priya, CEO, Riwayat
50M+Messages
4.6/5G2 rating
99.9%Uptime
Meta & AWSPartner
When custom WhatsApp is right
When to build custom on WhatsApp Business.
Four situations where a SaaS platform cannot fit your workflow and a custom build is the right call.
Data residency and compliance are real
Your data cannot leave your VPC. Healthcare, financial services, or DPDP jurisdictions where SaaS chatbot tools do not meet your legal boundary. A custom build lets you own the boundary.
AI agents need real conversation depth
Not just template broadcasts. You need multi turn AI agents that qualify leads, book appointments, take orders, or handle support with real context. Confidence based escalation to humans built in.
WhatsApp is one channel of many
You need WhatsApp integrated with CRM, email, product events, and internal systems. SaaS platforms give you shallow integrations. Custom builds go as deep as your operations require.
What we build on WhatsApp
Custom WhatsApp systems KUMO ships.
Custom WhatsApp AI agents
Multi turn agents built on Claude, GPT-4o, or open models. Real conversation memory, confidence scored escalation, tool use with your CRM and product APIs. What powers KUMO WhatsApp AI implementations in production, including Klickie.
Deep CRM sync
Bidirectional sync with HubSpot, Salesforce, LeadSquared, Zoho, Pipedrive, or custom CRMs. Lead scoring, deduplication, routing, enrichment. WhatsApp conversation becomes structured CRM data.
Custom broadcast + journey engine
Beyond SaaS builder templates. Custom trigger logic, event based journeys, personalization at the individual message level. Multi channel orchestration where WhatsApp is one step in a bigger flow.
WABA setup and compliance architecture
Meta Business Manager verification, WhatsApp Business Account provisioning, template approval, phone number migration from an existing BSP. Compliance aware architecture for regulated verticals.
Production operating model
How KUMO makes WhatsApp systems operable.
Where a KUMO engagement differentiates from freelance chatbot assembly. Every KUMO WhatsApp build includes:
Environment separation
Sandbox WABA, staging, production. Message flow tested end to end before customers see it.
Template governance
Template versioning, Meta approval tracking, per market variants, category compliance (Marketing, Utility, Authentication, Service).
Rate limit management
Meta throttling logic, per conversation rate awareness, backoff and retry policies.
Conversation retention + audit
Configurable retention. Full audit log per conversation. Compliance reporting for regulated verticals.
Confidence based escalation
Every AI response scored. Low confidence routes to a human agent with full conversation context. Escalation SLAs enforced.
Multi agent inbox
Shared team inbox on web plus mobile. Assignment logic, tagging, internal notes, agent handoff without customer disruption.
CRM sync at the right point
Not too early (spammy CRM), not too late (lost context). Trigger logic engineered per client workflow.
Runbooks + handover
Written runbook for WABA management, template submission, credential rotation, incident response. Your ops team runs it after handover.
How to choose
Custom KUMO build vs WATI vs AiSensy vs Interakt vs MoEngage.
An assumptions based decision table. Different tools serve different scales and different problems. On the architecture review call, KUMO recommends the right tool for your specific need. Sometimes that is not KUMO.
| Choice | Model | Best fit | Main trade off |
|---|---|---|---|
| KUMO custom on CampaignHQ or your BSP | KUMO engineering fee + monthly platform + Meta conversation rates | Custom AI agents, deep CRM sync, compliance sensitive workflows, teams with engineering budget | You need budget for custom engineering. Fastest ROI when the SaaS ceiling is clearly hurting. |
| WATI | Per user and conversation subscription | Broadcast and simple chatbot flows at SMB scale, 15K+ customers already onboarded | Custom AI logic, deep CRM sync, enterprise SSO |
| AiSensy | Per WABA subscription | India first SMB WhatsApp broadcast and template automation | Cross channel orchestration, multi tenant enterprise setups |
| Interakt | Per WABA subscription | E-commerce cart recovery, product catalog automation | Custom AI agents, non e-commerce workflows |
| MoEngage / WebEngage | Enterprise suite pricing (typically $100K+ per year) | Multi channel enterprise engagement suites | 4 to 6 month implementations, less flexibility for non standard workflows |
| Twilio direct | Per conversation plus developer time | Full custom code, cross channel APIs, US and global reach | Requires you to build WABA management, template governance, and the AI layer yourself |
Not sure whether custom WhatsApp is the right boundary?
Bring one customer journey. Its monthly volume, systems, compliance constraints, and current SaaS pain. Get a 30 minute WhatsApp architecture review. KUMO tells you whether to stay on WATI, move to CampaignHQ, or build fully custom.
Delivery approach
How a KUMO WhatsApp engagement runs.
01Week 1
Architecture review
30 min call. Recommendation on BSP, hosting, AI model, compliance path.
02Weeks 1 to 2
WABA + scoping
WABA provisioning kicked off with Meta. Detailed scope, milestones, timeline.
03Weeks 2 to 8
Build
Sprint based. Weekly progress calls. Working message flows every sprint.
04~2 weeks live
Deploy + monitor
Phased rollout. KUMO watches the first 2 sprints of production traffic. Templates cleared.
05Weeks 10 to 14
Handover
Runbooks delivered. Ops team walked through WABA and template management.
06Ongoing
Support (optional)
Optional retainer for tuning, incidents, and system additions post handover.
Typical engagement
Typical investment for WhatsApp engagements.
KUMO's approved engagement bands, applied to WhatsApp work. These are typical investment ranges, not fixed packages. Every engagement is scoped to your project during the architecture review.
Starter Build
Typical investment
$10K to $25K
4 to 10 weeks
One custom WhatsApp system shipped end to end. WABA setup, one AI agent, basic CRM integration, monitoring, runbooks, handover.
Grow Build
Typical investment
$25K to $50K
10 to 20 weeks
Multi agent WhatsApp system with cross channel orchestration, migration from an existing BSP, or compliance heavy architecture. Full observability, DR, evaluation harness.
Yearly Engagement
Typical investment
$50K to $100K / year
Annual, ongoing partnership
Ongoing multi project engagement for teams running WhatsApp at high volume. Continuous system improvements, new AI agents, template additions, incident response, Meta API upgrades, cross region expansions. Renews annually.
What changes the range: number of AI agents, integration depth, template count, migration complexity, compliance requirements, multi region setup. Final quote after the architecture review.
Why KUMO fits
Why KUMO is the right partner for custom WhatsApp.
Four signals that a KUMO engagement is the right shape for your team.
KUMO owns CampaignHQ
Nobody else in India runs their own Meta Tech Provider platform and ships custom engineering on top. Every KUMO WhatsApp client benefits from what we learn from running CampaignHQ at 50M+ messages of scale.
Real production WhatsApp AI experience
Not aspirational. Klickie's real estate broker automation runs in production on WhatsApp. Volopay's transactional flows run through CampaignHQ. We ship what we already know how to run.
Meta Tech Provider status
Direct on Meta's WhatsApp Business Platform, not a reseller. WABA provisioning through Meta's official approval flow. Template governance done right. Compliance signals to your legal team.
Senior engineering, full ownership
No junior offshore squad. Senior engineers scope and ship. Full IP transfer of custom code and workflows after delivery. Your ops team runs the system post handover.
Related KUMO work and WhatsApp resources
More on WhatsApp Business and adjacent work from KUMO.
Common questions
Common questions.
How is this different from WATI, AiSensy, Interakt, MoEngage? +
WATI, AiSensy, and Interakt are WhatsApp only chatbot in a box products. Good for simple flows, they hit their ceiling fast when you need custom AI logic or deep CRM integration. MoEngage is an enterprise engagement suite with 4 to 6 month implementations and enterprise pricing. KUMO ships custom engineering on top of CampaignHQ (KUMO's own Meta Tech Provider platform) for teams that need MORE than SaaS covers, without 4 to 6 month enterprise implementations.
Is CampaignHQ a real Meta partner or a reseller? +
Real Meta partner. CampaignHQ is a Meta Tech Provider on the WhatsApp Business Platform. Every WhatsApp Business Account (WABA) is provisioned through Meta's official approval flow. No reseller in the middle. This matters for compliance, pricing transparency, and Meta support escalation.
Do I have to use CampaignHQ if KUMO builds for me? +
No. If you already run WATI, AiSensy, Interakt, or a direct BSP integration, KUMO can build custom AI agents and CRM integrations on top of your existing setup. CampaignHQ is our default because we ship faster on our own platform, but we work on whatever you already have.
Can KUMO handle Meta's WABA approval process? +
Yes. WABA setup is included in every engagement. Typical Meta approval takes 3 to 5 business days. KUMO handles Meta Business Manager verification, template approval, and phone number migration if you are moving from another BSP.
What languages does the WhatsApp AI support? +
Anything the underlying model supports. In practice: English, Hindi, Marathi, Tamil, Telugu, Bengali, Kannada, Arabic, Bahasa, Vietnamese, Portuguese, Spanish. Multi lingual routing in a single agent is standard.
How do you handle escalation from AI to human agents? +
Confidence scoring at every turn. When confidence drops below the tuned threshold or the customer explicitly asks for a human, the agent hands off in the same WhatsApp thread with a written summary. Multi agent shared inbox on web plus mobile. No channel switch for the customer.
What are Meta's WhatsApp per conversation rates? +
Meta charges per 24 hour conversation window, with rates that vary by country and category (Marketing, Utility, Authentication, Service). Rates typically fall between $0.005 and $0.09 per conversation depending on those variables. KUMO forecasts your total Meta bill during the architecture review based on your actual volume.
What can KUMO transfer as IP after delivery? +
KUMO transfers custom AI agent code, prompt libraries, workflow definitions, CRM integration code, documentation, and infrastructure as code. KUMO cannot transfer ownership of CampaignHQ (KUMO's own product), WATI or AiSensy or Interakt (third party SaaS), Meta's WhatsApp Business Platform, or third party services (CRMs, model providers). Those remain governed by their own licenses and terms.
Can I migrate from WATI or Interakt to KUMO custom? +
Yes. Typical migration engagement: audit existing WATI or Interakt workflows, decide which move to custom and which stay on SaaS, migrate WABA and phone number to your new BSP with dual run validation, hand over new custom infra. Migration engagements typically fall in the Starter Build or Grow Build range depending on flow count.
What support do you offer after handover? +
Two options. Option 1: full handover with runbooks and no ongoing engagement. Your team operates the WhatsApp system independently. Option 2: an optional KUMO retainer for ongoing tuning, incident response, template additions, and Meta API upgrades. Most clients pick a hybrid.
Ready to ship WhatsApp?
30 minutes, no pitch deck. You describe one customer journey. Its volume, systems, compliance constraints, and current SaaS pain. KUMO tells you honestly whether to stay on WATI, move to CampaignHQ, or build fully custom.