Verify before you share
A flow authenticates the customer up front — account talk only happens with the right person.
Reach your customers where they already are, for support and marketing.
Shared inbox, AI replies, translation, flows, and broadcasts on the official WhatsApp Business API. Live in a day.
Answer it once.
The other forty-nine take care of themselves.
Link your WhatsApp Business number in a few clicks. No new SIM, no migration drama.
We connect your database, knowledge base, and FAQ — the groundwork your AI flows are built on — then add your team.
Start replying — with AI drafts, translation, and flows working from day one.
CustomerX watches the customer support questions that keep coming back. Answer one well and it becomes a suggested article — the next time someone asks the same thing in different words, the reply is already drafted. Supervise every send or automate it completely — your call.
answered once = answered forever ↻
German, French, Spanish, Italian, Polish, Dutch — whatever your customers write across Europe arrives in the one language your company works in, and every reply goes back in theirs. Seamlessly, in both directions, voice notes included. One team, every European market.
Voice notes are transcribed and translated the same way — no “hang on, let me listen” pauses.
Ask, verify, branch, act. No code, and we build the first ones with you. Here's one running live: a customer wants to swap shoes. The flow recognises her by number, finds the order, checks the return window, asks the one thing it doesn't know, and books the exchange. No agent touched it.
Pick who should hear it — VIPs, everyone who bought last month, one city — and send them a single WhatsApp message. A promotion, a launch, an invitation to join your next campaign. Replies come straight back into the shared inbox as normal conversations, so a broadcast starts real chats instead of ending in a void.
select · preview the cost · send ✦
Every card below is made from the same parts — flows, AI drafts, lookups and routing — wired to your systems with you during onboarding. Whatever your customer support looks like today, it fits.
A flow authenticates the customer up front — account talk only happens with the right person.
The flow collects documents and details step by step, then your team takes over for the final check.
Connected to your core system during onboarding — statuses and balances answer themselves.
Segment: customers with a savings account. One message, and the replies come straight back into the inbox as normal chats.
CustomerX isn't a sign-up-and-figure-it-out customer service tool. You get a team of CustomerX experts who onboard you, build the integrations into your own systems, and design the automation around how your business actually runs — and who stay reachable once you're live.
Our team builds the integration into your database, CRM or internal API, so every chat can show real orders, balances and bookings.
We build flows where the AI calls your API mid-conversation — check a status, book a slot, apply a change — so whole scenarios run themselves.
CustomerX specialists run the onboarding end to end and stay on hand afterwards. Live support, answered in under an hour.
Flat pricing, nothing added on top, and you always own your number and your data. No lock-in, no black boxes.
Start on Solo, move your team onto Core, and go fully custom when you outgrow it.
For support desks of up to 3
Up to 3 seats
see it work on your own chats
For a support team of 4–20
4–20 seats · one flat price
most teams live here 🙂
For 20+ seat operations
20+ seats · priced with you
your platform, your rules
Every feature sits in that price — AI drafts, flows, translation, broadcasts, voice calls. Inbound calls are free. Meta's per-message fees are passed through at cost — details in the FAQ below.
Because your customer already has it open. No download, no account, no password reset, no ticket number to quote. And the whole history sits in one thread on their phone — theirs and yours.
Using WhatsApp for customer support also means the fastest channel your customers have is the one your team works in — with a shared inbox, assignment, and history, so it scales past one phone on the counter.
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 depends on the mode you pick. In review mode, the AI writes a reply and your agent sends it, edits it, or bins it. In autopilot mode, the AI answers customers itself, from your knowledge base, and hands the chat to a person when it can't help.
Most teams start on review and switch topics to autopilot once they trust the answers. Some run everything on autopilot, some never do. Your call.
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 covers teams of 4 to 20 seats for €390 a month, on a six-month minimum term. Smaller? Solo is €149 a month for up to 3 seats. More than 20? Enterprise is priced with you.
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, and the rate varies by country and message type.
From 1 October 2026 that includes replies to customers who message you, after the first 1,000 replies per number each month. Our flows and AI drafts are built to resolve in as few messages as possible, so that bill stays small.
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.
30 minutes. We'll show you the inbox live, build a flow for your use case, and answer everything. No deck, no “discovery call”.