What does automating customer service cost?
Nobody asks for a quote out of curiosity. If you are reading this, it is because someone on your team spends the day answering the same question, or because the messages that arrive at eleven at night are still unopened at nine the next morning. The number you are looking for does exist, but it will not fit in a price table on a website. What can be explained upfront is what that number depends on, and how to get to it without going round in circles.
Why we do not publish a catalogue price
We do not publish a fixed rate, and the reason is simple: putting a number on your project before knowing how you work would mean assuming things about your business that we do not know yet. Whatever gets assumed ends up inside the price one way or another, and that helps nobody. An automation quote looks more like a building quote than a product label: until the floor comes up, nobody knows what is underneath.
That does not mean you have to sit through weeks of meetings to find out whether it is worth it. The more concrete the conversation, and the more of your own data on the table, the sooner a number can be put on it. At Zepai we reply to an enquiry in under twenty-four hours and most projects are delivered in five to seven working days, so we have the same interest you do in keeping the question phase short. What we will not do is put a price on something we have not yet seen working from the inside.
The cost you are already paying without seeing it
The minutes spent giving the same opening hours for the umpteenth time are easy to see coming. What is harder to see is the interruption: every message pulls someone out of what they were doing and makes them start again. Anyone serving customers and producing at the same time is switching tasks all day, and that switching costs something too, even if it never shows up on an invoice.
Then there are the messages that arrive out of hours. Someone writing on a Sunday afternoon may well be asking the same thing in three other places at once. If that message goes unanswered until Monday, more than that conversation can go with it: the moment when the person had half made up their mind. By Monday morning the message has gone cold, and picking up a cold thread is nothing like answering while they were still writing.
And then there is the copying and pasting. Order details travelling from the chat to a spreadsheet, a booking written into the diary by hand, the customer name typed again into every tool. That work creates nothing new, it only moves information from one place to another, and every hop is a chance to get it wrong. When you ask for a quote, count these tasks too: they are repetitive and the rules are clear, which is exactly what a machine handles best.
How many channels you need to cover
The first factor is where people write to you. Setting up WhatsApp on the official API is one thing; adding a voice agent that picks up the phone at any hour is another. Each channel has its own character: people write differently, they wait differently, and what works in one does not transfer word for word to the other. Adding a channel is a separate piece of work, so it is worth deciding where you start instead of opening everything at once.
The second is volume, and it counts, though not only as a headline number. Variety weighs too: a lot of messages asking the same thing can be handled with one rule, while a handful that each arrive with their own twist need an answer written for every case. Peaks matter as well: if your week is concentrated in two afternoons, the system has to hold up on those two afternoons, not on the average. That is why the messages as they arrived say more than a summary of them.
What it has to talk to, and what history you are carrying
A bot that only returns text is the simplest thing to set up and not much use. The work starts to grow when it has to look something up: a calendar to book an appointment, stock to say whether a size is left, a customer record to know whether they have bought before. At that point the automation is not in charge, the tool you already use is. If it has a decent API, connecting it is one of the quick parts. If it is an old program or a panel with no external access, the bridge has to be built before it can be crossed.
History is the other piece people forget when asking for a price. Bringing over your existing contacts and conversations can be a minor step or a job of its own, depending on their state: whether they can be exported, whether there are duplicates, whether the same customer appears with two phone numbers and three names. Sometimes the sensible decision is to migrate nothing. You start clean, the history stays where it is so it can still be consulted, and what you save there goes somewhere else.
How much judgement has to be written down
This variable appears on no list of services, and it weighs on the quote. An agent knows nothing about your business: it does exactly what is written. Every decision a person currently makes out of habit has to be put into words. What is said to someone asking for something you do not offer. The exact point where the conversation stops belonging to the agent and goes to a human, and how that person picks up the thread without making the customer repeat themselves.
Here is the real drawback, and the reason a quote can fall short: that judgement is not written down in any document, it lives in the head of whoever has been handling customers for years. It comes out by arguing over specific cases, and sometimes the team does not agree with itself. It is the part of the project that depends on you and the part that can stretch it. That is why we would rather see your awkward cases before putting a number on the table: without them, any price we give you is provisional.
There are uncomfortable conclusions too. If nearly every conversation you have ends in a different negotiation, putting an agent in front gets in the way more than it helps; what needs automating there is what happens behind, the paperwork after the yes. Sometimes the answer is not to automate, or not to automate yet. We would rather say so on the first call than find out halfway through, and that is why training is included at the end: so you can change the rules yourself when the business changes.
What to bring to the first call
Bring real conversations from a normal week, without picking the good ones, and bring them anonymised: for a quote the text is what matters, not your customers' personal details. Reading actual messages shows straight away what a long meeting never surfaces. From those you can work out which questions repeat, which ones need a piece of data from somewhere else, and which ones a machine should never answer. If you can also point out which arrive out of hours, better still: that is a good piece to start with.
Bring the list of tools you use as well and, above all, who holds the credentials. If nobody can find an access, the integration stops there, however well the code is written. Be clear about your real service hours and what happens today with anything arriving outside them. And come with the questions each person on your team answers differently: that is unwritten judgement, and you already know how much it weighs on the quote.
With that in front of us, the conversation moves much faster and the number stops being guesswork. Write to info@zepaiagency.com, call +34 604 14 09 97 or send a message on Instagram, at @zepaiagency; we reply in under twenty-four hours. We are an Official Meta Partner. WhatsApp always runs on the official API. And if, after listening to you, we think it is not worth it for you, we will say so on that same call.
Want to build this in your company?
Half an hour, no sales pitch. And if we think it is not worth it for you, we will say so.
Get a free quote →