If you work in sales, you know how easy it is to miss important updates. A deal moves stages. A new opportunity pops up. Someone pushes close dates back (again). If you live in Slack or Teams, you want those Salesforce updates to just show up where you work. That’s where Troops comes in—a tool that connects Salesforce with Slack or Teams and delivers real-time alerts so you don’t have to babysit dashboards or refresh tabs all day.
This guide is for anyone who wants to stop chasing Salesforce and start getting the updates that actually matter, right where your team works. No fluff, just the steps you need (and what’s not worth bothering with).
Why use Troops for Salesforce alerts?
Before we jump into setup, let’s be clear about what Troops actually does well—and where it can fall short.
What works: - Delivers Salesforce updates to Slack or Teams, fast. - Lets you set up alerts for just about any Salesforce event or field change. - Cuts down on “Did you see this?” emails and half-baked handoffs.
What doesn’t: - If your Salesforce data isn’t clean or your process is chaotic, Troops will just surface the mess faster. - Over-alerting is a real risk. Too many notifications, and people start ignoring them. - Troops isn’t magic—it won’t fix your Salesforce adoption problems.
If you want to get the most out of Troops, start simple and only alert on stuff you’d actually drop what you’re doing for. Now, let’s get it set up.
Step 1: Check your prerequisites
Before you dive in and try to connect everything, make sure you have:
- A Salesforce account with the right permissions (usually “API Enabled”).
- Access to Troops (if you don’t, talk to whoever manages sales tools).
- Admin or integration permissions in Slack or Teams.
- A rough idea of what you want to be alerted about (don’t skip this—think about what truly matters).
Pro tip: If you’re not sure what permissions you have, try logging into both services or ask your admin. Saves a lot of time.
Step 2: Connect Salesforce to Troops
This is the “wire them up” step. Here’s how:
- Log in to Troops. Go to the Troops dashboard (usually yourcompany.troops.ai or via their main site).
- Go to Integrations. Find the Salesforce section.
- Click “Connect.” Troops will walk you through OAuth—the standard Salesforce login screen pops up.
- Authorize Troops. You’ll need to grant Troops the right access to your Salesforce data. Don’t gloss over this—read what you’re agreeing to.
- Test the connection. Troops should confirm the link. If not, check your Salesforce permissions or try reconnecting.
What can go wrong:
- Wrong Salesforce user role (not enough permissions).
- Company security policies blocking the integration.
- Trying to connect a sandbox instead of production (double-check the environment).
Step 3: Connect Slack or Microsoft Teams
Troops needs to know where to send the alerts.
- In Troops, go to Integrations again.
- Click Slack or Teams and follow the prompts.
- Allow Troops to access your workspace. You’ll approve permissions so Troops can post to channels or send DMs.
Heads up:
- You need to be an admin in Slack or Teams, or get someone who is to do this part.
- Some companies lock down integrations tightly—it’s worth checking with IT before you hit a wall.
Step 4: Decide what you actually want to be alerted about
This is where most people go wrong. If you try to track everything, you’ll end up tracking nothing. Instead, start with just one or two high-impact alerts, like:
- When an Opportunity moves to a critical stage (e.g., “Proposal/Price Quote” or “Closed Won”).
- When a deal over a certain value is created.
- When close dates are pushed out.
- When an account has gone untouched for too long.
Ask yourself:
- Will I take action on this alert, or is it just noise?
- Who really needs to see this? The whole team, or just the rep?
Write down your “must-have” triggers before you build anything. Better to start lean and add later.
Step 5: Create your first Troops alert (“Workflow”)
Now for the fun part. Troops calls these “Workflows,” but really, they’re just automations for sending alerts based on Salesforce changes.
Here’s how to set up a basic alert:
- Go to the Troops dashboard and click “Workflows.”
- Click “Create Workflow” (sometimes called “New Alert”).
- Pick your Salesforce object. (e.g., Opportunity, Account, Lead)
- Set your trigger. This is the “when” something happens—like when the Stage field changes, or a new record is created.
- Add conditions. For example: “Stage = ‘Closed Won’ AND Amount > $50,000.”
- Choose your Slack or Teams destination. This can be a channel (for team-wide updates) or a DM (for more private nudges).
- Customize the message. Include key fields (like Opportunity Name, Amount, Stage, Close Date) so people don’t have to click through.
- Test the alert. Most platforms let you send a test message—use it.
- Save and activate.
What to ignore:
- Don’t get lost in fancy formatting or emoji. Clarity > cleverness.
- Don’t add 10 conditions just because you can. Keep it focused.
Step 6: Roll it out (and keep it sane)
Now that you’ve got alerts set up, don’t just turn them loose and hope for the best. Here’s how to keep things under control:
- Start with one or two alerts. Get feedback from the team before you add more.
- Watch for alert fatigue. If people start ignoring or muting the channel, you’ve gone too far.
- Refine as you go. Tweak the triggers, clean up the message, drop anything that’s not useful.
- Set expectations. Make sure people know what each alert means—and what they’re supposed to do with it.
Pro tip:
Check the channel (or chat with your team) after the first week. If no one’s acting on alerts, kill or tweak them. Silence is a signal.
Step 7: Troubleshooting and tips
Some common issues and how to handle them:
- Alerts not firing: Double-check your conditions. Are you testing with the right data? Sometimes the record needs to be edited after the workflow is live.
- Duplicate messages: Make sure you haven’t set up overlapping triggers.
- Wrong people getting alerts: Check your channel/DM settings. Troops lets you route based on owner or team—use it.
- Data delays: Troops is “real time” but only as fast as Salesforce allows. Sometimes there’s a lag of a few seconds to a minute.
- Security/privacy: Be careful not to blast sensitive deal info to the whole company. Use private channels or DMs for anything confidential.
Final thoughts: Keep it simple, tweak as you go
Setting up Salesforce alerts in Troops is straightforward if you focus on what matters. Start with the alerts you’d actually act on, not just what’s possible. Don’t turn on every bell and whistle—alert fatigue is real, and nobody wants more noise in Slack.
Once you’ve lived with your first alert for a week or two, refine it. Add another if you spot a real gap, but always ask: will this help someone do their job better, or is it just digital clutter?
You don’t need to monitor everything—just the stuff that actually moves the needle for your team. Keep it simple, and iterate. That’s how you’ll actually get value from real-time sales updates.