Maya, Cura's voice agent, works past-due accounts on real calls for credit unions and community banks — verifying identity, securing commitments, processing payments, with TCPA, Reg F, and FDCPA compliance enforced in-line.
Delinquency signals arrive from the core. Maya works the account inside a compliance perimeter. What surfaces is a payment, a promise, and a record that holds up.
Verifies identity, assesses hardship, negotiates arrangements, and captures consented payments — escalating to your team with full context when judgment is needed.
Append-only and tamper-evident. Every contact, disclosure, utterance, and disposition — recorded, timestamped, and ready for your CCO or examiner.
Contact-side gates clear compliance before a word is spoken. Resolution-side gates close the account and write the record.
One call, one audit record, organized around what a compliant collector actually does, not a vendor's feature list.
Cura adds the autonomous recovery layer your team does manually today and closes the compliance gap every outbound program carries.
Credit unions and community banks cannot profitably staff overnight and weekend collections for 30 to 90 day buckets. Maya covers those hours autonomously, with full compliance, and hands off to human agents only where judgment is required.
TCPA, Reg F, and FDCPA are pre-dial gates, not post-call audits — a rule-violating call never goes out. Every enforcement event is logged for examination; state overlays apply automatically by member address.
Single-tenant, inside your VPC — recordings, transcripts, payment data, and member information never leave your environment. Under Mode C, even the language model, speech-to-text, and text-to-speech run inside your network. The public demo uses synthetic data only.
Because Cura runs on the same financial-crime platform as your AML and fraud monitoring, it carries capabilities that are structurally impossible for a point-solution collections bot to replicate.
Cura cross-checks AML and fraud signals before every call. A suspected scam, elder-fraud, or account-takeover victim is held for human review — a standalone collections bot only sees the debt; Cura sees the whole member.
Cura reaches current-but-stressed members before they miss a payment, offering a no-penalty hardship option at first contact. Every outreach decision logs a model card and decision rationale, so it stays explainable to an examiner.
A configurable menu of options is offered before charge-off, matched to the member situation — not defaulted to whichever closes fastest.
Maya negotiates only within the settlement-authority matrix you define. Any offer outside those bounds routes to a human with full call context and a tamper-evident audit record — you set the floor.
Every collections decision is tested for disparate impact under the four-fifths rule, with an SR 11-7 model card and per-decision explainability — UDAAP and fair-lending defensible from day one, not retrofitted after an exam finding.
Maya handles the full recovery conversation, from opening disclosure to payment confirmation. Human agents step in only where judgment is required.
Maya understands natural language, not button presses — a member who says "I lost my job" gets an arrangement offer, not a menu re-prompt.
Maya captures card or checking details on the call and reads back a confirmation number before it ends.
Maya detects escalation signals — explicit request, distress, dispute, or threat — and offers a warm transfer or scheduled callback.
Compliance is a pre-dial gate, not a post-call audit. If a call would violate a rule, Maya does not place it.
Calling windows verified against the member address local time (8 AM to 9 PM) before every dial. Consent status checked for mobile numbers. No TCPA violation is possible: the call does not go out if the window is closed.
Contact frequency tracked per account across all channels. Maya will not place the 8th call in a 7-day window. The frequency cap is enforced at the dialer level, not as a recommendation.
Mini-Miranda delivered on every initial contact before any account information is disclosed. Cease-and-desist requests logged, flagged, and honored: no further Maya outreach is placed on the account.
California, New York, Wisconsin, and Texas have calling-hour restrictions and disclosure requirements that exceed federal minimums. Cura applies state overlays automatically based on the member address zip code.
Every compliance enforcement event is written to an append-only audit log. The log is available for examination on demand and can be exported for regulatory review.
Single-tenant in your VPC. Your KMS keys. Your network controls. Member data, call recordings, and payment data never leave your environment.
Standard Anthropic API for the voice language model. Lowest barrier to entry, fastest path to first live call. Suitable for institutions comfortable with cloud LLM inference from within their VPC perimeter.
Bedrock, Vertex, or Azure. Your cloud, your model, your compliance posture. No inference data leaves your cloud boundary. Preferred for institutions with existing Bedrock or Azure OpenAI agreements.
Language model, speech-to-text, and text-to-speech all run inside your VPC — no outbound network, ever. Support reaches you only through MCP tunnels you initiate and audit.
How Maya stacks up against IVRs, auto-dialers, and traditional collections operations.
30 minutes. Working demo on synthetic data. Compliance configuration walkthrough for your institution's rule set. No commitment, no multi-tenant SaaS.
Tell us a little about your team and we'll set up a walkthrough.