Recourse and dispute resolution
A path from any single agent action to a dispute about it, so an affected person can raise a dispute without first reconstructing what the agent did.
The impact of agents
As agents complete more of a user's actions without a person reviewing each one, the things that can go wrong multiply, but the path back from any one of them to someone who will look at it does not get easier to find. The dispute must be anchored to the specific action record, so the user never has to re-narrate the entire history to be heard.
What must be verified
Every disputed action must be traceable to its own action record, and answered within a defined time bound. The service provider holds the obligation to meet that bound.
Protecting access
Recourse is where exclusion compounds. A user disputing an agent's error is often already in hardship or distress, which makes language and literacy barriers, unreliable connectivity, and the lack of someone able to act on their behalf even more costly. Some users give up at an engaged phone line. Others get routed into a months-long process while the error stands.
Keeping the path open
- Give assisted channels (phone, in person, advocate-lodged) equal standing and the same time bound as the digital route.
- Make the dispute affordance on the receipt operable by keyboard and screen reader, with its filed state announced, so raising a dispute doesn't depend on a control only some users can see or click.
Response surface
A dispute is anchored to a specific action on the record, so raising one starts from the agency's own account of what happened rather than from a blank form.
Dispute action TX-2026-4829
We’ve filled in the record for you. You only need to tell us what went wrong.
New disputes arrive with the action record attached. The response clock starts when a dispute is received.
Submit the dispute on the left to watch it arrive here. Each dispute is tagged to an agent or model version and also counts toward the overall error rate. When many users report the same fault, it registers as one pattern rather than as unconnected phone calls.
Maturity
- Established
For chargeback and ombudsman models, long-standing recourse mechanisms grounded in Regulation Z, PSD2, and ombudsman accountability practice.
- Emerging
For GDPR contest affordances on automated decision-making, which are beginning to appear.
- Frontier Headline
For agent-action-anchored dispute flows in government services, which remain undesigned.
Precedents
Regulation Z billing-error resolution, with PSD2. Card holders hold reversal rights: the issuer must acknowledge a dispute within 30 days, investigate, and within 90 days correct or explain. Pre-dispute resolution services settle issues before they reach a formal chargeback. The clock and the acknowledgment are specified, so the person knows what is owed to them and by when.
The Office of the Ombudsman, Malta. The model requires the public body to explain what it did and why once a complaint is lodged, and the ombudsman assesses whether the decision was reasonable and lawful and can surface systemic problems. Recommendations are not binding. The explanation duty is triggered by the complaint, and not by the decision that prompted it.
GDPR Article 22 contest rights. Article 22 provides the right to contest an automated decision and to express one's own point of view, where the legal basis is consent or contract; where a government automated-decision statute is the basis instead, the contest right is left to whatever safeguards that law provides. Either way it requires concrete affordances: a way to initiate a contest, a channel to add information, and a mechanism to receive a revised decision.
What carries over to agent use
The chargeback model is particularly instructive: the dispute is anchored to a specific transaction with a unique identifier, the burden shifts to the service provider to investigate, and there are time-bound response obligations.
What the chargeback model assumes, and government agent actions currently lack, is a unique, universal transaction identifier and an issuer with an independent incentive to investigate quickly. A government agency defending its own agent's action does not have that same institutional separation, so the burden-shift has to be designed in rather than inherited. The ombudsman model adds the requirement that disputes can surface systemic issues, not just individual errors.
Where things go wrong
Where this goes wrong is recourse that is effectively inaccessible, trapping users in engaged phone lines while errors stand, or met with a boilerplate acknowledgment that closes the clock without addressing the dispute's substance. Anchoring disputes to specific action records with time-bound response obligations forces earlier correction.
Sources
7 references
The instrument, the operating deployment, or the official record itself.
Writing about the subject rather than the framework itself, including vendor commentary.