Customers · Proof ledger

Named clients. One number each. Counted the hard way.

Every row below is a live production system, a client we may name, and one outcome with its counting rule written next to it. Where the number is a save, it is counted only on the confirmation the client's own system records. Where it is a recovery, it is counted when the payment completes.

Watch the handover, by use case

The same seam, four kinds of call.

One-minute cuts of the Human + AI programme: the AI runs the call, a person takes the moment that needs one, the customer never repeats themselves. No bot-only demos here; the handover is the product.

Human + AI BPO · the handover, 1 minuteThe handover
Human + AI collections callCollections
Human + AI inbound support callSupport
Human + AI lead qualification callLead qualification
Human + AI renewals callRenewals
How we count

Three rules, before any number goes on this page.

01

The client's system is the source

A save is a confirmed cancellation reversal in the operator's own log. A recovery is a completed payment. We do not count intent, promises or "engaged".

02

The window is named

Every figure states the period and the population it comes from: the circle, the bucket, the month. A peak day is called a peak day.

03

Referenceable means you can ask

Clients named here have agreed to be named. Ask us for a reference call and we will set it up; where a client prefers anonymity, we say so.

The ledger

Open any row for the method.

Customers · Proof ledger

Named clients. One number each. Counted the hard way.

Every row below is a live production system, a client we may name, and one outcome with its counting rule written next to it. Where the number is a save, it is counted only on the confirmation the client's own system records. Where it is a recovery, it is counted when the payment completes.

Watch the handover, by use case

The same seam, four kinds of call.

One-minute cuts of the Human + AI programme: the AI runs the call, a person takes the moment that needs one, the customer never repeats themselves. No bot-only demos here; the handover is the product.

Human + AI BPO · the handover, 1 minuteThe handover
Human + AI collections callCollections
Human + AI inbound support callSupport
Human + AI lead qualification callLead qualification
Human + AI renewals callRenewals
How we count

Three rules, before any number goes on this page.

01

The client's system is the source

A save is a confirmed cancellation reversal in the operator's own log. A recovery is a completed payment. We do not count intent, promises or "engaged".

02

The window is named

Every figure states the period and the population it comes from: the circle, the bucket, the month. A peak day is called a peak day.

03

Referenceable means you can ask

Clients named here have agreed to be named. Ask us for a reference call and we will set it up; where a client prefers anonymity, we say so.

The ledger

Open any row for the method.

AirtelTelecom
31.9%
Save rate · engaged customers · MNP window
Counted539 saves in the June MNP window, Bihar circle. Counted only on confirmed CANCEL-to-1900.

Reversing port-outs at scale with a Hinglish AI retention voicebot

Retention · Hinglish + Gujarati · Bihar circleRead the case study →
Tata AIGInsurance
59.78%
Auto-renewal rate · 8,662 customers
Counted250,000+ automated attempts; IDV changes handled on the call itself, 24/7 in the T-45 window.

Scaling insurance renewals with Asmita, a bilingual GenAI voicebot

Renewals · Bilingual · Live IPDS APIsRead the case study →
Muthoot FincorpNBFC
~1 in 3
Best-bucket recovery · Post-Due Bandhan Plus
Counted5,171 of 21,796 accounts recovered in month two; payment completes inside the call.

AI voicebot collections program drives measurable recoveries

Collections · 5 languages · In-call paymentsRead the case study →
CredgenicsBFSI
5–8L
Calls/day · 16+ lending brands
Counted70+ bot builds across 16+ lending brands, 300 concurrent calls; monthly volume up ~17× since ramp-up.

Powering one partner's multi-brand collections voice channel at scale

Collections · Multi-brand · 6 languagesRead the case study →
ASUS IndiaConsumer
27×
Monthly leads · dealer engagement to 43×
CountedSelf-serve support +135%; 96–97% intent recognition held through the spike.

One platform, three journeys: powering ASUS India's consumer, commercial and dealer conversations

Multi-audience · Web + WhatsApp · OnebotRead the case study →
The measurement discipline

Every number here is tied to an event we can point at.

Retention is counted only on the CANCEL-to-1900 SMS being confirmed on the call, not a verbal "yes". So the number understates the true business impact, deliberately.

Renewals are counted only when the payment settles, not when the customer accepts on the call. So the number tracks money in, not intent.

Collections are counted only against paid/unpaid dispositions per bucket per language, with the paid figure fed by the payment gateway in the call itself.

Multi-audience outcomes are attributed by bot, channel and month, so category-level gaps surface rather than blend into one flattering headline.

Your book next

Bring one portfolio. We'll bring the baseline.

The measurement discipline

Every number here is tied to an event we can point at.

Retention is counted only on the CANCEL-to-1900 SMS being confirmed on the call, not a verbal "yes". So the number understates the true business impact, deliberately.

Renewals are counted only when the payment settles, not when the customer accepts on the call. So the number tracks money in, not intent.

Collections are counted only against paid/unpaid dispositions per bucket per language, with the paid figure fed by the payment gateway in the call itself.

Multi-audience outcomes are attributed by bot, channel and month, so category-level gaps surface rather than blend into one flattering headline.

Your book next

Bring one portfolio. We'll bring the baseline.