Start here
The free tool below runs entirely in this browser — no account, nothing stored or transmitted. Redact anything you would not want kept before you type it.
Open the companion tool →Why naming the decision changes the response
Support loops are optimized for volume: without a specific decision, a date, and an account reference, a request is indistinguishable from thousands of others. With them, it becomes a case that has to be routed somewhere.
The second paragraph is what moves it: stating that you will file a complaint with the relevant regulator if no human review happens by a stated date. That is not a threat, it is a factual description of what you will do next, and it is usually the sentence that gets a reply.
The protocol
- Write down the decision, the date, and the reference numbers from every contact so far, including chat transcripts and case IDs.
- State the one question a human needs to answer: why the decision was made, what record it relies on, or what evidence would change it.
- Request a written response, by email or in-portal message, within a stated period — two weeks is reasonable and specific.
- Name the regulator you will involve if there is no reply, and give them the date you will file.
- Send it through the company's official channel, and keep a copy of everything with the date you sent it.
- If the deadline passes, file the complaint with the regulator and attach the request. The escalation you described is now simply the next step you take.
What the tool does
Build a written request for human review of an automated decision or a support loop, with a reply deadline and a named escalation. It stores nothing and sends nothing.
Limit first: This is a request-drafting aid, not legal advice. Response obligations and oversight differ by industry and jurisdiction.
Open the companion tool →One human next step
Send the request today and put the follow-up date in your calendar. If the reply is another automated message, escalate to the regulator you named and reference your original request and its date.
Research log and safety checks
AI-assist path: not used for a verdict. The request is designed to be answered by a person at the company; the reader's own record of attempts and dates is the substance of it. §6.10: not a frontier-pace topic.
§0.5 protection result: category is rights-recourse; crisis-adjacent: no; fear/urgency/scarcity toolkit used: no. The protective function is free and the paid feature is convenience only.