DebtOps.
A voice agent that holds a repayment conversation, reaches an agreement a human would have reached, and writes that agreement back into the system of record.
What we built
Three agents, one write path.
The write path is the constraint the rest of the design hangs off. Everything below exists to make that one path safe enough to leave running.
- Agents
- The negotiator holds the conversation policy. The verifier checks every commitment before it is written. The escalation agent hands to a human, mid-call.
- MCP servers
- Telephony, CRM and the ledger. The ledger server is the only path that can write, and the agreed plan is the only thing it writes.
- Guards and schemas
- Hard limits the agent cannot cross, enforced in code. A plan outside the limits cannot be offered, let alone written.
- Evals
- A graded set of real transcripts, and a regression suite that reruns on every model change.
- Observability
- Traces, cost and latency per call.
- Runbook
- What on-call opens at 2am.
What changed
The outcome, stated honestly.
No figure appears on this page until it can be sourced. A qualitative statement a client would recognise is worth more than a percentage nobody can trace.