Agentic flooding is real. Your intake queue is next.

The cost of writing a formal complaint just went to roughly zero, and the queues that receive those complaints are buckling. A paper from Chris Schmitz, Lewis Hammond of the Cooperative AI Foundation, and Alan Chan of GovAI documents agentic flooding — surges in filings to public services driven by large language models generating text cheaply. TechCrunch reported on the research this week. If you run a business with any intake channel — support, warranty, refunds, disputes, quotes — this is a preview of your next twelve months.

What actually happened

The paper, Characterizing Agentic Flooding of Government Services, examines 84 potential flooding cases across 11 jurisdictions and concludes the phenomenon is likely happening widely today. The numbers TechCrunch cites are not subtle. Complaints to the UK housing ombudsman rose from 2,600 in 2022 to just over 7,000 last year. The US Consumer Financial Protection Bureau saw roughly 5x growth in complaints across the same period. The work is due to be presented at the AI Ethics and Society conference next month.

The finding that matters is who is doing the filing. This is not a spam story. "The vast majority of cases we find are people who are entitled to claim for something, claiming for that thing," Schmitz told TechCrunch. The barrier was never eligibility. It was the four hours of writing, the formatting, the knowing-which-form. An LLM removed that, and the latent demand showed up all at once.

The authors also flag the obvious wrong fix: agencies can throttle the flood by making filing expensive again, but cost-based barriers hit the people who needed the help most.

Why agentic flooding matters for your business

Your customers have the same tools. The person who would have grumbled and moved on now has a well-structured, citation-laden, three-page dispute letter in ninety seconds — and a follow-up sequence if you do not answer.

The wrong response is the one the agencies are being warned about: add friction. Longer forms, phone-only returns, a portal nobody can log into. That filters your good customers faster than your bad ones, and it is the exact posture that gets a business posted about.

The right response is to make the volume cheap to serve. Three moves, in order:

Structure the intake. Free-text email is the most expensive input you can accept. A short structured form — order number, category, desired outcome, evidence upload — turns a three-page letter into five fields your system can route without a human reading prose.

Auto-resolve the deterministic tail. A meaningful slice of any support queue is requests with one correct answer: order status, a refund inside policy, a reship on a confirmed-lost package. Those should never touch a person. Wire the rules to the systems of record and let them close themselves.

Route the rest with the context attached. When a human does get involved, they should open a ticket that already has the order history, the prior contacts, and the policy citation on screen. That is the difference between four minutes and twenty.

Capacity planning matters too. If your queue doubles, the question is whether that costs you two headcount or nothing. That number is decided by how much of the work is structured today, not by how fast you hire later.

Sources: TechCrunch, arXiv.