With Troops, you can use Signals to surface critical data into your Messaging Platform. There are two different Signal types:

  • Real-Time Notify your team when a field changes or an object is created in any of your connected Sources.

  • Scheduled: Notify your team of the current state of fields in your connected Sources on a scheduled cadence.

While each may be used for different reasons, their setup is largely similar.

To set up a Signal:

  • Navigate to your Signal library

  • Click Create New Signal

  • Select your Signal type

  • Choose your Source system

After giving your Signal a name, there are 3 required sections to complete- Conditions, Recipients, and Message. Optionally, you can add filters and actions to your Signal:

Conditions

When should this signal fire? Build the logic sentence that, when true for a record, will cause the signal to display in Slack or Microsoft Teams:

There are a variety of operators to choose from depending on the field type being selected.

Note:

  • Choose whether you want the signal to fire when ANY or ALL of the conditions are met with the "And/Or" toggle

  • If you want a signal to fire only when a record (like an Opportunity) is first created, there is a toggle setting

  • Scheduled signals allow you to choose the date and time you want the signal to fire

Recipients

When the trigger conditions are met, where should this Alert be sent? Depending on the Alert type, Troops can send Alerts to:

  • Slack channels, both public and private (invite the Troops bot to a private channel to see it appear).

  • Individual Troops users.

  • User reference fields. Troops can match an Opportunity Owner in Salesforce with their Slack account, for example, and send a signal to them.

  • User email address fields. Any field that contains an email address in your source system

Message

The message section is where you can completely customize the signal's content. Display the information related to the particular signal use case. You can even display fields from related objects.

Before Saving the Signal...

  • Rename the Alert to make it easy to find in the Signal library

  • You can "send a sample" to yourself to see how your Alert appears in Slack or Microsoft Teams

You're all set! Once you Save the Signal, it will "go live".

  • There may be a short period of data synching before the Alert is 100% reliable

  • Troops will begin to evaluate records that meet the trigger conditions once live; it will not "backfill" and alert-bomb existing records that meet the trigger conditions

Did this answer your question?