What an engagement looks like, what you get, and what it costs to start.
Five stages. You'll know at every point what's happening and what's needed from you.
We go through how enquiries reach you today, where they get dropped, and what happens after someone calls. I'm working out whether automation actually helps you — sometimes the honest answer is that a process fix costs nothing and solves it. If it does help, this call is where the scope and the real number come from.
I map the whole flow before writing anything: what the agent says, what it asks, when it hands over to a person, where the data lands, and what happens on the days it goes wrong. You see this and sign off on it. Changing a diagram is cheap; changing a live system is not.
The agent, the automations, and the integrations get built and tested against your real scenarios — including the awkward ones. Most of this window is testing rather than building, because that's where the real edge cases surface: how the agent handles accents and background noise, timezone and scheduling logic, making sure nobody gets called twice. Timelines stretch further when a system has to talk to software that doesn't want to be talked to; if that's your case, you'll hear it in stage one, not halfway through.
The system starts handling real conversations while I watch every one of them. Real callers do things no test does, so the first week is about catching those and fixing them fast. Your team gets shown how it works and what to do when they need to step in.
The system keeps running and keeps getting tuned. What that covers is below — it's the part most people underestimate, so it's worth reading before you commit to a build.
Every engagement, regardless of size.
The system connects to what you already use — your CRM or sheets, your calendar, WhatsApp, your phone numbers. If something has no proper API, I'll tell you what that costs in reliability before anything gets built on it.
Tested against your real scenarios, not a happy path: the caller who interrupts, the one who switches from Hindi to English mid-sentence, the wrong number, the one who wants a human.
A working session with whoever runs the front desk or the sales floor. They see what the system does, what it won't do, and exactly how to take over a conversation when they need to.
Written record of how the system is wired, what each part does, and where the credentials and accounts live — in your possession. If you ever hand this to someone else, they can pick it up.
Why a live system needs someone on it — this isn't a maintenance fee for a website that sits still.
A voice agent isn't software that gets finished. It talks to real people every day, and real people are unpredictable: they ask things it hasn't been taught, they call about products you launched last month, they phrase things in ways the model reads wrong. Meanwhile the platforms underneath it — the telephony, the WhatsApp API, the model itself — keep changing on their own schedule. A system nobody is watching doesn't stay still, it quietly gets worse. That's what the retainer is actually for.
Calls and conversations get reviewed, not just counted. Failures, dropped calls and handovers that should have happened get caught by me rather than reported by your customer.
The agent's script gets corrected against what real callers actually say. This is where most of the improvement after go-live comes from, and it never entirely stops.
New service, new price, new branch, a doctor who's stopped taking Thursday appointments — the system has to be told. Otherwise it confidently tells your customers something false.
APIs go down, credentials expire, providers push changes without warning. When that happens you have someone to call who already knows how your system is wired.
Systems start at ₹35,000 setup, plus a monthly retainer scoped to your call volume.
That's a starting point, not a fixed price. What a system actually costs depends on how many calls it handles, how many places it has to connect to, and how much of your process it takes over. I'll give you a real number after the discovery call — not before, because anyone quoting you a system before understanding your call flow is guessing.
Tell me how enquiries reach you today and where they're getting lost. If automation isn't the answer for you, I'll say so on the call.
Book a discovery call