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

# Slack & Teams

> Connect Slack and Microsoft Teams, map partner channels, and configure internal notifications in Introw.

export const provider_0 = "Slack and Microsoft Teams"

**Open in Introw:** [Integrations](https://app.introw.io/settings/integrations?category=communication)

## How it works

Slack and Microsoft Teams appear as tiles on the Communication tab. You connect via OAuth, then
configure the integration on its page. External channels map a Slack or Teams channel to a specific
partner for collaboration; internal channels post org notifications when partner activity occurs,
optionally scoped by partner or filter. Both of Introw's AI agents also answer in these channels:
partners @-mention the support agent in shared channels, and your team @-mentions the internal agent
in internal channels.

Notification event types, pipeline updates, form submissions, tasks, and more, mirror the patterns in
the Notifications settings. You map a channel per partner and choose which events post where.

## Ask Introw in {provider_0}

Introw runs two AI agents inside {provider_0}, so partners and your team get answers
and take action without leaving chat. Both read live from your CRM source of truth
and act only within each person's own access - partners stay scoped to their portal,
your team stays scoped to theirs.

<CardGroup cols={2}>
  <Card title="Partner support agent - shared channels" icon="robot" href="/features/ai/partner-support">
    In a shared partner channel, partners just **@-mention Introw** to ask the same questions they could in the portal - deal status, commissions, tiers, content, or even registering a deal - and get an instant, scoped answer.
  </Card>

  <Card title="Internal agent - internal channels" icon="chart-line" href="/headless/agentic-use-cases/ecosystem-performance">
    In your internal channels, your team **@-mentions Introw** to get insight on the partner ecosystem and act on it - handle open form submissions, surface best-performing partners, check pipeline, and update partner records.
  </Card>
</CardGroup>

### Partners self-serve in shared channels

@-mention Introw in a shared partner channel and the [partner support agent](/features/ai/partner-support)
answers from your knowledge base and live portal data, scoped to that partner. It is the
same agent partners use in the portal, now in {provider_0}: it can answer questions in any
language and take action on the partner's behalf - register a deal, update a record, or
surface the right asset - without anyone on your team being pulled in.

### Your team gets ecosystem insight in internal channels

@-mention Introw in an internal channel and the internal agent answers questions about
your whole program and acts on it, scoped to your access - no portal hunt and no RevOps
ticket. For example:

* **Handle open work** - "Show me open form submissions," then approve, reject, or follow up on [deal and lead registrations](/features/forms/submissions-approvals) right from chat.
* **Spot what's working** - "Who are my best-performing partners this quarter?" to pull [ecosystem performance](/headless/agentic-use-cases/ecosystem-performance) on demand.
* **Update partners** - "Move Acme to Gold" or "add a note to this partner" to change partner records on the fly.
* **Check the numbers** - "What's this partner's pipeline and commission status?" for a live readout.

<Note>
  Both agents depend on the [partner support agent](/features/ai/partner-support) being
  enabled. Each agent only ever sees and does what the person talking to it is allowed to -
  partners are scoped to their own portal data, your team to your program.
</Note>

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  chat["Slack or Teams"] -->|"OAuth"| introw["Introw"]
  introw --> external["Partner channels"]
  introw --> internal["Internal notifications"]
  introw --> agents["Support and internal agents"]
```

## Prerequisites

* Admin access to your Slack workspace or Teams tenant.
* Integrations write access.

## Settings & configuration

Chat integrations are managed at [Integrations](https://app.introw.io/settings/integrations?category=communication).

### Connect

Use the Slack or Microsoft Teams tile to authorize via OAuth.

### Partner channels

Map an external channel to each partner for collaboration; override per partner where needed.

### Internal notifications

Post org notifications to internal channels, scoped by partner or filter, for events like pipeline
updates, forms, and tasks.

### Notification events

Choose which event types post; these follow the patterns in your Notifications settings.

## Setup walkthrough

<Steps>
  <Step title="Open Integrations">
    Go to [Integrations](https://app.introw.io/settings/integrations?category=communication).
  </Step>

  <Step title="Connect Slack or Teams">
    Authorize via OAuth.
  </Step>

  <Step title="Map partner channels">
    Map a channel to each partner.
  </Step>

  <Step title="Configure notifications">
    Choose internal notifications and where they post.
  </Step>
</Steps>

## How-to guides

<CardGroup cols={2}>
  <Card title="Configure Slack or Teams for partner activity" icon="book-open" href="/features/integrations/chat/guides/configure-the-chat-integration">
    Map internal channels to keep your team informed, choose which partner events post, and open shared channels with each partner for collaboration.
  </Card>

  <Card title="Connect Microsoft Teams to run partnerships in chat" icon="book-open" href="/features/integrations/chat/guides/connect-microsoft-teams">
    Authorize Microsoft Teams so Introw can post partner notifications, run shared partner channels, and keep your team in the loop without leaving Teams.
  </Card>

  <Card title="Connect Slack to run partnerships in chat" icon="book-open" href="/features/integrations/chat/guides/connect-slack">
    Authorize Slack so Introw can post partner notifications, run shared partner channels, and keep your team in the loop without leaving Slack.
  </Card>
</CardGroup>

## Limits & gotchas

<Warning>
  External channels are mapped one per partner for collaboration; internal channels are for your own team. Notification event types follow your Notifications settings, so review those to avoid noise. Both AI agents in chat depend on the partner support agent being enabled, and each agent is scoped to the access of whoever @-mentions it - partners to their portal, your team to your program.
</Warning>

## Troubleshooting

* **Notifications are not posting** - confirm the channel mapping and that the event type is enabled.
* **A partner's messages are in the wrong channel** - check the per-partner channel override.
* **The connection dropped** - re-authorize the Slack or Teams integration.