There are multiple ways to route your Signals to different recipients. Below are the different options, and best practices and use cases for each one.


Troops Users

Individually select users with active Troops seats and send Signals to them.

Route Signals to Troops Users if you have a unique signal that needs to be sent specifically to one individual or group of individuals, and it doesn't make sense to scale that signal across other people within their role or teams.


User Groups

User Groups are an easy way to organize users and make sure a certain Signal gets sent to everyone in within that specific group of people.

Use cases and best practices:

  • Region-based Groups to share when a big deal in the region is closed

  • Revenue Leadership Groups to ensure everyone has the visibility they need to collaborate efficiently

  • Setting up User Groups for Signals


Channels

Send messages to channels, both public and private.

Best practices:

  • To route Signals to a private channel, you must first invite the Troops bot to the channel.

  • Members of recipient channels who do not have active Troops seats will be able to see the Signals, but will not be able to take action directly via the Signal in Slack or MS Teams.


Reference Fields

Troops can match users within Source reference fields to their Slack or MS Teams account, making it easy to send Signals to people at scale based on fields such as role when specified things happen within records they are associated with.

Reference Fields: Account/Opportunity Team Support

For Signals based on Salesforce Account or Opportunity objects, you can easily and dynamically route real-time Signals to all of the right people within a Salesforce Account or Opportunity Team, either individually or as group messages to drive collaboration and action.

Note that Account and Opportunity Team recipients can only be set for real-time Signals and for Signals that are based on the Account or Opportunity objects, respectively.

Use Cases

When...

Send Signal to...

Key activity occurs within an opportunity

Opportunity Owner

Opportunity next step due date is overdue

AE and Sales Manager within Opportunity Team

Opportunity close date moves out of quarter

Sales Manager and Executive Sponsor within Opportunity Team

Opportunity stage moves from Prospecting to Qualification

SDR, AE and Sales Manager within Opportunity Team

Opportunity stage moves to Technical Validation

SE within Opportunity Team

Opportunity forecast category moves to Commit

Executive Sponsor within Opportunity Team

Account health score or average NPS score changes

CSM, AM and Support rep within Account Team

Customer employee count increases by 50%

CSM and AM within Account Team

ARR increases by X% or account status changes to at-risk

Exec sponsor within Account Team


User Email Address Fields

Send Signals based on any field that contains an email address in your Source system.


Send as Group Message

You can route messages individually or as group messages. Simply toggle the Group Message switch on or off.

Did this answer your question?