Why I Switched from WATI to a Self-Hosted WordPress Plugin

Fourteen months. That is how long I paid $59 a month for WATI before I sat down and asked the obvious question.

Why was I paying a SaaS company to sit between me and my WhatsApp customers, when my entire business already runs on WordPress?

The answer turned out to be habit and inertia rather than genuine need. Everything I actually used WATI for existed in a self-hosted WordPress plugin at a fraction of the cost. This is the honest breakdown of what changed — including the three things I still miss.

What I was actually using WATI for

Before switching, I made myself list what I genuinely used rather than what I was paying for. The list was shorter than expected:

• Shared team inbox — two support agents handling inbound customer queries
• Broadcast campaigns — a weekly product announcement to opted-in contacts
• Basic chatbot — FAQ deflection for the questions we answered forty times a week
• WooCommerce notifications — order confirmations and shipping alerts, routed through Zapier

That last line is the one that eventually bothered me most. Connecting WATI to WooCommerce meant a Zapier subscription sitting in the middle, plus the maintenance that comes with it. Zaps break quietly. You find out when a customer asks why they never got a shipping notification.

The migration: what it actually took

Start to finish, an afternoon. Here is each step honestly, including the one that took longer than expected.

01Export contacts from WATI

WATI allows CSV export of your contact list. I exported all opted-in contacts with their tags and phone numbers. About ten minutes.

02Install the plugin on WordPress

Standard install via Plugins → Add New, then activate. The Connect with Meta wizard picked up my existing WhatsApp Business API credentials — phone number, access token, webhook — in one click. No manual token pasting, which is the part I had been dreading.

Worth stressing: my number did not change and I did not re-verify anything. The Meta Business account stays yours; only the platform reading the webhook changes.

03Recreate the team inbox rules

I rebuilt my routing rules — order-related keywords to one agent, refund queries to another — using Smart Routing. Twenty minutes, and I found the rule builder more intuitive than the interface I had come from, though that is a matter of taste.

04Rebuild the chatbot

This is where the new setup genuinely exceeded the old one. Rather than rebuilding a rule-based FAQ bot, I connected GPT-4o with retrieval and uploaded my FAQ document, product catalogue and returns policy.

The difference is qualitative. The old bot matched keywords to pre-written answers, so anything phrased unexpectedly fell through to a human. The new one answers from my actual documents, which means it handles the long tail of oddly-worded questions that used to reach my inbox.

05Set up WooCommerce cart recovery

This was the capability WATI did not offer natively — reaching the same outcome there would have meant more Zapier plumbing on top of what I already had.

Cart recovery reads abandoned carts directly, with no connector in between, and sends a timed sequence: a first message at one hour, a second at twenty-four hours carrying a coupon. In the first week it recovered three carts that would otherwise have gone. That alone covered more than a month of the plugin cost.

What changed after switching

• Monthly cost went from $59 to $25, with Meta's API fees unchanged — those are billed by Meta either way
• WooCommerce integration went from Zapier to native — one fewer dependency and nothing to maintain between the two systems
• Chatbot quality improved noticeably — retrieval over my own documents beats keyword matching for anything phrased unusually
• Conversation data now sits on my server rather than a vendor's cloud, which simplified my GDPR position considerably
• Cart recovery became a revenue line where previously it did not exist at all, now visible in analytics alongside everything else

The cost saving is the headline, but the cart recovery is what actually mattered financially. Saving $408 a year is pleasant. Recovering carts every week compounds.

What I miss from WATI

An account with no downsides is not an account worth reading, so here are mine.

• The mobile app. WATI's is polished and I used it more than I expected to. Working the inbox from a browser on a phone is workable but not the same.
• Enterprise CRM integrations. WATI has native Salesforce support. I now reach CRM through Zapier — ironic given that removing Zapier was part of the motivation, though it is one connector instead of the several I had before.
• Integration depth and campaign reporting. WATI's analytics went a little deeper on individual campaign performance than what I use now.

None of these were dealbreakers for my situation. If your agents live on phones, or Salesforce is central to how you operate, weight them more heavily than I did.

The verdict after three months

For a WordPress-first business that does not depend on enterprise CRM integrations or a polished mobile app, the switch was clearly right.

The savings are real. The cart recovery was an immediate revenue addition rather than a projected one. And having conversation data on my own server gives me a straightforward answer on GDPR that a vendor policy never quite did.

The honest caveat is that this is my situation, not a universal recommendation. I run a WooCommerce store with two support agents and no Salesforce. Change any of those variables and the calculation shifts.

But if you are paying $59 or more a month, and your entire business already runs on WordPress, the evaluation is worth thirty minutes of your time.

Read the full feature comparison →  ·  Explore the feature set →

Frequently asked questions