Chase a Slow Response

What it does

Writes the follow-up that unsticks something stuck in silence — a pending application, an unanswered request, a claim in limbo — firm enough to get a real reply, polite enough not to burn the bridge.

When to use it

• You applied, requested, or reported something and heard nothing back
• A person or office keeps saying “we’ll get back to you” and doesn’t
• You’ve followed up once already and are now unsure how hard to push

The skill

Act as someone skilled at moving stuck bureaucracy without making
enemies. Rules: no invented service-level guarantees or legal
deadlines — if there might be an official response time, say "ask
what their stated processing time is"; don't assert one. Calibrate
firmness to how many times I've already chased.

What I'm waiting on: [APPLICATION / REQUEST / CLAIM / DECISION]
Who owes me the response: [PERSON / OFFICE / COMPANY]
When I first submitted / last heard anything: [DATES]
How many times I've followed up: [NUMBER]
Any reference number or details: [PASTE]
Why it matters / any deadline of mine: [CONTEXT]

Give me:
1. The follow-up message: references my original request and its
   date/number, states plainly what I'm asking for, requests a
   specific response by a specific date, and stays warm.
2. Escalation calibrated to attempt number: gentle nudge (first
   chase), firmer with a deadline (second), asking to escalate to a
   supervisor or a named process (third+).
3. The question that forces movement: "can you tell me the current
   status and the expected date?" — harder to ignore than "any
   update?".
4. If still silence after this: the next realistic lever (a
   different contact, a formal complaint channel, an ombudsman to
   ask about) — named generally for my region.
5. A one-line record to keep of each chase.

Example output

[TO FILL AFTER TESTING]

Tweaks

• Ask for a status AND a date; “any update?” is easy to ignore, “what’s the expected completion date?” is not
• Reference numbers in the subject line get things found faster
• Keep every chase in one thread so the growing history is visible — silence looks worse stacked up