How Whatbot compares
Written to be checked rather than believed. Every claim about Whatbot below points at the thing in the product that makes it true, and the places we fall short are on the same page as the places we do not.
Whatbot vs Wassenger
| Whatbot | Wassenger | |
|---|---|---|
| Entry planWhatbot prices in INR first; GST is shown separately rather than folded in. | ₹1,999/mo · 3 agents | $39.90/mo · 3 agents |
| Top plan | ₹9,999/mo · 10 agents, +₹999/mo each after | $99.90/mo · 9 agents, +$14/mo each after |
| Campaigns / month | 10 · 25 · unlimited | 10 · 20 · 100 |
| Recipients per campaign | 500 · 2,500 · 10,000+ | 500 · 1,000 · 2,000 |
| Meta conversation feesSame model. This is a reason to ignore the axis, not a reason to pick either. | At cost, no markup | At cost, no markup |
Wassenger figures are its published Professional / Business / Enterprise tiers, checked 21 August 2026. Competitor pricing changes without notice — verify against their own pricing page before making a decision on it.
Where Whatbot is genuinely different
Voice calls happen inside WhatsApp
Customers call the same number they message, and agents answer in the browser — permission-gated per contact, logged on the same thread as the chat. No recording and no AI answering: the audio goes browser to Meta and never reaches our servers.
Browser WebRTC (ICE/DTLS/SRTP, OPUS) · no server-side SFU, so no recording path
Secrets never enter the flow graph
HTTP nodes reference a credential rather than embedding it, so exporting a flow cannot leak one. A missing or undecryptable secret fails the node instead of sending a blank header.
Fernet (AES-128-CBC + HMAC-SHA256), enc:v1: tagged, in utils/secret_crypto
The API is the product, not an add-on
Everything the dashboard does is available to your own systems, with signed delivery of inbound events and per-tenant keys.
9 public routers · SHA-256 hashed keys · X-Whatbot-Signature: sha256=…
It runs inside your own product
The whole inbox drops into an existing CRM as an iframe, signed in as the agent already using it — not a second login.
HMAC SSO hand-off · partitioned (CHIPS) cookies for Safari/iPadOS
Forms and the catalogue stay inside the chat
A form opens and submits in WhatsApp itself, and the customer browses your catalogue and sends a cart back as an order — neither step hands them off to a browser tab, which is where link-based flows lose people.
WhatsApp Flows (site_visit_booking.flow.json) · catalogue read live from WhatsApp, cart → order
Multi-tenant from the first line
Each organisation carries its own WABA and number. Running several brands is the normal case here, not an enterprise upsell.
Per-org config in organization_whatsapp_config
Where Whatbot is behind
If one of these is the thing you need, another product is the right answer today.
No native app integrations yet
There is no one-click Shopify, HubSpot or Zapier connector. The REST API and webhooks are how you integrate today.
No mobile app
The inbox is responsive on a phone browser. There is no iOS or Android client.
No call recording, and no AI answering calls
Voice calling itself is live, but the audio flows between the agent's browser and Meta and never touches our servers — so there is nothing on our side to record, and no point for an AI agent to pick up. This is the transport, not a roadmap item: both would need calls to terminate on a media server we do not run. If recorded calls are a requirement, this is not the product today.
Onboarding is operator-assisted
There is no self-serve signup. Connecting a number is done with our team, which takes a conversation rather than a form.
The voice-calling claims above — that calling is live, and that there is no recording and no AI answering — were re-checked against merged code on 22 August 2026. The Wassenger figures higher up carry their own, earlier date; they were not re-checked on this pass.