Slack-native
Monty waits for a mention, a DM or an approved trigger — then works in context.
Your team’s next teammate
Monty is an agent-native teammate for the work already happening in Slack. It investigates, makes a plan, produces the deliverable and stops for you exactly where your policy says it should.
Alex O. @Monty turn this thread into a client-ready SOP
I found the decision trail, the latest process and two edge cases. I’m preparing the SOP with sources.
Build a specialist for dispatch, customer success or executive briefings. Give it the right context. Let rules make the safe decisions repeatable.
Monty waits for a mention, a DM or an approved trigger — then works in context.
OAuth apps, API keys, MCP servers and custom HTTP tools live behind clear grants.
Every run, action, approval and handoff is visible, explainable and reversible where it can be.
Customer handoff prepared
Sentiment crossed your escalation rule. No outbound message sent.
Q4 service recovery brief is ready
18 threads · 3 calls · policy-cited
A teammate, not another tab
Chat with Monty, inspect the exact context it used, approve work, adjust rules and build new agents — all from a workbench that stays connected to Slack.
Explore the control centerWork in the open
Mention Monty, send a DM or let an approved event start the work.
Monty reads permitted context, creates artifacts and proposes actions in the right place.
Policies decide whether Monty observes, drafts, sends, escalates or stops.
Your systems, on your terms
Start with Slack. Add Quo/OpenPhone, GitHub, email, your internal API or an MCP server when the policy is ready. Monty discovers the tools, but your team grants the authority.
Explore integrationsBuilt for teams that move