Koravi Developers replaced their plot-enquiry desk with one AI agent.

The problem

Royal Estate Phase-XII launched in April 2026 with 71 plots on Unkal-Hebballi Road in Hubballi. Within 7 days, the Koravi sales team was getting more inbound enquiries on Phase-XII than their three-person calling desk could handle. The choice was: hire three more callers (~₹1.65 lakh/month at fully-loaded cost), or pilot AI calling.

The hiring path was hard. Quality tele-callers in Tier-2 Karnataka are scarce; Koravi had already burned through six candidates in the previous quarter. AI calling looked attractive — but the Hindi-English code-switch concern was real. Their previous attempt with a US-built tool had been embarrassing.

Why DigitalCallers

Three reasons:

• Indic-native voice. The Suresh agent uses our voice engine with our India-tuned voice — distinguishable from English-trained TTS in the first 5 seconds. Koravi’s director ran a side-by-side test with two friends pretending to be customers and reported “they couldn’t tell it was AI in 4 of 6 calls”.
• Project facts before close. Their previous tool would skip straight to a site-visit ask without delivering the rate, plot size, or documents. Customers hung up. DigitalCallers’s Hard Closer template forces project facts in turn 2 (mandatory) before the close turn.
• Resilience to SIP failure. Hubballi’s SIP routing has been spotty in the past. Multi-trunk failover meant Koravi got 62% connect rates where their previous tool got under 50%.

How they deployed

Day 0 was knowledge ingestion. Koravi dropped the Phase-XII brochure (rep-12 final updated.pdf) into the DigitalCallers knowledge base. The system extracted the 14 facts that mattered for an enquiry conversation — plot dimensions, rates, document status, NA/KJP clearance, EMI options, location landmarks (Sai Nagar Circle, Goa-Dharwad highway proximity), and the booking process.

Day 1 they picked the Hard Closer template (Suresh persona, male voice). They added one custom rule via the Prompt Editor: site-visit asks must use “weekday ya weekend, koi bhi din chal jayega” instead of locking the lead into Saturday-only.

Day 1-2 was test calling. Internal team tested it on each other’s phones, scored the conversations, and tweaked. The big iteration was around the “document clear hai?” question — Suresh originally answered too tersely. After three whisper sessions correcting the answer, the team applied the prompt-edit suggestion DigitalCallers generated.

Inside a typical call

“The first time I heard a Suresh call from start to finish, I had this moment where I forgot it wasn’t a real person. The way he said ‘1300 rupaye per square feet sir, 30x40 ka plot 15.6 lakh’ with that exact Hubballi cadence — that’s when I knew this was different.”

— Director, Koravi Developers

A typical Phase-XII call lasts 85 seconds. Suresh opens, delivers project facts in turn 2, handles 1-3 questions in turns 3-5, and asks for the site visit in turn 6. About 28% of connected calls end with a confirmed site-visit appointment. Of those, the on-site conversion to actual booking is being tracked separately.

What worked, what didn’t

Worked

• The Hindi-English code-switching held up across hundreds of calls. Customers commented on it positively, not negatively.
• Multi-trunk failover prevented the “why is no one connecting” complaints from sales when our SIP carrier had a brief 486-Busy spike.
• The knowledge ingestion meant Suresh never said “I’ll have to check” for any of the 14 facts that mattered. Confidence held.
• The Live Monitor + whisper feature got used 3-5 times per day during week 1, mostly to nudge Suresh to mention KJP clearance more proactively. After 5 whispers in 3 days, the team applied the prompt-edit suggestion and whispers dropped.

Didn’t work

• Mid-call language switching — if a Marathi-speaking lead asked questions in Marathi, Suresh stayed in Hindi. We documented this as a known limitation; it’s a our voice engine Live constraint, not a DigitalCallers one.
• Phase-XIII enquiries. Some leads asked about “next phase” — Suresh’s knowledge base only had Phase-XII. The weekly emerging-objections digest flagged this as a knowledge gap; Koravi added a Phase-XIII placeholder in week 3.
• The first version of the Hard Closer template was too aggressive — Koravi’s director rated calls 6/10 on warmth. We softened the template to 6/10 aggressiveness (down from 8/10) and that fixed it.

What’s next

Koravi is rolling out a second AI agent — Laxmi, the Storyteller persona — for warm follow-ups on leads who didn’t book a site visit on the first call. Different voice, different cadence, different end-call discipline. The same knowledge base.

For the Phase-XIII launch in Q3 2026, Koravi plans to dispatch the entire post-launch enquiry queue through DigitalCallers from day 1. They’re also evaluating per-client agency white-labeling for “Koravi Voice” as a separately-branded product they could offer to other Tier-2 builders.