When should you use it?
- Clients report issues in shared Slack channels
- Requests get lost between chat and your tracker
- You want faster first responses
Not for: Teams without a ticket tracker; Auto-replying to clients from day one
What do you need, and what do you get?
You need
- Shared Slack channel
- Issue tracker
- Coding or research agent
- Reply guidelines
You get
- Ticket per request
- Investigation notes
- Draft reply for approval
- Status dashboard
How does it work, step by step?
- Watch the channelFire the automation whenever the client posts in the shared channel.
- Open a ticketCreate an issue with the message, client name and link.
- InvestigateStart an agent session to reproduce or research the issue and attach findings.
- Draft and approvePrepare a reply in your voice; a person approves before it posts.
- Close the loopWhen the ticket is fixed, draft a follow-up to the client for approval.
The prompt
Our own prompt, inspired by Dale Spoonemore (@DaleSpoonemore) and written to work in Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
A client just posted in our shared Slack channel. Message: {message}. Client: {client}. Link: {link}. 1. Summarize the request in one line and classify it: bug, question, feature request. 2. Draft a ticket title and description with steps to reproduce if known. 3. Draft a reply under 80 words that acknowledges the issue and states the next step. No promised dates. Return all three for my approval.
Inspired by Dale Spoonemore (@DaleSpoonemore): Every day at @HelloUntangle has had a different focus when it comes to improving and automating our processes.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Duplicate tickets when a client posts several messages about one issue; group by thread.
- Draft tone drifts; keep a short style guide the drafts follow.
Our take
Dale Spoonemore described a client Slack watcher: each new message kicks off a Devin investigation, files a Linear issue and prepares a reply, while nothing reaches the client without his approval. A dashboard tracks open issues by client, and fixed issues trigger a follow-up draft. The best line is that nothing reaches the client automatically yet. That is the right order: automate intake, investigation and drafting first, then earn trust before letting go of the send. The follow-up after a fix is easy to forget and is exactly what clients notice. Add a rule for grouping related messages so one issue does not spawn three tickets. Group tickets by thread, and keep a short style guide the drafts follow so tone does not drift. Teams without a tracker should set one up first. Read every draft before approving it, and resist turning on automatic replies until the drafts have been right for weeks.
Where the time goes back: Triage, ticket creation and first drafts happen as messages arrive, so your time goes to approving answers.
FAQ
When can replies go out automatically?
Why a dashboard?
Source and credit
Inspired by Dale Spoonemore (@DaleSpoonemore). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Every day at @HelloUntangle has had a different focus when it comes to improving and automating our processes.
- Creator
- Dale Spoonemore (@DaleSpoonemore)
- Published on
- X
- Original date
- Oct 9, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.