Run Slack support investigations in a sandbox with external tool gateways
At a glance
Spur built a Slack assistant so support staff could check customer records and investigate suspected bugs without waiting for engineering. This workflow is listed under customer-support, slack-automation, agent-sandboxing, tool-gateways.
- Agents / tools
- Doozy, Slack, Postgres, Stripe, E2B
Building a tool for these workflows? See weekly rates.
What they did
The initial bot read Postgres and Stripe and used Slack search to recover files it could not read directly from a thread. Its creator rebuilt it as Doozy: a thread mention starts a job in a fresh E2B sandbox, model and tool calls pass through external gateways, and findings and files return to the thread.
How it went
The creator reports that 13 Spur employees use the internal assistant daily, especially support and customer-success staff. This usage report describes the internal predecessor to the rebuilt product.
Worth knowing
Destructive tools start disabled and owners enable them individually. The creator warns that prompt injection can still misuse tools the agent is allowed to call.