WhatsApp customer support,
in any language.

This is the part we're proudest of.

Every incoming message arrives in your team's language — text and voice notes alike. Nobody presses a translate button, and nobody switches tabs. A voice note in Arabic becomes readable text in English, in the thread, in seconds.

Replies can go the same way: we can set your team to write in one language and have every outgoing message delivered in the customer's. You choose per conversation or as a standing rule, and we set it up with you.

Your customers can write in almost any language. Detection and translation are automatic — German, Arabic, Chinese, Spanish, Farsi, whatever turns up in your inbox.

Your team works in whichever language you choose. That's the language your agents read incoming messages in, and the language the app itself is in — set up with you during onboarding. Want to change it later? It's a configuration change, not a rebuild.

Only where you decide it should.

Conversations you design — a greeting, a menu, a booking lookup — run on their own, because you wrote every word in them. Anything open-ended is different: the AI writes a reply and your agent sends it, edits it, or bins it. Nothing free-form reaches a customer without a person choosing to send it.

Most teams start with everything on review and open up one topic at a time. That's a perfectly good place to stay.

It answers from your documents and nothing else. When the answer isn't in there, it's instructed to say so and hand the conversation to a person rather than fill the gap itself.

That's also why the review step matters. Until you've watched it answer a topic correctly for a while, an agent sees every reply before your customer does. You decide when that changes, topic by topic.

It's the part everyone dreads, so we do it with you.

Point us at what you already have — your website, price list, policies, the answers you've typed a hundred times — and our AI turns it into a working knowledge base. You review it, fix what's wrong, and it's live.

Once your systems are connected, this is what an agent sees when they open a chat: who the customer is, their order or booking already on screen, the request checked against your rules, and anything missing already asked for — in the customer's language.

They start at the decision, not at “hello, could I take your booking reference?”

Yes — that's the main reason teams move off the WhatsApp Business app.

Every agent gets their own login. Conversations are assigned automatically or picked up manually, you can see who's handling what, and if two people open the same chat they can see each other typing. No shared phone on the counter, no two agents answering the same customer twice.

Yes. CustomerX runs in the browser and works on a phone — no app to install, nothing to update. Most teams work from a laptop and keep a phone open for evenings and weekends.

Nothing gets lost. Your flows keep running, so customers who ask a common question still get an answer at 11pm. Anyone who needs a person gets an honest reply telling them when your team is back, and the conversation is waiting in the queue — sorted and translated — when the first agent logs in.

Always.

A customer can ask for a person in their own words — we set up the phrases for every language you serve — and the conversation moves straight to your team. Your agents can also take over any conversation at any moment, and the AI steps back for the rest of that thread.

You need it. You don't need to understand it.

We set it up with you on a call. Once Meta has verified your business, most teams are sending and receiving the same day. If you can connect a printer, you're overqualified.

Your inbox is live the day we connect your number — messages arriving, translated, assigned to your team.

The rest lands over the following week or two: connecting your database or systems, building your first flows, filling the knowledge base. You're working in it the whole time, not waiting for a launch date.

Your number stays the same, and your customers notice nothing except faster replies.

One thing worth knowing: moving your number onto the business platform takes it off the WhatsApp Business app, and the history in that app doesn't come across. Everything from go-live onward lives in the platform — searchable, assigned, and visible to your whole team.

CustomerX is built to be wired into your world rather than used as-is. You can connect your own database and APIs, and build flows and features around how your business actually works.

A team of CustomerX support experts does that first round with you — building the connection to your database or API, designing the flows that automate your real scenarios (including letting the AI call your systems mid-chat), and setting up your knowledge base. They stay reachable once you're live: questions get a reply in under an hour. As your business changes, you can keep building — a new flow, another system, different routing.

Core includes ten agent seats for €390 a month, on a six-month minimum term. Extra seats are €20 each — so a team of fourteen pays €470. On your own? Solo is €149 a month for one seat, with the first two months free.

Past twenty seats it makes more sense to talk, because at that size teams usually want things built specifically for them. That's Enterprise.

Meta charges a small per-message fee for conversations you start, and the rate varies by country.

Replying to a customer is free. Once someone messages you, everything you send back for the next 24 hours costs nothing — which is most of what a support team does all day.

Marketing campaigns to a large list are the one place this adds up, and we'll show you the cost before you send. We pass Meta's fees through at cost, with no markup, and break them out on your invoice.

We don't have one. Zero markup, on broadcasts and on everything else.

You broadcast to your customer base paying nothing but Meta's official per-message rate, at cost, itemised on your invoice. We show you the full cost before a single message goes out, so nothing arrives as a surprise.

No, and we'll be specific about what that means.

Your WhatsApp number is registered to your business, not to us — it stays yours. Your conversations, contacts and knowledge base are yours too, and we'll give you a full export whenever you ask, including if you're leaving.

The one genuinely fiddly part is moving a number back off the WhatsApp business platform afterwards. It's a Meta process, not ours, and we'll walk you through it rather than make it your problem.

Yes. We never sell your data or share it with advertisers or data brokers — not ever. Your workspace runs in its own database in a region you choose with us at onboarding — EU (Amsterdam) or US (California) — and we tell you exactly which one. EU hosting is available to every customer.

Individual logins for every agent, role-based access so people only see what they should, and your conversations in a database dedicated to your business — not pooled with other customers.

Message content is processed only by the providers needed to run the service — Meta for delivery, Google and OpenAI for translation, AI and voice transcription — under data-processing agreements, and none of them train on it. Our privacy page names every one, and our data-processing page lists where each one sits and under which transfer terms.

If a customer asks you to delete their data, we'll do it — properly, including message history and voice transcripts.