Skip to main content
Implementation Guide · Module 3 of 9 · ~10 minutes

​
Why this matters

Your team’s chat channels hold context that doesn’t exist anywhere else: internal strategy discussions, quick updates after calls, requests for help on tricky deals. When you map channels to accounts, Endgame can reference these conversations when answering questions. A rep asking “What’s the latest on Acme?” gets answers informed by what the team has been saying internally, not just what’s in the CRM. Endgame supports both Slack and Microsoft Teams. Connect whichever platform your team uses, or both if your org spans both.
If your team doesn’t use Slack or Microsoft Teams, skip this module and move to Upload Knowledge.

​
What you’ll do

  • Connect Slack and/or Microsoft Teams to Endgame
  • Map account-specific channels to the right accounts
  • Optionally configure organization-wide channels (Slack)

​
Before you start

  • Slack: You need to be a Slack Administrator or have approval from one.
  • Microsoft Teams: The connecting user must be a Teams Global Administrator.
Check with your IT team if you’re not sure about your permissions.

​
Slack walkthrough

1

Start the connection

Navigate to Settings > Integrations and click “Connect” next to Slack. This kicks off the Slack OAuth process.If you’re not a Slack admin, you’ll see a request approval screen. Submitting this sends a notification to your Slack admins via Slackbot.
2

Grant permissions

Click “Allow” on the Slack permissions page to give Endgame access.
3

Map channels to accounts

You’ll land on a configuration page where you map public Slack channels to Endgame accounts.How to think about mapping: For each major account, select the Slack channels where your team discusses that account. Common patterns include:
  • Deal channels: #deal-acme, #opp-bigcorp
  • Account channels: #acme-internal, #bigcorp-support
  • Customer channels: #ext-acme (shared channels with customers)
You can map multiple channels to a single account. Add them one at a time.
4

(Optional) Add organization-wide channels

Organization-wide channels don’t map to specific accounts but enable multi-account Endgame conversations within Slack. Good candidates: #sales-team, #pipeline-review, #competitive-intel.Select the channels under “Organization-Wide Channels” and submit.

​
Microsoft Teams walkthrough

1

Start the connection

Navigate to Settings > Integrations and click “Connect” next to Microsoft Teams. This kicks off the Teams authentication process.
2

Authenticate and grant consent

Select the Microsoft account you want to connect and go through the authentication flow. Make sure to check the box for “Consent on behalf of your organization” to give Endgame access to the necessary scopes.
3

Map channels to accounts

Once connected, click “Manage” to open your configuration. From here you map public Teams channels to Endgame accounts:
  1. Select a channel you want to associate with an account
  2. Choose the account to associate with that channel
  3. Click Add
You can map multiple channels to a single account. Remove associations anytime by clicking the trash icon.

​
Channel mapping strategy

Start with your top 10-15 accounts by revenue or strategic importance. You don’t need to map every channel on day one. A focused initial set gives you something to validate in Module 7 (Test Drive), and you can expand from there.
Endgame can’t distinguish between different account conversations in a single shared channel. Use channels that are dedicated to a single account for best results. A #general-deals channel with mixed account discussions won’t produce clean account-level intelligence. This applies to both Slack and Teams.

​
Checkpoint

You’ve completed this module when you’ve mapped at least one channel to an account in Slack or Teams. Endgame will begin ingesting messages from mapped channels every 15 minutes.

​
Go deeper

Previous Module

Connect Transcripts

Next Module

Upload Knowledge