Wati vs. Respond.io (2026)
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
Wati vs. Respond.io (2026)
Wati builds messaging automation around the WhatsApp Business API and handles Facebook and Messenger conversations in the same omnichannel inbox, while Respond.io is a channel-neutral shared inbox that treats Messenger, WhatsApp, and other channels as equal options.
Introduction and methodology note
If your app needs to send and receive Facebook Messenger messages, the underlying API is Meta's own Messenger Platform. The practical decision for most teams is not which raw API to call, but which platform sits on top of it: who hosts the webhook, the inbox, the automation, and the compliance setup. Wati and Respond.io both do that job, and both cover Messenger alongside other channels.
Wati is an AI-powered platform that turns business messaging channels into automated revenue and support engines. It is built as a WhatsApp Business API platform first, with Facebook, Instagram, TikTok, web chat, and RCS arriving in the same Team Inbox. Respond.io is a shared inbox platform covering WhatsApp, TikTok, Instagram, calls, and Messenger, positioned as a channel-neutral conversation management system.
Both platforms also differ in how they treat developers. Wati publishes a developer hub with API capacity tiers and webhook access that scale by plan, which matters if your app will call the messaging API directly. Respond.io's published pages emphasize the inbox and team workflow side, and its API capacity figures are not published on the pages reviewed for this comparison.
Methodology note: Wati figures on this page come from Wati's own published pages, linked inline. Respond.io figures are stated in plain text from its published pages and are not hyperlinked. All figures were last verified in November 2026. Performance and reliability claims are self-reported by each vendor, so test both platforms on your own message volume before committing.
TL;DR
- Wati fits teams whose messaging volume is WhatsApp-led and who want Messenger and Instagram conversations handled in the same inbox, with automation and AI built around that flow.
- Respond.io fits teams that run several channels at equal weight and want a channel-neutral inbox with zero markup on Meta's messaging fees.
- Neither product replaces Meta's raw Messenger Platform API for custom app-to-Messenger integrations; both sit on top of Meta's APIs and add inbox, automation, and AI layers.
Quick-comparison table
| Dimension | Wati | Respond.io |
|---|---|---|
| Primary focus | WhatsApp Business API platform, official Meta BSP | Channel-neutral shared inbox |
| Messenger coverage | Facebook and Messenger DM automation in the omnichannel inbox | Messenger as one of several equal channels |
| Entry plan (annual billing, as of November 2026) | Growth at $59 per month | $79 per month |
| Billing model | Per plan plus per-message rates under Wati's rate card | Per Monthly Active Contact |
| Broadcasts on entry plan | 15,000 broadcasts a month on Growth | The $79 plan cannot run broadcasts |
| AI agents | Astra included in every plan (1 agent on Growth) | AI agents not on the entry plan |
| Free trial | 7 day free trial | Not published on the page reviewed |
| Setup fee | Zero fee WhatsApp setup | Not published on the page reviewed |
| API capacity (top plan) | 20 million API calls a month on Business | Not published on the page reviewed |
Granular differentiator table
Respond.io's clearest differentiator is its billing model and its zero markup on Meta's messaging fees. Wati bills messages under its own rate card, and no published figure for that markup exists, so the table compares structure rather than claiming a price winner.
| Aspect | Wati | Respond.io |
|---|---|---|
| Meta messaging fee markup | Billed under Wati's own rate card; no published markup figure | Zero markup on Meta's messaging fees, per Respond.io's published positioning |
| Entry plan broadcasts | 15,000 broadcasts a month on Growth (as of November 2026) | Not available on the $79 plan, per Respond.io's published plan structure |
| AI agent on entry plan | 1 Astra AI agent on Growth | Not on the entry plan |
| Extra seats | $39 per user per month on Pro, $89 on Business | Not published on the page reviewed |
| Card processing fee on top-ups | Not published on the page reviewed | Waived from 1 October 2026 until further notice, per Respond.io's own blog |
On raw Meta fee pass-through, Respond.io's model is simpler to predict. Wati's rate card bundles platform capability with message billing, and the WhatsApp Business API pricing calculator lets you estimate conversation costs before committing.
Why teams choose Wati over Respond.io
One inbox built around messaging automation, not just conversation management
Wati's omnichannel inbox covers WhatsApp, WhatsApp Business Calling, Facebook, Instagram, TikTok, web chat, and RCS, with assignment, tagging, reporting, and follow-up automation. The difference is what surrounds the inbox: broadcast campaigns, no code chatbots, and Click to WhatsApp Ads are native parts of the same product. Respond.io also offers a shared inbox across those channels; its automation depth on the entry plan is where the plans diverge.
AI that is included, not gated to top plans
Every Wati plan includes the Astra AI agent builder, where agents are built in minutes using natural language, plus Wati AI credits (2,000 a month on Growth, 5,000 on Pro, 20,000 on Business, as of November 2026). Astra handles customer-facing conversations while Wati AI features such as AI Conversation Summary and AI Editor support your team inside the inbox. Respond.io's $79 entry plan does not include AI agents, per its published plan structure.
Developer surface when you outgrow the inbox
Wati exposes a developer hub with API capacity that scales by plan: 10,000 API calls a month on Growth, 200,000 on Pro with limited webhooks, and 20 million on Business with extensive webhooks. A minimal send looks like this:
curl -X POST "$WATI_API_BASE/sendSessionMessage/$WA_ID" \
-H "Authorization: Bearer $WATI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"message": "Your order has shipped."}'
$WATI_API_BASE is the base URL printed in your Wati API settings, and $WA_ID is the WhatsApp ID of the contact.
That API surface is WhatsApp and Instagram focused. For Messenger specifically, Wati's coverage is the inbox and DM automation rather than a raw send/receive REST API, which is the honest trade-off against Respond.io's broader channel API story.
If that mix of WhatsApp depth plus Messenger and Instagram coverage in one platform matches your roadmap, you can book a demo with Wati to see the inbox and automation side by side with your current setup.
Best use cases for Wati
WhatsApp-led support with Messenger as a secondary channel
Support teams that handle most volume on WhatsApp but still receive Facebook messages get both in one Team Inbox, with routing rules on Pro and round robin assignment on Business. How Respond.io compares: it covers the same channels with a channel-neutral design, which suits teams without a dominant channel.
E-commerce messaging and campaigns
Wati's e-commerce tooling includes the WhatsApp catalog, Shopify abandoned cart and order templates, and broadcast campaigns with 15,000 messages a month included on Growth. How Respond.io compares: its entry plan excludes broadcasts, so campaign-led teams land on higher tiers there.
AI-assisted qualification and support at scale
Astra agents qualify leads and answer customers around the clock, and Pro adds advanced agents with multilingual support, integrations, and human handoff. Business adds Voice AI Agents with multiple languages, accents, and voice cloning. How Respond.io compares: AI agents exist higher up its plan ladder, so the entry-level AI experience differs.
Best use cases for Respond.io
Truly multi-channel teams with no dominant channel
If your conversation volume splits evenly across Messenger, Instagram, WhatsApp, and web chat, Respond.io's channel-neutral inbox is designed for exactly that balance. Wati's tooling is deepest on WhatsApp, and that shows in features like Click to WhatsApp Ads and Coexistence.
Teams that prioritize Meta fee pass-through
Respond.io charges zero markup on Meta's messaging fees, which makes per-message costs directly predictable against Meta's published rates. Wati bills under its own rate card, and no published markup figure exists, so cost-sensitive teams should request a quote from both.
Platform overview of Wati
WhatsApp Business API access
Wati is an official Meta BSP and provides WhatsApp Business API access with zero setup fee and blue tick verification help. See the WhatsApp Business API page for the onboarding flow.
Messaging API for developers
The WhatsApp messaging API covers session messages, templates, and media sends from your backend. Full endpoint documentation lives at docs.wati.io, with endpoint availability by plan spelled out per tier.
Webhooks for real-time events
Inbound messages and status events arrive via the webhooks API. Webhook access scales by plan: none on Growth, limited on Pro, extensive on Business. In practice that means a Growth workspace polls or relies on the inbox, while a Business workspace can drive real-time order and CRM updates from every inbound event.
Chatbots and automation
The no code chatbot builder handles keyword replies, forms, and connected chatbots, with third-party webhooks available on Pro for custom logic. Automation triggers are metered: 1,000 a month on Growth, 2,000 on Pro, and 5,000 on Business, with packs available as add-ons from $40 a month (as of November 2026).
Messenger and Instagram in the same inbox
Facebook and Instagram conversations land in the same inbox as WhatsApp, and Instagram DM automation runs on Meta's official messaging API with keyword, comment, and story-reply triggers. An Instagram DM chatbot with AI works across Instagram, WhatsApp, and Messenger in Wati. For Messenger specifically, this is the practical path: conversations arrive in the inbox, get automated and assigned like any other channel, and never require you to host a Meta webhook yourself.
MCP for AI agents
Wati offers an MCP server so AI tools like Claude can operate your messaging workspace; setup is documented in the MCP overview. Standard workspaces connect to https://mcp.wati.io/mcp and EU-hosted workspaces to https://eu-mcp.wati.io/mcp.
How to choose decision matrix
| Your situation | Choose |
|---|---|
| WhatsApp is your primary channel, Messenger and Instagram secondary | Wati |
| Four or more channels at roughly equal volume | Respond.io |
| You need broadcasts and AI agents on a low plan | Wati |
| You need exact pass-through of Meta's messaging fees | Respond.io |
| You need a raw Messenger send/receive API in your own app | Meta's Messenger Platform directly; neither vendor replaces it |
| You need deep WhatsApp API capacity and webhooks | Wati (up to 20 million API calls a month on Business) |
Migration guide: switching from Respond.io to Wati
This migration makes sense when WhatsApp becomes your dominant channel. If your volume stays evenly split across channels, staying put is the better end state, and a partial migration (WhatsApp only) is a valid middle ground.
- Set up the account. Start the 7 day free trial, connect your WhatsApp Business number through Meta's flow, and confirm zero setup fees apply.
- Rebuild automations. Recreate Respond.io workflows as Wati no code chatbots and automation triggers. There is no one-to-one import; expect to rebuild logic manually.
- Swap API calls. Replace Respond.io API calls with Wati endpoints for WhatsApp flows:
// Before: a channel-neutral POST to the shared-inbox messages endpoint
await fetch(`${RESPOND_API_BASE}/messages`, {
method: "POST",
headers: { Authorization: `Bearer ${RESPOND_KEY}` },
body: JSON.stringify({ channelId, recipientId, text: "Your order has shipped." })
});
// After: a WhatsApp-specific session message on Wati
await fetch(`${WATI_API_BASE}/sendSessionMessage/${waId}`, {
method: "POST",
headers: { Authorization: `Bearer ${WATI_KEY}` },
body: JSON.stringify({ message: "Your order has shipped." })
});
The shape is similar, but the semantics differ. Wati's endpoint is WhatsApp-specific: session messages only work inside the 24-hour customer service window, and outbound-initiated messages need an approved template instead. Map each Respond.io call to the matching Wati endpoint in the API reference rather than doing a blind find-and-replace.
- Plan the cutover window. Run both platforms in parallel for at least a week, forward notifications from the old inbox, and move channels one at a time, starting with WhatsApp.
- Watch for gaps. Wati's developer API surface is WhatsApp and Instagram focused; there is no equivalent raw Messenger send/receive API, so keep Messenger traffic in the inbox and automation layer. Template approval lead times on WhatsApp are a Meta process no vendor skips.
- Repoint integrations. Reconnect HubSpot (Pro), Salesforce (Business), Shopify, Zapier, Zoho CRM, and WooCommerce under Wati's integration settings.
FAQ
Which API actually sends and receives Facebook Messenger messages?
Meta's own Messenger Platform is the API that sends and receives Messenger messages from your app. It requires a Meta developer app, a Facebook Page, webhook verification, and page messaging permissions. Platforms like Wati and Respond.io build on Meta's APIs rather than replacing them.
Does Wati offer a Messenger API for developers?
No. Wati's developer API surface covers WhatsApp and Instagram, while Messenger conversations are handled through the omnichannel inbox and Messenger DM automation. If your requirement is raw programmatic Messenger access, use Meta's Messenger Platform directly.
Can Wati and Respond.io both handle Messenger conversations?
Yes. Wati routes Facebook and Messenger conversations into its Team Inbox alongside WhatsApp, Instagram, TikTok, web chat, and RCS. Respond.io covers Messenger as one of several equal channels in its shared inbox.
How do their entry plans compare on price?
As of November 2026, Wati's Growth plan is $59 per month billed annually with 15,000 broadcasts, 1 Astra AI agent, and 10,000 API calls a month. Respond.io's entry plan is $79 per month and, per its published plan structure, cannot run broadcasts, workflows, or AI agents.
Which platform is cheaper for messaging fees?
Neither vendor changes what Meta charges. Respond.io passes Meta's messaging fees through with zero markup. Wati bills messages under its own rate card, and no published markup figure exists, so request quotes from both before deciding.
Do I need Meta business verification to use either platform?
Yes. Both platforms run on Meta's official APIs, so Meta's business verification applies to your WhatsApp Business account and Facebook Page regardless of vendor. Wati helps with blue tick verification as part of its zero fee setup.
Is Wati a good fit if my app is Messenger-first?
Not the best fit. Wati's depth is in WhatsApp-native automation, campaigns, and AI, with Messenger handled at the inbox level. For a Messenger-first product, build directly on Meta's Messenger Platform, or evaluate Respond.io if you also want managed inbox tooling.
Start with the 7 day free trial to test Wati's inbox and automation against your current Messenger and WhatsApp volume, or book a demo with the team first.