Setup Guide 2 of 3 Testsigma
Slack Alerts

Get notified in Slack
when a contact changes jobs

Apollo can push a Slack message directly to your team the moment a job change is detected - no need to log into Apollo to check. You mentioned using this for customer account monitoring, and you can use the exact same setup for your own contact database.

Two alert modes - choose what fits your team
Via Apollo app in Slack
Apollo Slack app (native)
Install the Apollo app directly in Slack. Job change alerts come through the Apollo bot - up to 3 channels. Easiest setup, no third-party tools.
Recommended
Via Workflow → Slack action
Embedded in job change workflow
Add a Slack notification step directly inside the Workflow B (company move) you've already set up. Fires conditionally - e.g., only for net-new accounts.
More control
What you discussed on the call

You use Slack alerts internally already - getting a notification when a key contact joins or leaves a client organization. The same mechanism works natively in Apollo: you can receive alerts when any of your monitored contacts triggers a job change. You confirmed you want this included in the setup. The connection is direct Apollo → Slack - no Bitscaler or Nathan required.

Step 1

Connect Apollo
to your Slack workspace

The Apollo Slack integration is a native connection - no API keys or third-party automation tools required. Takes about two minutes.

Setup steps
1
Go to Apollo Integrations
In Apollo, navigate to Settings → Integrations → Slack. You'll see the Slack integration card.
2
Authorize the Apollo Slack app
Click Connect to Slack. You'll be redirected to Slack's OAuth screen. Sign in with your Testsigma workspace and click Allow. Bhavani should do this with an account that has Slack admin rights.
Permissions required
Apollo requests read access to channel names and write access to post messages. It does not read message history.
3
Confirm the connection
Back in Apollo, the Slack card will show Connected with your workspace name. You're ready to configure which alerts get sent where.
Connected - proceed to configure alerts
The integration is workspace-wide. Any Apollo user on your team can now receive or configure alerts - you don't need to reconnect per user.
Step 2

Configure
what triggers an alert

Apollo lets you set rules so you only get notified for job changes that actually matter. You can filter by signal type, seniority, company size, or whether the contact is tied to a specific list.

Alert trigger options
In Apollo: Settings → Slack Alerts → New Alert Rule
Alert type
Job change (company move)
Job change (title only)
Contact joins a target account
Contact leaves a target account
Recommended filters for Testsigma
// Recommended setup based on your use case:

Trigger: Job change - company move
Filter 1: Contact is in list "Active Accounts - Key Contacts"
Filter 2: New company headcount > 50 // optional - prevents noise
Filter 3: Contact seniority = Manager, Director, VP, C-Suite
Two recommended rules for your team
Rule 1 - Customer account monitoring
Alerts when a key contact at one of your existing customers changes jobs. Useful for Bhavani to track relationship continuity across accounts.
List: Customer Key Contacts
Type: Company move
Channel: #apollo-customer-alerts
Rule 2 - Prospect / pipeline monitoring
Alerts when a contact in your active outbound pipeline moves companies. Lets BDRs pause and re-route immediately before sending to a dead address.
List: Active Sequences
Type: Any job change
Channel: #apollo-bdr-alerts
Step 3

Set up
your alert channels

Apollo supports up to 3 Slack channels per alert rule. You can route different alert types to different channels - keeping BDR noise separate from admin/ops visibility.

Recommended channel structure for Testsigma
# apollo-job-changes
Primary ops channel
Receives all job change alerts across your full contact database. Bhavani as primary owner. Used for daily review and workflow triage.
Recommended
# apollo-bdr-alerts
BDR team channel
Filtered alerts only - contacts in active sequences who've moved companies. BDRs can act immediately (pause, reroute, or flag for Sakshi).
Optional
# apollo-champion-moves
Champion re-engagement channel
Alerts only when a previously closed-won or high-value contact moves to a new company. Warm intro opportunities surface here automatically.
Optional
How to create private channels in Slack
In Slack, click the + next to Channels → Create a channel → set to Private → invite Bhavani, Sakshi, and BDR leads. Then add the channel name to your Apollo alert rule.
Alert Preview

What an alert
looks like in Slack

When Apollo detects a job change matching your rules, a message is posted to the configured channel via the Apollo bot. Here's an example of what your team will see.

Example: company move alert
# apollo-job-changes
A
Apollo App · Today at 9:14 AM
🔄 Job change detected - Priya Nair has moved companies.
Contact: Priya Nair
Previous companyFinTech Startup Co.
New companyTestsigma
New titleHead of Quality Engineering
New emailpriya.nair@testsigma.com
Workflow statusOld record marked departed · SFDC updated
Example: champion move (re-engagement alert)
# apollo-champion-moves
A
Apollo App · Today at 2:47 PM
Champion on the move - Arjun Mehta just joined a new company. Previously interacted with Testsigma.
Warm intro opportunity
ContactArjun Mehta
New companyRapidTest Labs (Series B, 280 employees)
New titleVP of Engineering
Suggested actionEnroll in champion re-engage sequence