Chatting from Slack, Teams & Telegram
You don't have to open the web app to work with EnClaw agents — you can talk to them wherever you already work: Slack, Microsoft Teams or Telegram. The conversation feels the same everywhere — plain English in, real work out — but each channel has a few habits worth knowing.
Slack
Slack is where most people chat with EnClaw day to day. There are three ways in:
Direct messages
DM the EnClaw bot like you'd DM a person. This is the most natural way to work with your personal agent — it's private, and the agent already knows it's you.
@mentions in channels
In any channel the bot has been invited to, mention it: "@EnClaw what's the status of the Acme project?". The Orchestrator picks the right agent and replies in the channel (or in a thread, if you asked in one).
Channel-bound agents
Admins can bind an agent to a specific channel — for example, a Deal Desk Assistant living in #sales-deal-desk. In a bound channel, that agent answers everything; you don't need to name it. This is deliberate and exclusive: a bound agent answers only in its channel, and other agents stay out of it. If a channel seems to have a "resident" agent, that's why.
Live progress, in one message
When an agent takes on a longer task in Slack, it posts a single status message and edits it in place as it works — you'll see the message update through the steps rather than the channel filling with noise. When the task finishes, that message becomes the final answer.
Microsoft Teams
Chat with EnClaw through the Teams bot, exactly as you would in a Teams chat with a colleague. Ask questions, give tasks, approve actions — same conversation style as everywhere else. Teams works especially nicely alongside an Outlook connector, since your email and calendar live in the same Microsoft world.
Telegram
Message the EnClaw bot directly, or use it in a group chat your admin has enabled. In groups, mention the bot by its @username so it knows you're talking to it. Telegram supports the same stop and cancel commands as everywhere else.
Sticky routing — "why did the same agent answer me again?"
When the Orchestrator routes your question to a specialist, EnClaw remembers that choice for you in that channel or DM. Your next message goes straight to the same agent, without re-routing. This is called sticky routing, and it's usually exactly what you want — a follow-up question like "and what about next week?" lands with the agent that has the context, not a stranger.
The stickiness is per person, per channel. Your colleague in the same channel might be "stuck" to a different agent, and your DM stickiness is separate from any channel's.
If the wrong agent has stuck to you, just redirect — see the next section.
Directing a question to a specific agent
You never have to accept the Orchestrator's choice. To reach a particular agent:
- Name it in your message. "Ask the Project Manager agent to summarise this week's tickets" or "@pm, what's overdue?" — EnClaw understands you're delegating and passes the actual request (not the "ask the PM to…" wrapper) to that agent.
- Use its home channel. If the agent is bound to a channel, ask there.
- Chat with your own agent directly from My Agents in the web app.
Once you've redirected, sticky routing follows your lead — the agent you named becomes the one that keeps answering.
Stopping a task
Any running task can be cancelled from the same conversation. Just send one of:
stopcancelabort/stop
The agent halts at the next safe moment — usually within a few seconds. Anything it had already completed (say, an email that was approved and sent before you typed stop) stays done; anything still in flight is dropped. You can then rephrase and try again.
Where the outputs go
Work you start from Slack, Teams or Telegram behaves exactly like work started in the web app: files land in your File Space, and the run — with everything it produced — appears in My Sessions. So even a task you fired off from your phone in a taxi is waiting for you, fully accounted for, next time you open the app.