Does WATI have a chatbot?
WATI chatbots are strong at keyword replies. They stall on CRM-stage branches, Shopify order context, and Growth-plan webhook/trigger caps. Here is how a visual Cloud API flow builder differs — and when to switch. Yes. WATI includes chatbots and automations on WhatsApp Cloud API, strongest as keyword replies and linear FAQs. Advanced branching, webhooks, and CRM-stage logic are limited on Growth and metered on Pro.
Last updated: 30 August 2026
People searching WATI chatbot usually already have one. It answers “price,” “hours,” and “catalogue” with a keyword. The ticket is: can it wait for Shopify “paid,” branch on Zoho stage, collect a COD yes/no, and hand off with full history? That is a different product than an inbox auto-reply.
This guide compares WATI’s public automation limits (August 2026 pricing page) with Ominiflow’s visual WhatsApp flow builder on Cloud API. WATI is not “bad at bots.” It is inbox-first. Ominiflow is journey-first. Pick the shape that matches the job.
WATI Growth lists 1,000 free automation triggers/month, 2 commerce/CRM integrations, 10k API calls, and no webhooks. Pro lists 2,000 triggers and limited webhooks. Source: wati.io/pricing. Verify live — add-ons change.
1,000
automation triggers / month on WATI Growth (public page)
webhooks on WATI Growth — events stay inside WATI
Visual
Ominiflow builder: buttons, lists, delays, CRM, human handoff
Too long? Start here
- WATI chatbot = keyword / linear FAQ with trigger caps. Fine for FAQs. Weak for order-aware journeys
- Visual flow builder = branches + delays + webhooks + CRM so the bot sees the same order a human would
- Growth has no webhooks. If your store or CRM must push events in, you are already on the wrong plan — or the wrong BSP
- Rebuild on migrate. Bots do not export. Switch from WATI · no-code store chatbot
What a WATI chatbot is good at
Keyword triggers, canned media, buttons, and “talk to human.” That covers 80% of first-week WhatsApp API use. If your only bot is a menu that routes to an agent, WATI is adequate. The review score stays high until the bot needs state.
State means: this contact’s last order, COD flag, CRM stage, payment link status, or whether they already opted into marketing. Keyword trees fake state with more keywords. They explode. Visual flows read the system of record.
WATI chatbot limits that show up in production
| Limit (public WATI pricing) | Why it bites | Ominiflow equivalent |
|---|---|---|
| Growth: 1,000 automation triggers/month | A busy store burns this on cart + COD + FAQ in days, not months | Journey nodes on the platform plan — not a trigger pack as the unit of scale |
| Growth: no webhooks | Shopify “order paid” cannot tap the bot from outside WATI | Inbound and outbound webhooks + native Shopify/Zoho events |
| Pro: 2,000 triggers, limited webhooks | Better, still metered; complex graphs still feel like an inbox add-on | Drag-and-drop branches, delays, template steps, agent handoff |
| Keyword-first mental model | Cannot natively wait on “if Zoho stage = Proposal” | CRM-stage triggers without Zapier — Zoho native |
| Astra AI listed as add-on on Pro+ | AI is a SKU, not the operating model | AI nodes included in WhatsApp AI agents with human handoff |
Visual flow builder: what “event-driven” looks like
On Ominiflow you draw the conversation: trigger (Shopify checkout started, CTWA ad, keyword, CRM stage) → message nodes (text, image, video, list, buttons) → conditions → wait → template or live agent. The customer stays on one Cloud API number. That is the same orchestration Meta and BCG describe when AI without systems fails — messaging orchestration.
Store-shaped example (no developers):
- Shopify abandoned checkout → Utility or Marketing template (category by Meta rules)
- Customer taps “Need help” → list message: Track order / Change address / Talk to human
- Track order → webhook lookup → send status
- Low confidence or “agent” → shared inbox with full history — shared inbox setup
WATI can approximate pieces with Shopify extras and higher plans. The $4.99/mo Shopify add-on on their pricing page is a reminder that commerce is not the core SKU. Native path: Ominiflow Shopify · 10 Shopify workflows.
WATI chatbot vs Ominiflow — decision table
| Job | Stay on WATI chatbot | Move to visual builder |
|---|---|---|
| FAQ + office hours + catalogue PDF | Yes | Optional |
| COD confirm before dispatch | Fragile / custom | Native YES/NO utility flow — COD playbook |
| Cart recovery with store data | Add-on / Zapier | Shopify event → template → bot |
| Zoho stage “Qualified” → WhatsApp | Zapier | Native OAuth trigger |
| Multi-agent handoff with collision lock | Basic inbox | Shared inbox + assignment |
| AI that can see the order | Copilot credits / Astra add-on | AI node on the same thread as CRM |
If you already run a WATI chatbot
Do not rebuild everything. Screenshot the top five intents by volume. Recreate those five in Ominiflow. Leave the long-tail keywords for week two. Bots never copy on a BSP switch — plan it: migration guide.
Setup without engineers: no-code WhatsApp chatbot for stores · chatbot builder feature.
Pricing note (bots are not free on either side)
Every bot reply that opens a business-initiated window still pays Meta. India (August 2026): utility ₹0.115, marketing ₹0.86 per conversation. Ominiflow does not markup that line. WATI bills a WATI rate card. Automation trigger packs are a second meter on WATI Growth/Pro. TCO: WATI pricing · calculator.
Ominiflow vs WATI · WATI review · demo
FAQ
Does WATI have a chatbot? expand_more
Yes. WATI includes chatbots and automations on Cloud API — strongest as keyword replies and linear FAQs. Advanced branching, webhooks, and CRM-stage logic are limited on Growth and metered on Pro.
What is the WATI Growth chatbot limit? expand_more
As of August 2026 WATI’s pricing page lists 1,000 free automation triggers per month and no webhooks on Growth. Confirm on wati.io/pricing; packs and add-ons change.
Can a WATI chatbot read Shopify orders? expand_more
WATI offers Shopify integration and lists a $4.99/mo add-on for some commerce templates. Deep order-aware journeys usually need higher plans, middleware, or a platform with native store events such as Ominiflow.
WATI chatbot vs Ominiflow — which is better? expand_more
WATI is better for simple keyword FAQs on a small inbox. Ominiflow is better for multi-step visual flows, native Shopify/Zoho, webhooks, and AI with human handoff on one number.
Do I lose my WATI chatbot if I migrate? expand_more
You lose the graph, not the number or Meta templates. Rebuild priority journeys in Ominiflow’s visual builder. Typical assisted go-live is 5–7 business days with complete documents.
