How an e-commerce team stopped letting FAQ calls drown out their real buyers
An e-commerce team was getting around 6,000 phone calls a month, and roughly 60% of those were the same handful of FAQs and product questions over and over. We trained an agent to answer all of them, transferred real buyers to the sales team instantly, and gave the client a knowledge-base sheet they manage themselves.
- Monthly call volume
- ~6,000
- FAQ share of inbound
- ~60%
- Customer-managed knowledge base
- Yes
Phase 1 of an engagement with an e-commerce retailer. Phase 2 is the IVR replacement + live product search build that followed.
The pattern in the call log
6,000 inbound calls a month. Roughly 60% of them were the same six or seven questions: opening hours, return policy, "do you have this in stock", "what colour does it come in", "where's my order".
The other 40% were the calls the business actually needed. Real buyers, real escalations, real money on the line.
But all 6,000 calls were hitting the same human team. The sales reps were being interrupted by people who just wanted to know the store hours, while customers ready to spend money were sitting on hold behind them.
What we built
A voice agent fronting the customer-care line, trained on the website, the FAQ page, the product information, and the store details. It answered the FAQ and product questions directly, in plain language, with the same answers a human rep would have given.
The handoff logic was the part that mattered. The moment the agent picked up real buying intent on a call, it transferred. No qualifying questions, no "let me get the right person", just an immediate handoff to a human salesperson with the context attached.
We instrumented every call. Every question asked, every answer given, every place the agent stumbled.
What changed for the team
Sales stopped being interrupted by FAQ calls. Real buyers reached a human faster, because the human team wasn't drowning in repetitive questions anymore.
The agent absorbed the bulk of the FAQ traffic. We don't have a clean percentage to publish here; instrumentation on the deflection rate was the thing we learned to build better on the next project, not this one.
The thing this engagement gave us going forward
A knowledge-base sheet the client owns. Every question the agent gets asked is logged. Every answer is editable in three clicks. New Q&A pairs can be added without a developer in the loop, and without us.
That single artefact made every later build easier to ship and easier for the client to actually own. It's been standard scope on every voice agent we've deployed since.
When this build fits
Teams getting buried in repetitive phone questions while their real customers wait on hold. Start here. No deep integrations, no booking system, no fancy database. Just the questions, the answers, and a clean handoff to a human when it matters.