Pilot · Mobility
Proactive pre-boardingvoice calls on thePune–Bangalore corridor
A 16-day outbound pilot with Prasanna Purple Mobility reached 74% of 1,100+ passengers before departure, with 59% hearing the full announcement and zero complaints about receiving the call.
1,105
Passengers dialled
73.7%
Delivery rate
58.8%
Full listen rate
319
Feedback recordings
Repetitive calls blocking urgent ones
Prasanna Purple's support team fields a high volume of repetitive queries in the two hours before every departure. Passengers call to ask the same three questions: what is my boarding point, what time does the bus leave, and what is my bus number.
These calls are not urgent — but they are constant. While the support line handles generic queries, passengers with genuine emergencies cannot get through: a driver who is unreachable, a passenger at the wrong stop, a tracking failure. Rezonna's AI voice agent flips the model by proactively pushing the right information to every passenger before they feel the need to reach out.
Outbound pre-boarding voice calls
From 20 May to 4 June 2026, Rezonna ran a complimentary 16-day pilot, automatically placing pre-boarding voice calls to every Prasanna Purple passenger approximately two hours before departure. No human agent was involved. An AI voice agent placed each call, delivered travel details, and gave passengers the option to leave feedback.
- Route and direction of travel
- Scheduled departure time and bus number (registration)
- Reminder to check WhatsApp for the live tracking link
- Option to leave a voice message or report an issue
Scope: both Pune → Bangalore and Bangalore → Pune routes · 56 departure runs · 1,105 passengers dialled in total
Core targets met
The pilot met its core operational targets on delivery, message consumption, and passenger engagement. Three success criteria were green — delivery rate, listen rate, and client value. Two amber items reflect measurement gaps (inbound call baseline, data accuracy fixes), not concept failures.
Delivery by route
| Route | Dialled | Reached | Missed | Rate |
|---|---|---|---|---|
| Pune → Bangalore | 588 | 434 | 154 | 73.8% |
| Bangalore → Pune | 517 | 380 | 137 | 73.5% |
| Total | 1105 | 814 | 291 | 73.7% |
Why calls fail — and the fix
Of 291 missed contacts, 92.1% were due to a busy line — not wrong numbers or platform errors. A single retry 5–10 minutes after the first busy signal is estimated to push delivery rate from 73.7% to 85%+.
Passengers are listening
Of the 814 passengers who answered, 58.8% stayed on the line long enough to hear the complete announcement (50 seconds or more). A further 26.2% heard most of the message. 85% of passengers who answered stayed for at least 30 seconds — the content is not being rejected.
| Duration | Calls | Share | Interpretation |
|---|---|---|---|
| Under 30 seconds | 122 | 15% | Likely hung up early |
| 30–49 seconds | 213 | 26% | Heard most of the message |
| 50–69 seconds | 309 | 38% | Full message + feedback window |
| 70 seconds+ | 170 | 21% | Full message + left feedback |
What passengers said
319 passengers left voice messages after the announcement — 39% of everyone who received the call. No passenger complained about receiving an automated call.
39%
Left a voice message after the call
0
Complaints about receiving the call
85%
Stayed on the line at least 30 seconds
Passengers treated the call as a useful pre-trip briefing, not a nuisance. The optional feedback step gave operations a direct channel after the announcement — without passengers needing to dial the support line first.
Calls intercepted before they happen
814 passengers received their full travel details before departure — without placing a single inbound call. If 30% of reached passengers would have called support anyway, the pilot potentially intercepted roughly 230–330 support calls across 56 departure runs (~4–6 per run).
A precise inbound reduction figure requires a pre-pilot baseline. Tracking inbound call categories from Day 1 of a subscription produces an exact ROI figure after 30 days.
Fixes before scaling
- 1Sync departure times at campaign dispatch — removes the top feedback complaint
- 2Add boarding point to the announcement script
- 3One retry on busy lines (5–10 min delay) — estimated delivery above 85%
Why this matters for real estate teams
Rezonna is built for real estate teams that lose deals when calls go unanswered. Our voice platform also runs high-volume outbound campaigns where the same problem appears: repetitive questions flooding the line before a critical moment. In a 16-day mobility pilot we reached 74% of 1,100+ passengers before departure, with 59% hearing the full message and zero complaints about receiving the call. The infrastructure, compliance, and voice quality are what carry over to your sales desk — not the bus script.
Run a focused pilot on your operation
Most teams go live in under two weeks on a single workflow. Book a demo to map your use case, integrations, and success metrics.