Make every minute count!
Brands today spend significant man-hours and resources addressing the most common customer queries across multiple channels. Imagine your agents answering “How do I reset my password?” all day.
Our conversational AI-enabled FAQ Bots let Customer Service teams run truly 24 / 7 on telephony, IVR, WhatsApp, and more.
The questions are not hard. They are simply endless — and they arrive at three in the morning as readily as at three in the afternoon. A bot that holds the repetitive two-thirds gives the hard third back to the people who are good at it.
Read the dial: the day never actually stops.
Each of the twenty-four ticks is drawn to the length of that hour’s inbound volume. The heavy arc is the window a human rota covers. Half the circumference sits outside it — and the traffic there does not fall to zero, it merely falls to a level nobody is paid to answer.Twelve of the twenty-four hours, and roughly 31% of all inbound FAQ volume, arrive when the office lights are off.
- 09:00 — 21:00
The staffed window. Twelve hours of human rota, holidays and sick days included.
- Tick length
Inbound FAQ volume for that hour, as a share of the 11:00 peak.
- Midnight
Still 18% of peak. Somebody is always locked out of their account.
Where a hundred queries actually go.
Deflection is the only metric that settles the argument. Measured across a steady-state deployment after the first two intent expansions:
- Queries resolved end to end
- 68%
Never touched by a human agent.
- Handed to an agent, pre-briefed
- 22%
Intent, account and history attached.
- Routed straight through
- 10%
Sensitive or out-of-scope. No bot detour.
Figures from live Vocallabs deployments in retail and consumer finance. Your mix will differ.
The ten questions that eat the week.
Almost every support desk we have opened up looks like this: ten intents, a little under four-fifths of the volume, and not one of them requiring judgement. Shares are of total inbound FAQ traffic.
| # | Query | Share | Resolution | Path |
|---|---|---|---|---|
| 01 | Where is my order? | 14.2% | Reads live tracking, speaks the ETA | Self-serve |
| 02 | How do I reset my password? | 11.8% | Sends a one-time link, confirms receipt | Self-serve |
| 03 | What is my outstanding balance? | 9.6% | Authenticates, reads the figure and due date | Self-serve |
| 04 | How do I return this? | 8.1% | Checks eligibility, books the pickup | Self-serve |
| 05 | Is this covered under warranty? | 7.4% | Looks up purchase date and plan | Self-serve |
| 06 | What are your working hours? | 6.9% | Answers from the store directory | Self-serve |
| 07 | I want to change my address | 6.2% | Captures, verifies by OTP, writes to CRM | Self-serve |
| 08 | Why was I charged twice? | 5.5% | Explains the hold, escalates if genuine | Escalates |
| 09 | How do I cancel my plan? | 4.8% | Retention offer, then a warm transfer | Escalates |
| 10 | Can I speak to someone? | 4.1% | Transfers immediately. Always. | Escalates |
78.6% of inbound volume · ten intents · one evening of configuration
A password reset at 2:41 a.m., and the moment it hands over.
The interesting part of this call is not the reset. It is the fourth turn from the end, where the caller mentions a duplicate charge and the bot stops trying.
Inbound · +91 · 02:41 IST · no agents rostered
Hi, you have reached Northline Support. I can help with orders, returns and account access. What do you need?
I can't log in. It keeps saying my password is wrong and I've tried like four times.
I can sort that out. Is this the mobile number on the account, ending 4417?
Yeah, that one.
I have sent a reset link to that number. It is valid for ten minutes — tell me when it arrives.
Got it. Okay, it's letting me set a new one. That worked.
Good. While you are here — your order from the 12th is out for delivery today, expected before 7pm. Anything else?
Actually yes. I was charged twice for it. There are two debits on my card.
Intent: duplicate_charge · outside self-serve scope · escalation triggered
A duplicate charge needs a person to look at the ledger. I am putting you through to billing now — they will already have your account and both transactions open. One moment.
Hi, this is Meera in billing. I can see the two debits on order 88-1129 and the reset you just did — no need to repeat any of it. Let me check the settlement.
Call handled with no agent rostered · escalated at 00:49 · caller repeated nothing
The same desk, six weeks apart.
| Measure | Agents only | With FAQ bots |
|---|---|---|
| Time to first response | 4 min 20 s in queue | Under 2 seconds, every hour |
| Hours covered | 09:00 — 21:00, weekdays | All 24, including holidays |
| Cost per resolved query | ₹ 48 | ₹ 6 |
| Repeat questions per agent, per day | ~90 | ~12, all genuinely hard |
| Abandoned before answer | 19% | 2% |
| Languages held at 2 a.m. | None | English, Hindi and eight more |
From your ticket history to a live line, in five moves.
- 01
Mine the last 90 days
We read your ticket history, call recordings and chat logs, then cluster them by intent. The ten questions that make up two-thirds of your volume fall out of that on their own — no workshop required.
- 02
Ground the answers
Each intent is wired to a real source: the order API, the billing ledger, the help centre article. The bot quotes your systems, not a guess, so an answer is never stale.
- 03
Draw the escalation line
You decide what the bot must never attempt — refunds over a threshold, medical advice, anything a regulator names. Those route straight to a human, with no attempt to deflect.
- 04
Shadow, then go live
It runs silently behind your agents first, answering into a log nobody hears. When its answers match your team’s for a fortnight, you point the after-hours traffic at it.
- 05
Watch the dial move
Every unresolved turn becomes a gap report. New intents get added weekly, so the deflected share climbs instead of plateauing on day one.
One intent model, every place they ask.
The same answers, the same escalation line, the same logs — whether the question arrives spoken down a phone line or typed into WhatsApp.
- 01PSTN · SIP trunk
Telephony
Answers on the number your customers already know. Sub-second barge-in on interruption.
- 02Press-1 retired
IVR replacement
Callers say what they want in their own words instead of walking a menu tree.
- 03Business API
WhatsApp
Same brain, typed. Carries the reset link, the tracking card and the return label inline.
- 04Web · iOS · Android
In-app voice
The help button opens a spoken session already signed in, so nothing needs verifying twice.
- 05Zoho · Salesforce · Freshdesk
CRM write-back
Every resolved query lands as a closed ticket with the transcript and intent attached.
- 06Warm transfer
Agent desktop
Handoff carries the caller, the intent and the last four turns. No "can you repeat that?".
The six things every support lead asks us first.
Give your team back the hard third.
Bring us ninety days of tickets. We will tell you which ten questions are eating your week, what share of them a bot can close on its own, and what the dial looks like at two in the morning for your customers specifically.
