Collections · Voice Workflow
Collections Call + Payment Link
When handle_payment fires, the workflow reads the account, delivers the mini-Miranda, handles objections, and either captures a keypad payment via VoicePay or texts a secure payment link.
Workflow
How it runs, step by step
- 01TRIGGER
Tool call: handle_payment
The agent invokes handle_payment when the caller is ready to discuss their balance.
- 02MEMORY
Read account
Pull the balance and promise-to-pay history from Zep.
- 03VOICE
Required disclosure
Deliver the mini-Miranda and any jurisdiction-required disclosures.
- 04AI AGENT
Handle objection
Detect willingness to pay and respond to objections.
- 05BRANCH
Pay now?
Branch on whether the caller will pay during the call.
- if willing → Capture payment
- if not now → Record promise-to-pay
- 06INTEGRATION
Capture payment
Collect card details over the keypad and tokenize via VoicePay, so the digits never reach the agent.
- 07INTEGRATION
Record promise-to-pay
Log the promised payment date to memory.
- 08BRANCH
Payment approved?
Branch on the payment processor response.
- if approved → Confirm payment
- if declined → Send payment link
- 09VOICE
Confirm payment
Confirm the payment and that a receipt is on its way.
- 10INTEGRATION
Send payment link
Text a secure hosted payment link for the caller to use later.
- 11INTEGRATION
Text receipt
Send a payment receipt by text via Twilio.
- 12MEMORY
Save outcome
Write the call outcome and next action to Zep.
- 13END
Return tool result
Return the result to the agent.