Track a list of contacts and get alerted when they change jobs. This is especially useful when you want to reconnect with people who already know your product and reach out right as they start a new role.
By the end of this tutorial, you’ll know how to create a job change signal agent in lemlist, choose the right contacts to monitor, set your daily identification limit, and decide how new signals should be processed.
Why this matters
Job changes are strong outreach signals because they often create a natural reason to reconnect. Instead of checking manually, lemlist monitors your selected contacts daily and creates a signal as soon as a job change is detected.
Each detected signal can include the contact’s new job title, new company, headline (when available), location, start date, and LinkedIn URL.
Before you start
You should already have access to Signal agents in lemlist.
You should already have either:
an existing contact list in lemlist, or
a CSV file of contacts you want to monitor.
You should know which audience you want to track, such as former customers, champions, or warm contacts.
How job change signal agents work
Choose the Contact changed job signal type.
Select who to monitor using either a specific segment or an existing lemlist contact list.
lemlist checks for updates daily.
When a change is found, a new signal is created so you can review or act on it.
Core lesson: Set up your signal agent
Phase 1: Start a new signal agent
Go to Signal agents, then click Create signal agent to begin. This opens the guided setup where you’ll choose the signal type, audience, and processing rules.
Phase 2: Choose the signal to detect
In the signal agent builder, open People moves, select Contact changed job, then continue. This tells lemlist to specifically look for job change events instead of other buying or engagement signals.
Phase 3: Name your signal agent
Enter a clear Agent name, then click Next. Use a name that helps you recognize the audience later, such as Former customers - job changes or Champions to monitor.
Phase 4: Choose which contacts to monitor
Select the scope you want to use. You can monitor:
Contact list to track people from an existing lemlist list
Specific segment if you want to use a CSV file
This choice determines where lemlist will pull the contacts from for daily checks.
If you choose Contact list, select the list you want to monitor. If you prefer to use a CSV, choose Specific segment and upload or define the segment from your file instead.
Phase 5: Set your daily identification limit
Choose the maximum number of signals identified per day. This controls how many job change matches lemlist can identify daily and helps you manage both volume and credit usage.
Keep in mind:
Each identified signal costs 100 credits.
A lower limit is useful when you want tighter control over spend.
A higher limit is better when you’re monitoring a larger audience and want faster coverage.
Phase 6: Decide how signals should be processed
Choose how you want new job change signals to be handled:
Review signals manually if you want to review each one yourself first
Auto-create tasks if you want your team to follow up through task management
Auto-push to campaign if you want contacts to move straight into an outreach workflow
This step is important because it determines whether signals stay for review or immediately trigger action.
If you choose to auto-push contacts into a campaign, review the extra options carefully:
Choose which campaign should receive the contacts.
Decide whether to include contacts already linked to existing signals.
Set rules for leads that are already in another campaign to avoid accidental overlap.
Phase 7: Review and confirm
Review your setup, including the signal type, billing details, processing method, and segment being monitored. Once everything looks correct, finalize the signal agent.
Practical example
Let’s say you want to reconnect with past users who were already familiar with your product. You can create a job change signal agent for a saved contact list of former customers.
Select Contact changed job as the signal.
Choose your existing list of former customers.
Set a daily identification limit that matches your available credits.
Either review signals manually or send them directly into a campaign designed for warm re-introductions.
When a former customer moves to a new company, you’ll get a fresh signal with key details like their new title and company. That gives you a timely, relevant reason to reach out.
Best practices
Start with a focused list. Smaller, high-intent audiences usually give better results than very broad monitoring.
Name signal agents clearly. Use names based on the audience or use case so they’re easy to manage later.
Set a realistic daily limit. Match the identification cap to your team’s follow-up capacity and credit budget.
Use manual review first if you’re testing. This helps you validate signal quality before automating campaign actions.
Create dedicated outreach messaging. Job change signals work best when your message acknowledges the new role or company context.
Troubleshooting and common pitfalls
Issue: No signals appear right away
Root cause: Job change monitoring runs daily, so results may not show immediately.
Fix:
Wait a few days for the first checks to complete.
Confirm the selected audience contains valid contacts to monitor.
Make sure your identification limit is not set too low for your expected volume.
Issue: The wrong contacts are being monitored
Root cause: The wrong contact list or CSV segment was selected during setup.
Fix:
Review the signal agent summary before finalizing.
Use clear contact list names to avoid confusion.
If needed, recreate the signal agent with the correct list or segment.
Issue: Credits are being used faster than expected
Root cause: The daily identification limit is set too high for your current budget.
Fix:
Lower the maximum number of signals identified per day.
Focus on a smaller, more qualified audience.
Review whether all monitored contacts are still relevant.
Issue: Contacts are entering campaigns too quickly
Root cause: Automatic campaign processing was selected before the workflow was fully tested.
Fix:
Start with Review signals manually while validating the setup.
Switch to automatic campaign routing only after confirming the signals and campaign rules are correct.
Double-check rules for contacts already present in other campaigns.
What to do next
Once your signal agent is live, check your incoming signals regularly and build outreach that matches the context of the job change. A timely, relevant message is what turns this signal into real pipeline.