How to track complaint deadlines with an AI agent

Start the clock correctly and the rest is arithmetic. The agent spots complaints in every channel, dates each from the day it arrived, applies the deadline rules compliance has approved, and warns handlers before each deadline. It drafts holding letters for staff to send and reports every breach. People classify disputed cases and write the responses.

What does complaint deadline tracking involve, and who owns it?

Most regulated firms must acknowledge complaints, resolve them or send a final response within set periods, and tell customers where they can go if they remain unhappy. The periods differ by market, product and complaint type, and some are counted in business days. A firm that misses them has a conduct problem on top of whatever caused the complaint.

The head of complaints owns handling. Compliance owns the deadline rules and monitors the book. Handlers own individual cases. The agent does the watching across the whole book, which is the part people do badly at volume. It is the easy part, as complaints handling with agents: deadlines are the easy part argues, but it still has to be right. The wider position is in our guide to AI compliance agents.

What are the steps, and who acts at each one?

1. Person, compliance: writes the deadline rule table. For each complaint type and market: what starts the clock, each deadline, business or calendar days, holidays, and what the customer must be told at each point. Versioned and approved.
2. Agent, depth 1: reads incoming contact in every channel and flags anything that expresses dissatisfaction and asks for something, whether or not the customer uses the word "complaint".
3. Agent, depth 1: proposes a classification against your complaint classification matrix, which sets the rule that applies.
4. Agent, depth 3: starts the clock on the date the complaint first reached the firm, in any channel, not the date it was logged. Where classification is disputed, the strictest applicable clock runs until a person decides.
5. Person, complaints team leader: confirms disputed classifications.
6. Agent, depth 3: tracks every case against its deadlines and sends warnings to the handler and team leader at points you set before each one.
7. Agent, depth 2: drafts holding and delay letters that tell the customer where things stand and what they can do. A handler sends them.
8. Agent, depth 3: records breaches the moment a deadline passes, with the case history, and adds them to the compliance report.
9. Person, handler: writes and sends the final response.

Which controls matter, and what evidence does each leave?

Receipt date, not log date. The clock starts from the earliest evidence the complaint arrived: the email timestamp, the call record, the branch note. Evidence: the source and time of the receipt date for each case.

Rule table version on every case. When a rule changes, you can see which cases ran under which version. Evidence: version reference per case.

Strictest clock while disputed. If a person later decides the contact was not a complaint, the agent stops the clock with that person's reason. Evidence: the decision and reason.

No silent extensions. The agent cannot pause or extend a clock. Only a rule in the table, applied to recorded facts, does that. Evidence: any paused clock names the rule.

Breaches are filed as they happen. Evidence: breach records with timestamps, not reconstructed at month end.

What should you measure?

• Cases closed within each deadline, by type and team, as counts against volume.
• Near misses: cases closed in the final days before the deadline. A rising count predicts breaches.
• Lag between receipt and logging. The bigger it is, the more the agent's correction of the start date matters.
• Complaints found by the agent that staff had not logged.
• Holding letters drafted against holding letters sent.

Where does it usually go wrong?

Complaints hide in other channels. A dissatisfied social media message or a remark in a call is a complaint under many rules. If the agent only reads the complaints inbox, it misses them.

Holidays are wrong. Business day counts depend on the calendar for the market. Keep one approved calendar per market and treat it as part of the rule table.

Deadlines drive the work instead of the fix. Teams send fast final responses to protect the numbers. Track how many reopen.

Warnings become noise. Too many alerts and handlers ignore them. Send fewer, at fixed points, to the person who can act.

Transferred cases lose their clock. A complaint passed between teams, or to a third party that handles part of the service, often restarts in the receiving system. The agent should carry the original receipt date across every transfer and flag any case whose start date moved.

Root causes go nowhere. Breaches and themes should become remediation items; see how to track remediation actions with an AI agent. New rules on handling should flow into the rule table, which is where whether an AI agent can track regulatory change matters.