← Back to library

Have an agent work each client Slack request

Dale Spoonemore described an automation at his company that watches a client's Slack thread. Each new message kicks off a Devin investigation, files an issue in Linear and prepares a reply. Nothing goes to the client without his approval, a dashboard tracks open issues by client, and fixed issues trigger a follow-up draft.

  • OutcomeWatch a shared Slack channel with a client, open an investigation and a ticket for each new message, and route a drafted reply to you for approval.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditDale Spoonemore (@DaleSpoonemore)
View original
Works with
Custom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

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?

  1. Watch the channelFire the automation whenever the client posts in the shared channel.
  2. Open a ticketCreate an issue with the message, client name and link.
  3. InvestigateStart an agent session to reproduce or research the issue and attach findings.
  4. Draft and approvePrepare a reply in your voice; a person approves before it posts.
  5. 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)

Prompt3 variables
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?
The poster plans to loosen control only once drafts reliably match how he wants to speak.
Why a dashboard?
It shows which issues are open for which client so nothing waits silently.

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.

More in Customer Support

All 27 Customer Support playbooks →

Related playbooks

Customer SupportPrompt✓ AI dry run

Find the bugs in your intake chatbot with one test chat per rule

Write a small set of test chats, each aimed at one rule in your bot's field spec with the stored values you expect written down first, and catch errors a large pile of happy-path chats misses.

Credit: Adam (Adam13y)

Under an hour
Customer SupportWorkflow✓ AI dry run

Book tutoring sessions through a WhatsApp chat agent

Let parents and students book, move and confirm lessons in WhatsApp with an agent tied to the tutoring calendar and its booking rules.

Credit: MarcoKueks on Hacker News

An afternoon+
Customer SupportPrompt✓ AI dry run

Clean up saved support replies before your bot reuses them

Read every saved answer your support bot can pull from as if it were about to be sent to a stranger, rewrite the risky ones into generic answers and set rules so new ones are written that way.

Credit: Pierre-Laurent Medori

Under an hour
Customer SupportPrompt✓ AI dry run

Generate app help videos from code, not screen recordings

Have a coding agent build a help page whose tutorial videos are scripted and rendered automatically, so they can be regenerated whenever the app changes.

Credit: Nadia I (@NIftek)

An afternoon+
Customer SupportWorkflow✓ AI dry run

Hand callers from a phone bot without repeats

Design an AI phone line so callers can reach a person quickly and the staff member sees everything the caller already said.

Credit: u/Philodendron60 on r/VetTech

Under an hour