Skip to main content

​
Where it lives

Slack & Teams sits under Settings, at Integrations.
The Communication integrations, with Slack, Microsoft Teams, WhatsApp and Zapier and the state of each connection.

​
Before you start

​
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

Introw runs two AI agents inside , 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.

Partner support agent - shared channels

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.

Internal agent - internal channels

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.

​
Partners self-serve in shared channels

@-mention Introw in a shared partner channel and the partner support agent 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 : 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 right from chat.
  • Spot what’s working - “Who are my best-performing partners this quarter?” to pull 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.
Both agents depend on the partner support agent 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.

​
Settings & configuration

Chat integrations are managed at Integrations.

​
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.

​
Automate it with a workflow

Once a workspace is connected, Send a chat message is a workflow action: a short plain-text nudge into Slack or Microsoft Teams, with {{partner}} standing in for the partner’s name. The partner’s channel posts into the shared channel mapped on that partner’s page, resolved when the message sends, so remapping a partner later moves every workflow with it. One fixed channel posts every run into the same place, which is for internal alerting rather than for reaching a partner. Only connected and active providers are offered, and with one connected there is no provider choice to make. A run for a partner with no mapped channel stops at that step with a note saying so rather than failing, which is worth knowing before chat becomes your only nudge. Reaching a quiet partner where they already are, rather than in a third email, is the point. See Re-engage quiet partners.

​
How-to guides

​
Troubleshooting

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.
Confirm the channel mapping and that the event type is enabled.
Check the per-partner channel override.
Re-authorize the Slack or Teams integration.