Support answers pulled in the Slack thread
A team member at Spur, a support company, posted about their internal Slack agent, Doozy. Staff mention it in a thread and give it a task in plain words. It runs the task in a fresh sandbox. It holds no keys of its own. Gateways add the access each request needs. It can query the database, payments, code, and the issue tracker. It posts the answer and any file back in the same thread.
Start with one job only. Fill in the three lines. Keep the bot on that job.
The one job this bot does: ______________________________
What it may do on its own: ______________________________
What it must ask me first: ______________________________
Two lines from this case, side by side. No new figures.
A team member at Spur, a support company, posted about their internal Slack agent, Doozy. Staff mention it in a thread and give it a task in plain words. It runs the task in a fresh sandbox. It holds no keys of its own. Gateways add the access each request needs. It can query the database, payments, code, and the issue tracker. It posts the answer and any file back in the same thread.
13 people at Spur use it daily, per the poster. Most are support and success staff, not engineers. Destructive tools stay off until the owners turn them on. His report, from his post.
The after line is the source's claim, not our measurement.
smalloffice.space · Get a case like this in your inbox each morning. Subscribe free
Read this case on your phone now, and keep it for later. Type your email. We send this case to that address, and you get the next cases each morning too.