My AI Agent Lost a Client: A Post-Mortem on Automation Without Guardrails

Description and use

An automated collections agent sent reminders to a customer who had already paid because of a stale input file, damaging the relationship. Freshness checks, escalation confirmation, and intent-based reply handling were added to prevent recurrence.

Problem

An automated collections agent sent payment reminders to a customer who had already paid, causing relationship damage and loss of business.

Outcome

The agent failed silently due to stale input data, sending inappropriate reminders and damaging client relations. Adding freshness checks, escalation confirmation, and intent-based reply handling prevented future failures.

Workflow

• 1. Export ageing report to a folder
• 2. Agent reads file and parses outstanding invoices
• 3. Classify invoices by days overdue
• 4. Select message template and personalize
• 5. Send message via WhatsApp
• 6. Log send and handle replies
• 7. Escalate tone as overdue days increase
• 8. Stop sending when invoice marked paid

Evidence

The agent kept asking for money that was already in the bank.

Source

The failure was in the input. The ageing export was generated on a schedule and dropped into a folder the agent read from.

Source

Freshness checks on every input the agent trusts.

Source