Compress a long support thread for a specialist

Specialists should not re-read forty messages to find the ask. Brief them. Don't dump.

This hack: twelve minutes, one long thread, specialist summary. Distinct from VIP routing: this is thread compression for any escalation.

When to use it

• A thread is long and needs a specialist.
• Basic troubleshooting already happened.
• You can state the ask in one sentence.

When not to

• Thread is short. Just @ them.
• You haven't read it. Read first.
• Customer is waiting on a promise you can keep now.

Do this (timer on)

1. 1. Paste the thread (redact secrets).
2. 2. Produce summary: problem, tried, evidence, ask.
3. 3. Route with summary on top.

Prompt (copy)

Compress this support thread for a specialist.

Output:
- One-sentence problem
- Customer impact
- Timeline (bullets)
- What was tried
- Current hypothesis (labeled guess)
- Exact ask for specialist
- Links / IDs

Do not invent troubleshooting.

THREAD:
[paste]

After you send

If specialists always re-discover context, support handoff is the leak. Support Automation Audit when escalations thrash.

Start free assessment (Support Automation Audit) at https://faisalrizvi.com/ - See where we're wasting hours. 3 minutes. Score + prioritized roadmap. Shareable report. No login.

Book a free 30-min call only if you want a walkthrough after the roadmap.