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

# Contact an employee through channels

> Message or call an AI Employee through a published channel, keep the right context, and handle requests for review.

You can work with an AI Employee through Odella chat or a supported email, messaging, phone, or meeting channel. Use a channel already set up for that worker; you do not need to configure a new one for every conversation.

For your first request, [start a chat in Odella](https://docs.odella.ai/workforce/chat.md). If your team prefers another channel, use the worker's current published contact details.

## Find the right contact

1. Open the worker's profile and its contact details where available. Check the name and role.
2. Use the published email address, number, username, or channel link. A **Connected** status alone is not a contact address or an invitation to a private room.
3. If a contact is missing, ask the manager to check the worker's channel setup and access policy. For Signal, use the published contact QR/link from its [setup guide](https://docs.odella.ai/workforce/channels/signal.md#5-share-and-test-the-contact), not a registration or device-linking QR.
4. Send a low-risk first message and confirm the reply before sharing sensitive material.

A published channel is not public permission to use the worker. Account membership, allowed contacts, group rules, and the worker's availability still apply.

## Choose a channel for the conversation

| Channel | How to use it |
| - | - |
| **Odella / web chat** | Start a direct conversation, attach supported files, and follow work with the available document and Computer panels. |
| **Email** | Send the brief to the worker's published address. Reply in the relevant email thread with corrections or missing context. |
| **Slack or Microsoft Teams** | Use the installed worker in an allowed conversation. Follow the configured direct-message, room, and mention rules. |
| **Signal, WhatsApp, Telegram, or Discord** | Message the published contact or installed worker where supported. Use the request's own approval controls when review is needed. |
| **Phone or meetings** | Call the assigned number or use the supported meeting flow when enabled. These are separate from browser Talk. |

For an administrator connecting a new channel, see the [channel setup directory](https://docs.odella.ai/workforce/communication-channels.md). Supported features and publication requirements differ by service.

## Keep the request and context together

Explain the desired result, approved sources, and anything the worker must not do. Ask follow-up questions in the relevant thread or direct conversation. In a shared room, consider who else can see the request, attachments, and reply.

Do not assume a new channel shares the entire history of an earlier chat. Identify the existing work and provide the necessary non-secret context rather than sending the same assignment again.

## Handle approvals and sign-in requests

An approval may arrive as a card, buttons, a reaction prompt, or a review link:

* **Signal:** react to the **approval message itself** with **👍 to approve once** or **👎 to deny**, when those decisions are offered. An ordinary thumbs-up message is not the approval action, and a reaction does not grant permanent permission.
* **Other channels:** use the buttons or review link shown on the current request. Do not assume Signal's reaction controls work elsewhere.
* **Browser sign-in or Vault requests:** follow the request into signed-in Odella. Enter secrets in the browser or Vault form, never in a message or email reply.

Only an authorized approver can make the decision. See [channel-specific approval controls](https://docs.odella.ai/workforce/approvals.md#approvals-in-each-channel) and [browser takeover](https://docs.odella.ai/workforce/computer.md) before continuing sensitive work.

## If the worker does not reply

Check the current contact, channel connection, allowed sender or room, mention requirements, worker availability, and account limits. Ask the manager to inspect [Activity](https://docs.odella.ai/workforce/activity.md) if needed. A delivered message or successful call connection is not proof that work finished; check the answer or resulting task before retrying.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.