Collecting Payment During an AI Phone Call

The caller never leaves the conversation. That is the detail that changes conversion — there is no gap between ‘yes I will book’ and ‘payment received’ for the intent to decay in.

Because the check runs against your payment gateway, not against what the caller says. When your account is connected, a completed payment is a fact the agent can read — it either exists in the gateway or it does not.

That removes the two failure modes of manual verification. Nobody at the counter squints at a screenshot that may be edited, and nobody matches a UTR against a bank SMS between serving customers. It also removes the polite fraud where a customer says the payment ‘is processing’ and the slot gets held anyway — the agent confirms bookings on landed payments, and your booking rules decide what happens when a payment does not arrive.

Anywhere a held slot has a real cost when it dies. A dental chair blocked for an hour, a salon artist reserved for a bridal session, a banquet-hall date, a site-visit cab, a table of eight on a Saturday — each of these loses money to a no-show, and a small advance converts ‘probably coming’ into ‘paid, coming’.

The amount is your rule, not ours: a flat ₹100 token, a percentage, or the full consultation fee. Set it per service in the dashboard — an advance on the expensive treatment, none on the walk-in checkup. The agent applies whichever rule the booked service carries, and quotes it plainly rather than springing it at the end.

Businesses that do not collect advances still get the rest of the flow — the booking, the confirmations, the reminder — the payment step simply stays off.

Four, stated plainly.

First, you need your own payment gateway account connected — the money goes directly to you, which is the point, but it means the gateway onboarding is yours to complete once.

Second, the mid-call link travels over WhatsApp, so it works when the caller can receive WhatsApp on a smartphone. For the shrinking set of callers who cannot, the agent books per your no-payment rules or hands off to a human.

Third, payment apps and banks occasionally delay confirmations by a minute or more. The agent handles the common case — payment confirms while the call is still live — and the booking completes on confirmation, not on promises, even if that lands just after the call ends.

Fourth, Dvaarik adds no commission on your customer payments, but your gateway's own transaction fees apply as they would on any link you sent by hand.

The payment step itself adds nothing on Dvaarik's side — no commission and no per-link fee from us. You pay for the conversation that carries it: voice from ₹2/min with whole-minute billing on the standard grades, and ₹1,500 per 30 days for a phone number with one concurrent call line, all prepaid from credits with no setup fee and no minimum. The same flow runs on WhatsApp conversations at ₹2 per conversation, and on website chat and browser calls through the widget.

For agencies: the identical flow works for every client you onboard under the white-label programme, with each client's payments settling into that client's own gateway account — you are never in the money path, which is exactly where a reseller wants to not be.