Tag it in a channel
Mention Ballet on a message and it reads the thread: the ticket, the account, whatever has already been said.
Two ways to ask
Tagging keeps the answer next to the question. A DM is for when the request isn't a conversation yet.
Message it directly
A DM works like the side panel. Ask for a playbook by name, or just say what you need.
The result lands in the thread
The answer posts where the question was asked, so nobody has to relay it.
This work already starts in Slack
Someone asks a channel, and it turns into forty minutes in four tabs. Ballet answers the message instead.
The same reviewed playbook
Asking in a channel doesn't skip anything. The gates your engineers set still apply.
Visible to whoever asked
The output lands in the thread. Everyone who was following can see what ran.
Exceptions come back as questions
When a record doesn't fit the rules, Ballet says so in the thread instead of guessing.
No new tool to adopt
Nobody needs a login for the system the workflow touches, or a reason to leave Slack.
There are two other ways in
The playbooks and the governance are the same in all of them.
Platform
Build and run the workflow
Where a workflow gets written, reviewed, and watched once it's live.
Platform →
Chrome extension
Run playbooks beside the tab you're in
A side panel next to your CRM or helpdesk. Ask for something, or type / and pick a playbook.
Chrome extension →
Claude connector
Build and run playbooks inside Claude
Connect Ballet in Claude and ask it to run a playbook, read what happened, or build a new one.
Claude connector →
Slack agent
Tag Ballet where the work already happens
Mention Ballet on a message, or send it a DM. The result posts back in the thread.
You're herePut it in your busiest channel
Think of the request your team fields over and over. We'll build it, and you can tag Ballet for it instead.