From ManyChat to a Custom WhatsApp Assistant for WooCommerce, with Claude as the Brain

ManyChat is a fast way to get a chatbot live on WhatsApp, and there is no shame in starting there. You drag a few blocks into a flow, connect your number, and within a day customers are getting replies. For the first stretch it feels like a quiet win: messages get answered, a few sales come through, and nobody had to write code. Then the store grows, the questions get sharper, and the cracks start to show. A customer asks where their order is and the bot offers a menu instead of an answer. Someone asks whether a product is in stock or which size fits, and the flow has no idea, because it has never actually seen your catalog. Every new contact nudges the monthly bill upward, and all of those conversations, with all of that customer detail, are passing through a company that is neither you nor your store.

That is the moment worth paying attention to. It usually means your support and your presale conversations have become valuable enough to deserve something that truly knows your business, rather than a generic flow that only pretends to. The good news is that the upgrade is not a leap into the unknown. You can move to a WhatsApp assistant that is wired directly into your WooCommerce data, runs on your own infrastructure, and thinks with a real brain instead of a script.

What ManyChat genuinely does well

It is worth being fair, because ManyChat earns its place at the start. The visual flow builder is approachable, you can stand up a basic experience without a developer, and the marketing side, broadcasts and simple opt-in campaigns, is the kind of thing that gets a young store its first repeat sales. As a way to prove that customers will engage with you on WhatsApp at all, it does the job. The trouble is not that it is bad. The trouble is that it is built to be generic, and your store has stopped being generic.

Where it starts to pinch for a real store

A handful of limits tend to arrive together, and they are structural rather than anything you can configure away:

• It does not actually know your store. A flow is a script. It cannot look up a real order, read live stock, quote the right price for a variation, or recall what a returning customer bought last month, because it has no real connection to the data that makes those answers possible.
• Your customers' conversations run through someone else. Every message, name, and order detail passes through a third party's systems. For conversations that touch purchases and personal information, that is a layer of trust you are handing away.
• The price grows exactly as you succeed. Per-contact plans mean the bigger and more engaged your audience becomes, the more you pay, which is the worst possible time for a cost to climb.
• The intelligence is shallow and bolted on. Whatever AI features exist sit on top of a flow engine that was never designed for genuine understanding, so anything nuanced, multilingual, or specific to your products quickly hits a ceiling.
• You cannot build past the platform. The day you want behavior the builder does not offer, you are stuck negotiating with a tool instead of simply building what your business needs.

Each of these is something a customer can feel, in a slow or wrong answer, and something your bottom line feels, in a sale that did not close or a bill that keeps rising.

What "custom, without a third party" really means

Let us be precise, because honesty here matters. The one piece you cannot remove, and would not want to, is WhatsApp itself. Messages travel over Meta's official WhatsApp Business Platform, the same way email travels over a mail provider. That is the channel, not a middleman.

What you remove is the bot platform sitting between you and WhatsApp, and between you and your own data. Instead of ManyChat relaying messages and holding the logic, your own small backend connects straight to WhatsApp's official API, reads directly from your WooCommerce database, and answers with Claude as the brain. It runs on your Vercel project, under your account, with your keys. Nobody else is in the conversation, and nobody else is metering your contact list.

The architecture, in plain terms

The whole thing is simpler than it sounds, and it is the same serverless pattern we use for production payments and compliance software. A message comes in, your backend gathers the facts, the model decides what to say, and the reply goes out:

// Vercel serverless webhook: WhatsApp in, Claude (with Woo tools) out
export async function POST(req) {
  const update = await req.json();
  const msg = extractMessage(update);              // the customer's actual words
  const reply = await claudeWithTools(msg, {       // Claude is the brain
    lookupOrder, findProducts, checkStock, policy  // tools that read your live Woo data
  });
  await sendWhatsApp(msg.from, reply);             // straight back to the customer
}

The important detail is in that third argument. Claude is not guessing. It is given a set of tools that read your real WooCommerce data, order status, product details, stock levels, your shipping and returns policy, and it calls them when a question needs a fact. So when a customer asks "did my order ship," the assistant looks up the actual order and tells them, rather than offering a menu. The webhook is verified so only WhatsApp can trigger it, every secret lives in environment variables rather than in the browser, and the whole backend deploys the moment you push, which is the same webhook discipline we describe for Revolut on Vercel and for Stripe in a headless storefront.

What it can finally do

This is where the move pays for itself, because the assistant stops performing helpfulness and starts being helpful:

• Presale questions, answered with real knowledge. Which size fits, whether two products are compatible, what is in stock, what shipping costs to a given country, what the price is for a specific variation. These are the questions that decide whether a hesitant visitor becomes a buyer, and they get answered from your catalog, correctly, in the moment the customer is ready.
• Support that actually resolves things. Order status and tracking, returns and exchanges, address corrections, all grounded in the live order in your database, so the customer gets a real answer instead of a holding pattern.
• A voice that fits your brand and your customers. On-brand tone, multiple languages, and the judgment to say "let me get a person for this" and hand off cleanly when a question is sensitive or out of scope, which is the difference between an assistant that builds trust and one that quietly erodes it.

The thinking behind this, knowing when to buy a tool and when the answer is something built around your own data, is the same case we make in build versus buy for an AI chatbot and in giving your site an AI assistant that knows your business.

The economics, stated honestly

A fake percentage would not help you, so here is the real shape of it. With a per-contact platform, your cost is tied to the size of your audience, and it climbs as your list grows whether or not those people are messaging you. A custom assistant changes what you pay for. You pay WhatsApp's own per-conversation fee to Meta, a small amount to host the backend on Vercel, and the model usage you actually choose to run through Claude. None of those scale with the raw size of your contact list the way a per-contact plan does.

That means the savings are not a single number, they are a trajectory. The larger your audience and the more you lean on messaging, the wider the gap grows between a bill that follows your list size and one that follows real usage you control. For a small store sending a handful of messages, the difference is modest. For a store where WhatsApp is becoming a real sales and support channel, which is exactly the store that outgrows ManyChat, it compounds.

Migrating without disrupting what works

You do not flip a switch and hope. The move is a sequence of small, safe steps:

1. Map what you have. We look at your current ManyChat flows, list what they do and which ones actually earn their keep, and identify the questions your customers ask most.
2. Set up the official channel. Your WhatsApp Business account and number on Meta's platform, owned by you, so the conversation belongs to your store from day one.
3. Build the backend behind a fixed-scope first phase. Usually that first phase is one or two high-value jobs done properly, for example order-status answers and your top presale questions, grounded in live Woo data, with a clean handoff to a human for anything beyond it.
4. Prove it, then widen it. You see it working on real questions before it ever faces a customer, and once it is solid we layer on more: returns, broadcasts, deeper product help, each shown to you before it ships.
5. Keep marketing clean. Outbound campaigns still work, through WhatsApp's approved message templates and proper opt-in, so you stay compliant and your number stays trusted.

How we build it, and why you can trust the result

A channel that talks to your customers in your name deserves a careful process, so ours is built to keep you in control the whole way. We start with discovery and a clear roadmap, so you know the shape of the work before it begins. The first phase is fixed in scope and agreed up front, so there are no surprises. You see demos before each next step, and you give feedback that turns into changes quickly because you talk to the developer building it, not a queue. Above all, you own everything: your WhatsApp account, your Vercel project, your keys, and your WooCommerce data, with no lock-in, which is the entire point of leaving a rented platform behind. The same ownership-first instinct runs through our guide to why connecting your stack beats copy and paste and our look at when a custom WooCommerce build is the right call.

Proof, not promises

This is the everyday substance of our work, not a theory. We run real production backends on Vercel, including the customs-invoice.com compliance platform, and we ship full storefronts with live payments such as LeO-Optic. Verified webhooks, careful handling of customer data, and AI grounded in real business records are exactly the ingredients a trustworthy WhatsApp assistant needs, and the WooCommerce craft behind it is the work we do as WooSmiths.

If your store has outgrown ManyChat and you want a WhatsApp assistant that truly knows your catalog and your orders, runs on your own Vercel project, and thinks with Claude rather than a script, tell me how you use WhatsApp today and I will outline the cleanest first phase to get there.