> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openmote.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Communications

> Connect Slack, Microsoft Teams, or Telegram so Roomote can start, continue, and summarize work from chat.

Communications providers are the chat and collaboration surfaces where people
already coordinate work.

Roomote can run from the web dashboard alone, but a communications provider
turns it into something you can reach from wherever work is happening. You can
start tasks from chat, continue an existing task thread, receive updates while
the agent works, and get proactive summaries when background work needs
attention.

## Supported providers

Roomote supports these communications providers:

| Provider        | Best for                                                                   | Notes                                                                       |
| --------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Slack           | Teams that already coordinate work in Slack channels and threads           | Can also be used as a Roomote sign-in provider.                             |
| Microsoft Teams | Teams that use Microsoft 365, Teams channels, and Microsoft Entra accounts | Can also be used for Roomote sign-in and account linking through Microsoft. |
| Telegram        | Lightweight personal or group chat access                                  | Useful when you want a simple bot-driven chat surface.                      |

Configure communications providers from **Settings > Communications**.

Slack and Microsoft Teams can do two jobs:

* they can be task surfaces where Roomote starts, resumes, and reports on work
* they can be authentication surfaces so users sign in or link the same
  workplace identity they use in chat

This matters because task ownership follows the person who asked for the work.
When identities are linked, Roomote can attribute a task to the right user,
respect access rules, and continue the right thread when someone replies later.

## Why chat matters

Chat is useful even if you are the only person using Roomote.

With a communications provider connected, you can:

* start a task from your phone without opening the dashboard
* ask follow-up questions while you are away from your computer
* run multiple tasks in parallel, each in its own thread
* keep long-running work visible without babysitting the web UI
* receive progress updates, blockers, PR links, preview links, and final
  summaries where you already check messages
* hand work off between devices by continuing the same chat thread
* let proactive automations post task suggestions or summaries when something
  needs attention

For teams, the same workflow becomes shared. A channel thread can hold the
request, Roomote's updates, review links, and follow-up decisions in one place.
That makes agent work easier to review than a private browser tab, especially
when several people need to understand what changed or decide what happens
next.

## Common workflows

Use communications providers for:

* **Starting work from a conversation.** Mention the Roomote app or message the
  bot with a task request. Roomote can route the request to an environment and
  start work from the conversation context.
* **Continuing a task.** Reply in the same thread to give new instructions,
  answer a question, or ask Roomote to make another change.
* **Monitoring parallel work.** Keep separate tasks in separate chat threads so
  each one has its own updates, links, and final summary.
* **Receiving proactive summaries.** Automations and background checks can post
  summaries to the configured chat destination when there is something useful
  to review.
* **Remote control.** Start, steer, or unblock work from mobile chat when you
  are away from your development machine.

## Setup checklist

Before connecting a communications provider, make sure your deployment has:

1. a public URL that the provider can call back into
2. provider app or bot credentials
3. at least one Roomote user who can sign in
4. an environment that tasks can run against

After connecting the provider, run a small task from chat and confirm that:

* Roomote acknowledges the request in the same conversation
* the task appears in the dashboard
* replies in the thread continue the same task
* final summaries and links are posted back to chat

## Authentication and linking

Slack and Microsoft Teams can also help control who can use your deployment.
When configured for sign-in, users can authenticate with their Slack workspace
or Microsoft account instead of relying only on email/password invites.

Users can also link their chat identity after signing in. Linking is important
when a message comes from chat: Roomote needs to know which Roomote user that
Slack or Teams person represents before it can start work, resume a task, or
apply user-scoped permissions.

If someone asks Roomote to do work from chat before their account is linked,
Roomote prompts them to link the account and then continues once the link is
complete.

## Related setup

Communications providers are only one part of a working Roomote deployment.
Most deployments also need:

* [Compute Providers](/compute), so tasks have sandboxes to run in
* [Environments](/environments), so tasks know which repositories and setup
  commands to use
* [Integrations](/integrations), so tasks can reach source control, issue
  trackers, monitoring, docs, and MCP-backed tools
* [Automations](/automations), if you want proactive summaries and scheduled
  work to post back into chat