Wati Plans: Seats, Numbers, and Qualifying Tiers

Choose your Wati plan by mapping must-haves to seats, numbers/minutes, and qualifying features — not homepage “from” tiles — then confirm on the pricing page.

By Lee M.Updated Aug 17, 20266 min readFact-checked

Quick answer

Choose a Wati package by listing day-one must-haves, mapping them to contacts and minute/number limits on researched tiers, and picking the cheapest package that clears every gate — then confirm list price on the pricing page. Confirm sms messaging (Growth+) and CRM CTI (Growth+) are on the package you will actually buy. Homepage “from” tiles are not a bill of materials.

List day-one must-haves
Map seats and numbers
Highest gate sets the tier
Soft-check usage limits
Confirm on pricing page
Defer unused packs

Wati plans takeaways

Packaging is often usage-shaped — Researched plans: Growth, Pro, Business, Enterprise. Confirm credit and seat limits in writing.
Must-haves set the tier — Plan-gated in research: sms messaging (Growth, Pro, Business, Enterprise); CRM CTI (Growth, Pro, Business, Enterprise).
No invented totals — Never invent list prices here — confirm seats, numbers/minutes, and quote terms on /pricing/wati/.
Seat discipline still matters — Count who prospects or dials weekly — not the whole org chart — before you compare Wati packages.

Wati plan anatomy

Wati must vs nice

Must-have

Calls + CRM CTI / call logging
Softphone or IVR / routing

Nice-to-have

Extra optional add-ons
AI assistance

Wati checklist

Bring these questions to every demo

Ask vendors to show the workflow live, not just describe it.

1List day-one must-havesData, calling, sync that must ship without unused enterprise.
2Map seats and numbersUse researched plan names — not marketing tiles.
3Confirm on pricing pageList price and seat or number-pack upgrades live there — not in this guide.

1. List day-one must-haves before you open pricing tiles

Wati plans diagram 1. — Must-haves decide the Wati floor — not the homepage starting tile.

Write five day-one jobs for the sales + support team.
Mark which require seats vs seats/numbers vs add-on packs.
Circle the highest gated must-have — that sets the floor tier.
Plan-gated in research: sms messaging (Growth, Pro, Business, Enterprise); CRM CTI (Growth, Pro, Business, Enterprise). Worked example: an 8-person sales + support team needs calls, CRM CTI / call logging, and IVR / routing on day one in Wati. Extra call routing and AI are nice later, so they refuse to let those upsells set the package.

2. Count weekly users and expected minute burn

Wati plans diagram 2. — Seat and minute discipline beats vanity headcount for Wati.

Count who takes or places calls weekly — not headcount.
Estimate number provisioning and calls per week (orders of magnitude, not fake precision).
Check researched capacity notes. Confirm seat/number caps for Wati on the pricing page.
Never invent list prices here — confirm seats, numbers/minutes, and quote terms on /pricing/wati/. Worked example: an 8-person sales + support team counts 8 daily users and 2 managers, defers view-only execs, and refuses any package that cannot explain seat and number renewals in writing.

3. When packaging is opaque, demand written gates

Wati plans diagram 3. — Refuse to compare Wati on a homepage tile alone when seats/numbers matter.

Our snapshot lists researched plans (Growth, Pro, Business, Enterprise), but still confirm live terms. 1. Named SKUs / editions on the quote.

Seat definition (full vs light) and seat/number definition.
What happens when seats/numbers exhaust mid-month.
Exit / export rights for numbers you built. Worked example: an 8-person sales + support team delays shortlisting Wati until seat/number exhaustion behavior and export rights appear in writing.

4. Defer unused packs; confirm the live price last

Wati plans diagram 4. — Confirm Wati on the pricing page — this guide never invents dollars.

Buy seats/numbers required for the day-one loop.
Defer AI packs, extra channels, and unused add-ons until day 30+ evidence.
Annualize only after you have written terms — never invent monthly×12 from a marketing tile.
Final check: /pricing/wati/ Worked example: an 8-person sales + support team scopes the first Wati invoice to seats + core seat and number tiers, parks the AI add-on, and only revisits packs after two Friday reviews.

5. Map must-haves to plan names in writing

Feature gates researched on Wati: sms messaging (Growth, Pro, Business, Enterprise) and CRM CTI (Growth, Pro, Business, Enterprise). Map each must-have to the plan that unlocks it.

Compare Growth, Pro, Business, and Enterprise on the same headcount assumption.

Worked example: Ecommerce and D2C teams that sell and support on WhatsApp screenshots the plan shown in demo and matches it to /pricing/wati/.

6. Model seats, usage, and add-ons together

Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Wati. Compare totals — not entry tiles.

7. Get a written quote on the qualifying configuration

Ask Wati for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.

Worked example: Ecommerce and D2C teams that sell and support on WhatsApp files quotes in the same folder with identical date and headcount headers.

8. Map must-haves to plan names in writing