Wati vs Gallabox vs WhatsApp Cloud API for Education Teams
Wati vs Gallabox vs Meta's WhatsApp Cloud API for education teams: what each includes, how message charges and plans stack up, switching numbers and who each suits.
Wati vs Gallabox is the comparison most education teams in India make when WhatsApp outgrows one phone, and there is a third option that often gets left out: connecting Meta's WhatsApp Cloud API directly. This post compares the three on what you actually get, who bills you for what, what happens if you switch later, and which shape of team each one suits. It is for admissions heads, coaching centre owners and study abroad consultancy owners choosing where their WhatsApp number should live.
Key takeaways
- Wati and Gallabox are providers that sell an inbox, chatbots and broadcasts on top of Meta's platform. The Cloud API is Meta's own interface and comes with no inbox at all.
- Every option pays Meta's message charges. Wati and Gallabox add a subscription plan on top; going direct means you need software, usually a CRM, to read and answer chats.
- Both providers list plans by users, flows or broadcast volume. Match the plan limits to your counsellor count and season peaks before comparing anything else.
- A number can move between WhatsApp Business Accounts later, keeping its display name and quality rating, but templates need time to copy across. Switch outside admissions season.
- Decide where counsellors will work every day first. The WhatsApp option should follow that decision, not lead it.
Three different things, not three brands
The names sit side by side in every comparison, but they are not the same kind of product.
| Wati | Gallabox | WhatsApp Cloud API direct | |
|---|---|---|---|
| What it is | A provider with its own WhatsApp software | A provider with its own WhatsApp software | Meta's programming interface for WhatsApp |
| Inbox for counsellors | Yes, its own shared team inbox | Yes, its own shared team inbox | None; you need your own software or a CRM |
| Chatbots and flows | Built in | Built in | Only if your software provides them |
| Who you pay | Meta's message charges plus a Wati plan | Meta's message charges plus a Gallabox plan | Meta's message charges, plus whatever your software costs |
| Best fit | Teams that want WhatsApp handled as its own tool | Teams that want WhatsApp handled as its own tool, with CRM integrations by plan | Teams whose CRM connects the Cloud API, or who have developers |
Meta's Cloud API overview is clear about the third column. You need a business portfolio, a WhatsApp Business Account and a business phone number, and incoming messages are delivered to your software by webhook. Meta's WhatsApp Manager handles account settings, not conversations. So "going direct" never means "no software": it means the software is your CRM instead of a provider's inbox.
What Wati offers, from its own pages
Wati's pricing page (checked September 2026) lists three subscription tiers, Growth, Pro and Business, on monthly, quarterly or annual billing, plus a pay-as-you-go single-user option.
- Included on every tier: a "Shared Team Inbox", "Chatbot Builder", "Contact Management", "APIs", "Broadcast Management" and "WhatsApp Catalog".
- Pro adds advanced chatbots and what Wati calls "AI qualification".
- Business adds "Multiple WhatsApp numbers", a dedicated customer success manager and priority support.
- Users: Growth includes three users with no add-ons; Pro and Business include five, with extra users available at a charge.
- Messages: the page says "Additional charges apply for messages" and that per-message charges vary for marketing, utility and authentication.
Who it suits: a team that wants a capable WhatsApp inbox with chatbots and broadcasts, and is happy for WhatsApp to be a separate screen from wherever student records live. The Business tier's multiple numbers matter for institutes that give each branch its own number.
What to check: whether three or five included users covers your admissions season, when temporary telecallers join, and how the chats connect to your student records.
What Gallabox offers, from its own pages
Gallabox's pricing page (checked September 2026) lists four tiers, Basic, Essential, Advanced and Enterprise, billed quarterly or annually.
- Included on every tier: a "WhatsApp Shared Team Inbox".
- Users: Basic has "3 users (hard cap)"; Essential includes six and Advanced ten, both expandable; Enterprise has custom seats.
- Flows and broadcasts: the number of active chatbot flows and monthly broadcast contacts rises by tier, with Enterprise listed as unlimited.
- Integrations and API: Basic lists "20+ integrations" and a "Message + Contact API"; higher tiers add more CRM integrations, including Zoho and HubSpot, and "All APIs".
- Messages: WhatsApp conversation fees are listed separately, with a link to country-by-country fees.
Who it suits: a team that wants flows and broadcasts at clear volume limits, and expects to connect WhatsApp to a CRM through an integration its plan includes.
What to check: the Basic tier's hard cap of three users, and which tier includes the integration with the CRM you already use.
The Cloud API directly: what Meta gives you
Going direct means you, or your CRM, talk to Meta without a provider in between. From Meta's documentation:
- Throughput: business phone numbers can send "up to 80 messages per second by default", with a pair-rate limit of "1 message every 6 seconds to the same WhatsApp user".
- Billing: Meta's pricing page says billing is handled through Meta Business Suite.
- No inbox, no chatbot builder: anything counsellors see comes from your own software.
Who it suits: teams whose CRM already connects the Cloud API, often through Meta's Embedded Signup, so counsellors answer chats on the student's record and there is no second subscription for an inbox. Also teams with developers who want full control. It suits a team that relies on no-code chatbots less well, unless their CRM provides them.
What it costs: two layers, whichever you pick
We will not quote amounts here, because Meta sets rates by category and country and both providers change their plans. The structure is what you need for a decision.
Layer 1, Meta's charges, identical for all three. Since 1 July 2025, Meta charges per message and you are "only charged when a template message is delivered". Non-template messages inside an open customer service window are free, and so are utility templates delivered inside one. When a student starts a chat from a Click to WhatsApp ad or a Facebook Page call-to-action, all message types are free for 72 hours. Rates vary by template category and the recipient's country calling code.
Layer 2, the software. A Wati or Gallabox plan, sized by users, flows and broadcast volume. Going direct, this layer is your CRM's subscription instead.
Worked example: counting billable messages
Take a hypothetical coaching institute in a results month. The volumes are assumptions, so use your own:
| Message | Volume | Billable? |
|---|---|---|
| First message to 1,200 Meta lead form enquiries | 1,200 templates | Yes, the student has not messaged you, so no window is open |
| Replies to 400 students who clicked a Click to WhatsApp ad | Around 2,000 messages | No, inside the 72-hour free entry point |
| Counsellor replies to students who wrote back | Around 3,000 messages | No, non-template messages in an open window |
| Demo-class broadcast to 5,000 opted-in contacts | 5,000 templates | Yes, charged per delivered message |
| Fee reminder templates after the window has closed | 600 templates | Yes |
That is roughly 6,800 delivered templates to price against Meta's rate card for India by category, and the figure is the same whether they go through Wati, Gallabox or the Cloud API. The provider plan is a fixed cost on top. Two habits cut the bill: reply while the window is open, and do not broadcast to contacts who never opted in. If the Meta form leads are the big line, our Meta Lead Ads CRM page covers how those enquiries reach counsellors.
Switching later: moving your number
Teams worry that choosing Wati or Gallabox locks the number in. Meta's guide to migrating a phone number between WhatsApp Business Accounts says otherwise, with conditions:
- Embedded Signup is "the preferred solution" for the move.
- The number keeps its display name, quality rating, template messaging limits and Official Business Account status.
- Eligible templates are duplicated to the new account with the same approval status, but template quality ratings reset to "UNKNOWN", and templates can't be used until they are copied.
- Two-step verification on the number must be disabled first.
- Registration is instant, so the number keeps sending and receiving messages.
Meta's guide does not cover chat history. Before you leave any provider, ask how to export past conversations, and keep the export with your student records.
The practical rule: switch in a quiet month. A day without your fee reminder or document templates in May is an inconvenience; in the week after board results it is lost enquiries.
Wati vs Gallabox vs Cloud API: a decision rule by team shape
| Your situation | Lean towards | Why |
|---|---|---|
| Two or three staff, WhatsApp is the main tool, no CRM yet | Wati or Gallabox, entry tier | A ready inbox and chatbots without buying anything else; check the user limit |
| Chatbots already built in one provider and working | Stay where you are | Rebuilding flows costs more than any plan difference |
| Each branch has its own WhatsApp number | Check multi-number support on the tier you need | Wati lists multiple numbers on its Business tier |
| Counsellors already live in a CRM all day | Cloud API through that CRM | One screen, chats on the student record, no second inbox subscription |
| The owner answers from the WhatsApp Business app and won't stop | Cloud API with Coexistence, if your CRM supports it | App and API on one number |
| An in-house developer and custom needs | Cloud API direct | Full control, at the cost of building and maintaining it |
The mistake to avoid is running a provider inbox and a CRM side by side with no link between them. Then a student replies in one place, the follow-up sits in the other, and nobody knows which is current. For how the Business app, the API and Coexistence differ in more depth, read WhatsApp Business app vs API vs Coexistence, and for full CRMs with WhatsApp inside, the best WhatsApp CRM for education.
How Xale handles this
Xale is our product, so weigh this section accordingly. Xale connects all three routes, and what works differs by route:
| In Xale | Cloud API (incl. Coexistence) | Wati | Gallabox |
|---|---|---|---|
| New WhatsApp enquiries become leads | Yes | Yes | Yes |
| Reply from the Xale inbox | Yes | Yes | Not yet |
| Automated template sends | No | Yes | Yes |
| Broadcasts to a filtered segment | Yes | No | No |
Chats land in one inbox scoped by role, so counsellors see their own students' conversations. On the Cloud API, templates can be created and submitted to Meta for approval from the CRM, and broadcasts go out immediately rather than on a schedule. Gallabox teams reply in Gallabox for now, while Xale captures their leads and sends automated templates. Xale never bills WhatsApp messages: Meta or your provider does. UrbanChat accounts connect too. The WhatsApp CRM for education page walks through each connection, and our best education CRM by use case guide compares full CRMs.
Frequently asked questions
Is Wati or Gallabox cheaper for an education team?
It depends on your shape, not on a headline price. Meta's message charges are the same whichever provider you use, so compare the plans on what you will actually hit: included users during admissions season, active chatbot flows, monthly broadcast contacts and the integrations you need. A plan that is cheaper on paper but caps users below your team size becomes the expensive one.
Do we need Wati or Gallabox to use the WhatsApp Cloud API?
No. Any business with a Meta business portfolio, a WhatsApp Business Account and a phone number can use the Cloud API. What you do need is software to read and answer messages, because Meta delivers incoming chats to that software and provides no counsellor inbox. That software can be a provider such as Wati or Gallabox, a CRM that connects the Cloud API, or something your developers build.
Can we move our WhatsApp number from one provider to another later?
Yes. Meta supports migrating a number between WhatsApp Business Accounts, and the number keeps its display name, quality rating and messaging limits. Approved templates are copied across, but they can't be used until the copy finishes and their quality ratings reset. Two-step verification must be switched off first. Ask your current provider how to export chat history before you move.
Does going direct to the Cloud API avoid message charges?
No. Meta charges for delivered template messages whichever route you use, with rates set by template category and the recipient's country code. What going direct removes is the provider's subscription, not Meta's charges. Replies inside an open customer service window are free on every route, so fast replies save money everywhere.