Members & Revenue · Billing Recovery
Most churn is a failed card, not a lost member
The recovery agent treats each failure reason differently: an expired mandate needs a one-tap renewal nine days early, insufficient funds needs a retry timed to salary day, a chargeback needs a human with an evidence packet.
Payments at risk
9,658
Recovered this cycle
5,324
Revenue saved
₹1.94Cr
annualised, net of retries
Messages per member
≤ 3
hard cap, then a human
Recovery by failure reason
Tap a row to act on the cohort
| Failure reason | Members | Recovery rate | Play |
|---|---|---|---|
| Card declined | 4,120 | 62% | Agent retries on the issuer's best-hour window, then messages in the member's language. |
| Mandate expired | 1,840 | 71% | Pre-expiry nudge 9 days out with a one-tap re-mandate. |
| Insufficient funds | 2,600 | 48% | Retry after salary-day inference, capped at 3 attempts. |
| Voluntary cancel | 980 | 22% | Value reframe, never a discount as the first move. |
| Chargeback raised | 118 | 0% | Evidence packet assembled by the agent, filed by a human. |
Recovery rates
Where the effort pays back
Card declined62%
Mandate expired71%
Insufficient funds48%
Voluntary cancel22%
Chargeback raised0%
Rules the recovery agent follows
- Three attempts maximum, then a human decides. Repeated retries damage the issuer relationship.
- Every message names the real reason in the member's language — never "there was a problem".
- Access is not cut mid-billing-cycle; the member keeps what they paid for while recovery runs.
- A chargeback is never fought by an agent. It assembles the evidence, a human files it.
- A member who asks to cancel is not put through recovery. They get a clean exit and one honest question.