Getting started
Half an hour, one channel, and something real connected.
There is no migration, no data import, and no separate place your team has to start going. The whole first session fits in a lunch break, and about fifteen minutes of it is your job.
The first session, at a glance
Us before you arriveYou about 15 minutes of your time
The session
Five steps. Most of them are not your job.
Usbefore the call
The app, the console, the model endpoint.
The bot is one Go binary with the console embedded, talking to Slack over Socket Mode — an outbound websocket, so there is no public URL to expose and no inbound firewall rule to ask anyone for.
It runs wherever you want it: a container on your own infrastructure, a Cloud Run service, or a box under a desk. Storage is a single database, replicated off-box if you want it replicated.
You15 minutes
Install the Slack app and invite it to one channel.
A workspace admin installs the app and invites the bot to a single channel — the noisiest one you have, ideally, because that is where it either earns its place or does not.
Set ALLOWED_EMAIL_DOMAINS at the same time and guests, Slack Connect members and shared channels are out from the first minute rather than after the first incident.
Together20 minutes
Connect one service and point it at some documents.
Pick something real — the repo you are on call for, the ticket tracker, the error tracker. A preset fills in the hosts and the auth style, Test connection proves the token before you save, and if you would rather not hold the secret yourself, a setup link sends that job to the person who does.
Drop in whatever documentation you have. It is chunked, embedded and searchable in a couple of minutes, and a document can be scoped so it only answers in the channel it belongs to.
Youthe rest of the session
Try to break it.
Ask it something that needs three lookups. Ask it to change something and watch it stop. Feed it a document with an instruction hidden in it. Ask it about a private channel you are not in.
This is the part that decides it, and it is the part most vendors will not sit through with you. We would rather you find the edge on a Tuesday with us in the room.
Youwhenever you like
Widen it one channel at a time.
Every channel is its own scope: its own instructions, its own model, its own budget, its own connections. Nothing is workspace-wide until you attach it to the workspace.
So the second channel is a decision you make with a month of evidence behind it — not a migration you committed to on day one.
What we need from you
Three things, and none of them is a project.
A Slack admin
For half an hour, to install the app and invite the bot to one channel.
One credential
For one service you actually use. Or the name of the person who holds it — a setup link does the rest.
A model endpoint
OpenRouter, a vendor API, or your own host. Bring a key or use ours for the session.
No procurement conversation is required to run the first session, and turning it off afterwards leaves your Slack exactly as it was.
Questions
Asked on most first calls.
Anything not here, ask on the call — or read the guardrails, which answer most of the rest.
Do we need to open a port or expose a URL?
No. The bot connects to Slack over Socket Mode, which is an outbound websocket from wherever it runs. Nothing on your side listens for Slack, so there is no inbound rule to ask a network team for.
Where does our data go?
It stays in the one database the bot runs against, on your infrastructure. The only thing that necessarily leaves is the model call itself — to the endpoint you chose. Credentials are sealed at rest and injected by the proxy at the network edge, so they are never in a prompt.
Which model do we have to use?
Any OpenAI-compatible endpoint. It ships pointed at z-ai/glm-5.3-flash through OpenRouter, and the workspace, a channel and a single thread can each be switched to a different model from the console.
Can it change things in our systems during the trial?
Only after a person confirms. Any write is held in the thread with a Confirm card, and writes that grant access go to an approver instead of the asker. Reads are never held. You can also leave the first channel read-only by giving it a connection with no write methods at all.
What does it cost to run the first session?
Nothing beyond the model calls, which are metered and shown under each reply. Set a budget for the channel before you start and the bot pauses at the ceiling. The subscription is quoted per workspace, not per seat — see pricing.
What if we decide against it?
Remove the app from the workspace and stop the container. There is no data import to unwind and no separate place your team was sent to, so your Slack is exactly as it was.
Pick a channel and we will bring the rest.
One admin, one credential, one model endpoint. We do the rest before the call.