For collections, receivables & e-commerce
Past-due balances and declined subscription cards are the same problem wearing different clothes: revenue you already earned, sitting behind a phone call nobody has time to make. Voicent makes the call and closes it — card or ACH captured on the line, posted to your system before the caller hangs up.
The number that decides everything
Every receivables operation and every subscription business runs on the same brutal arithmetic: what does it cost to recover a dollar? Human dialing answers that with wages, turnover, and a contact rate that collapses the moment the queue gets long. Payment links answer it with an open rate.
A voice agent that can actually accept money changes the denominator. It works the whole queue, not the top of it — and the call that would have ended in a promise ends in a posted transaction instead.
What you get
CAPTURE
The caller enters their card on their phone keypad. The digits go to the telephony layer rather than the agent — they aren't spoken, they aren't in the transcript, and the recording is paused around them. The charge is handled in a separate flow while the caller is still on the line.
How VoicePay works →GATING
In a collections flow, the payment node is unreachable until the required disclosures have actually been delivered on that call. It isn't a prompt instruction the model might skip — it's a branch condition in the graph. The trace shows what was said and when.
See the collections workflow →PLANS
Tokenize once and schedule the rest. Arrangements are workflow state, not a rep's memory — installments run on schedule, failures trigger a follow-up call, and a broken promise routes somewhere instead of disappearing.
DUNNING
A declined renewal is churn on a timer. Voicent calls the customer, takes the updated card over the keypad, and retries the charge on the same call — recovering the subscription instead of adding another email to a dunning sequence nobody opens.
POST
Transaction, outcome, and arrangement written back to your collection platform, store, or CRM as part of the same workflow. Reconciliation isn't a nightly export someone has to babysit.
See the connector directory →SEE
Every workflow is a visible map of steps and decisions. Before a single consumer hears the agent, your compliance reviewer can read what it says, when it may ask for money, and where it stops. No prompt in a black box you have to trust.
Browse the template library →The numbers
Recovery economics or nothing. These stay blank until they're measured against real portfolios — an invented recovery rate is worth less than an empty box.
Two operations. One primitive.
Past-due receivables and failed subscription charges are the same workflow with different disclosure requirements — a call that has to end in a posted payment.
Disclosures delivered before the flow will accept a dollar, payment captured over the keypad, arrangements tracked as workflow state — across a queue depth no dialer floor can staff.
ARM agencies · debt buyers · medical and dental receivables · property management · utilities · lending servicers
See the workflow →A declined renewal is churn on a timer. Voicent calls, takes the updated card over the keypad, and retries the charge on the same call — instead of adding one more email to a dunning sequence nobody opens.
subscription boxes · DTC brands · membership and SaaS billing · 3PLs and high-AOV retail
See the workflow →Also running on Voicent
These work, and we support them. But if you're here because money is owed and nobody has time to call for it, the two above are where the platform is deepest.
Card and ACH taken on the live call, with the digits handled by the telephony layer — so the card number doesn't reach the agent, the transcript, or the recording.
See how payment capture worksImplementing voice AI for clients rather than for yourself?See the agency platform
Questions we get asked
Card entry is handled by the telephony layer, so the digits are never spoken to the agent, never written to the transcript, and not present in the recording or your application logs — the places that would otherwise pull those systems into scope. What that means for your own PCI assessment depends on your wider environment; we'll walk your assessor through the call path.
Required disclosures, call frequency and time-of-day limits, right-party verification, and cease-communication handling are modeled as workflow nodes and branch conditions rather than prompt text. Every call leaves an execution trace showing what fired. Your counsel should review the specific flow before it dials.
The flow stops asking. Refusal, dispute, attorney representation, and cease requests each route to their own branch — logged, flagged, and excluded from further dialing according to the rules you set.
There are prebuilt connectors for the payment, commerce, and CRM systems these operations run on, and anything with an API can be connected. Tell us your stack and we'll confirm before you buy.
Cost per dollar recovered, net of platform and telephony spend — with outcomes verified against posted transactions rather than inferred from a transcript. If a metric can't be tied to recovery or cost, we don't put it on a dashboard and call it success.
Bring a real queue segment to the call. We'll map the flow, show you the disclosure gating, and model what recovery costs you per dollar before you commit to anything.