AI Blocks › Help your customers
Get a stuck customer issue unstuck and close the loop
Give it the stuck issue. Get the facts, an escalation brief and a reply that keeps its promises.
Get a stuck customer issue unstuck and close the loop is a free AI workflow for the job "Help your customers". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks · Thinking: high
What it does
Some tickets never close. The customer asks, support says "we're looking into it", engineering or the warehouse never hears a clear question, and the customer writes again, angrier. Support, with nothing new to say, promises a date nobody agreed to. The issue is now two problems: the original one and the broken promise. This workflow closes the loop. First it reads your docs, past tickets and chats and lays out what is already known about the issue, each source named, and what nobody has answered. Then it writes an escalation brief for the owner: the customer's impact, what was tried, what you need from them and by when. You send it and wait for a real answer or a real date. Then it drafts the reply to the customer and checks every promise against what the owner actually said, so the customer hears the truth once, from you.
You give it
- The issue and its history: what the customer asked and what was said back
- The customer's own messages, in full
- Who can fix this kind of problem and how to reach them
- Your docs, past tickets or chat logs on the topic (optional)
- Source text (optional)
You get
- What your records already say about the issue, each source named, and the open question
- An escalation brief with impact, what was tried, what you need and by when
- A reply to the customer with the real answer or date, checked so it promises only what was agreed
Use it when
- A customer has written three or more times and the thread has no answer.
- Support keeps saying "we're looking into it" because nobody inside has said anything.
- An issue needs engineering, the warehouse or a supplier, and the request to them is vague.
Steps
- Customer question researcher: Ask a customer question. Get an answer found across your docs, past tickets and chats, with each source named.
- Escalation brief writer: Give it a stuck customer issue. Get a clear escalation brief for engineering or leadership, with impact and what was tried.
- Customer reply drafter: Describe the customer's situation. Get a reply in the right tone, plus notes on what to check before you send it.
- Customer reply commitment checker: Paste the complaint and your draft reply. Get each promise checked, tone flags and a repaired draft.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
- Paste the issue, the customer's messages and who owns the fix. It finds the facts and writes the brief.
- Send the brief to the owner. Wait for an answer or a date and paste it back.
- Read the checked reply and send it. Note the date you promised.