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

# Using the Chamelio Teams Integration

> Initiate flows and start agent conversations directly from Microsoft Teams

The Chamelio Teams integration lets your organization interact with Chamelio directly inside Microsoft Teams, in two distinct modes: one available to any designated user (including viewers such as sales, procurement, or finance) for initiating flows, and a more open-ended mode reserved for agent users — typically the legal team — to start agent conversations.

## Initiating Flows

Any user with access can kick off a flow from Teams, in one of two ways depending on how the flow's Intake step was configured:

<Tabs>
  <Tab title="Mentioning Chamelio">
    Tag Chamelio in a dedicated channel — for example, asking whether an agreement exists with a given counterparty. Chamelio reads the tagged message and replies in the thread within moments, optionally with a summary and links to relevant documents. Works well for Q\&A-style flows, like letting sales ask about contract terms or policies.
  </Tab>

  <Tab title="Submitting a form">
    Click the **+** icon in Teams to open the app picker, select Chamelio, and choose from the available forms (e.g. an NDA generation request). After completing the required fields and submitting, the request appears as a task in Chamelio. Some requests may include an approval step — for example, granting Chamelio permission to upload the resulting file to OneDrive — before you can access the output.
  </Tab>
</Tabs>

## Agent Conversations

Reserved for agent users — generally the legal team — for a more open, direct exchange with Chamelio's AI agent from within Teams. Mention Chamelio inside an existing thread so it reads the surrounding context and responds with a summary, or start a private, standalone session to ask a question directly.

<Tip>
  Use channel mentions for quick, contextual questions and forms for structured requests with defined fields. Reserve agent conversations for users who need broader, unstructured access rather than a fixed flow output. Building the underlying flows — including configuring the Teams intake — is covered in the flow-building guide.
</Tip>