{"id":6531,"date":"2026-09-24T08:22:19","date_gmt":"2026-09-24T06:22:19","guid":{"rendered":"https:\/\/atlax360.com\/?p=6531"},"modified":"2026-11-04T13:24:39","modified_gmt":"2026-11-04T12:24:39","slug":"ai-voice-agents-collections","status":"publish","type":"post","link":"https:\/\/atlax360.com\/en\/blog\/ai-voice-agents-collections\/","title":{"rendered":"AI Voice Agents in Collections: What a Real Call Sounds Like"},"content":{"rendered":"

For years, automating collections meant automating email.<\/strong> Templates, reminders and sequences that fire 5, 15 and 30 days after the due date. It works well until the debtor stops opening the email. And then someone on your team has to pick up the phone.<\/p>\n

In our most recent webinar, we showed, live and without a safety net, what happens when it is an AI voice agent who picks up. Two calls to the same debtor, two agents with opposite tones and two different outcomes. And afterwards, what almost no one shows: the configuration screen behind it.<\/p>\n

The question is who decides who gets called, when, through which channel, in what tone, and what happens to what the debtor says in response.<\/p>\n

Here is what was covered in the session, with the full video so you can listen to it yourself.<\/p>\n

From spreadsheet to orchestrator: the three models that coexist today<\/h2>\n

In the meetings we hold every week with credit and collections teams in Chile, Peru, Colombia, Mexico and Spain, we almost always come across one of these three realities.<\/p>\n

1. Manual collections<\/h3>\n

The manager sends emails one by one or calls directly and logs payment commitments in a shared spreadsheet. Fewer and fewer operations work this way, for a simple reason: traceability depends on someone remembering to write it down.<\/p>\n

2. Static automated flow<\/h3>\n

Actions are triggered according to the stage each invoice is in (pre-due, due, post-due) and according to fixed rules defined by segment. This is a huge step up from the previous model, but it remains a rigid decision tree: always the same channel, always the same message, always the same day. And if the client replies to the email, the reply dies in one manager’s inbox.<\/p>\n

3. AI-orchestrated collections<\/h3>\n

An orchestrator is layered onto that flow to decide when, how and what to claim<\/strong>, invoice by invoice. It assigns tasks to each manager’s calendar, chooses the most effective channel for each client type (email, WhatsApp, SMS or a voice call) adjusts the tone and, above all, reads and interprets the debtor’s response.<\/p>\n

This is the difference between automating tasks and delegating operational judgement. The orchestrator handles the volume; the manager handles the decisions that require human judgement.<\/p>\n

Listen to the calls: the same debtor, two different agents<\/h2>\n

In the demo, Macarena Donoso, who is responsible for Chile, Peru, Colombia and Mexico at Atlax 360, played both the collections manager and the debtor: she configured the agents and then answered the phone herself.<\/p>\n

Webinar video<\/em><\/a><\/p>\n

The first call was deliberately set up to go wrong.<\/strong> The task concerned an invoice more than 90 days overdue, close to being declared a bad-debt claim, and it should have been handled by the escalation agent. It was mistakenly assigned to Marcela Montes, the initial-claim agent. The result was a flawless, friendly call and entirely wrong for that stage of the debt. That live mistake explains, better than any slide could, why tone is not a cosmetic detail: it is part of the collections policy.<\/p>\n

Next came the second call, from Ram\u00f3n Oviedo, the legal-escalation agent. You can listen to it here: video.\u00a0<\/strong><\/em><\/a><\/p>\n\n<\/thead>\n\n\n\n\n\n
Agent<\/strong><\/td>\nAssigned role<\/strong><\/td>\nTone<\/strong><\/td>\nPoint in the cycle<\/strong><\/td>\nHow the call ended<\/strong><\/td>\n<\/tr>\n
Marcela Montes<\/td>\nInitial invoice claim<\/td>\nWarm and collaborative<\/td>\nEarly days after the due date<\/td>\nThe debtor commits to checking the payment with Finance and agrees to a follow-up call<\/td>\n<\/tr>\n
Ram\u00f3n Oviedo<\/td>\nEscalation prior to legal action<\/td>\nFirm and direct<\/td>\nMore than 90 days overdue<\/td>\nRejects instalment terms, sets a final deadline and closes with a specific day and time for follow-up<\/td>\n<\/tr>\n
Marcela Montes<\/td>\nIncident verification<\/td>\nWarm and collaborative<\/td>\nOverdue invoice with payment blocked<\/td>\nIdentifies a commercial dispute and refers it to the relevant team<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The third call is the most interesting one for any collections manager: the debtor had not paid because she had received eight boxes instead of ten, and damaged ones at that. The agent did not press for payment. It acknowledged the problem, logged the case and escalated it. When the orchestrator detects a commercial dispute, it automatically notifies the salesperson assigned to that account, because the issue is no longer one of collections.<\/p>\n

The 7 parameters that define a collections voice agent<\/h2>\n

A voice agent is not “hired<\/em>“, it is configured. These are the seven parameters that determine its behaviour within Yndika’s collection management module.<\/p>\n

    \n
  1. Role and purpose of the call.<\/strong> Initial claim, legal escalation, dispute verification, or an administrative task, such as requesting the purchase order without which no invoice can be issued.<\/li>\n
  2. Tone and personality.<\/strong> From warm to firm. Defined in writing and tested before it is switched on.<\/li>\n
  3. Language, voice and accent.<\/strong> Configurable by segment. This has a real impact: in some markets we have found that a particular accent gets far more responses than the local one.<\/li>\n
  4. Agent disclosure.<\/strong> Whether the agent must identify itself as a virtual agent at the start of the call. In countries such as Colombia, regulations require the call to be identified as debt-collection management, and this rule is built into the flow.<\/li>\n
  5. Negotiation scope.<\/strong> The maximum acceptable term, whether instalments are permitted, and what interest or collection costs apply under your arrears policy.<\/li>\n
  6. Originating number.<\/strong> Calls are placed from a number belonging to your own company, not from a call-centre prefix that no one picks up any more.<\/li>\n
  7. Escalation and referral.<\/strong> Which channel is triggered if there is no answer (WhatsApp, SMS or email) and which manager or salesperson the case is referred to.<\/li>\n<\/ol>\n

    With these seven fields, a team of three collectors can operate with five or ten agents assigned to their department, each playing a different role. Capacity grows without growing headcount.<\/p>\n

    Behind the tone lies the data: how the orchestrator decides<\/h2>\n

    A voice agent with no data is simply a robot dialling in chronological order. What turns these calls into a recovery strategy are the risk indicators that Atlax 360 models for each client:<\/p>\n