Outbound

How to route LinkedIn leads to the right sales rep, with the reason each one qualified

Route LinkedIn leads to the right sales rep by territory, segment or owner: one saved view per rep, a route to Slack or the CRM, and why each lead qualified.

By the traxy teamPublished Nov 13, 202616 min read

TL;DR: To route LinkedIn leads to the right sales rep automatically, save one view of leads per territory, segment or account list, then connect each view to that rep's destination with a route: their Slack channel, or a webhook, Zapier or n8n flow that writes the lead to your CRM. In traxy, an automatic route sends each new lead that enters the view and clears the route's ICP match threshold, and every lead keeps the post or comment behind it, so the rep sees why the person qualified. Assign the lead to the rep and add a note so that reason stays on the record.

We make traxy, so read this as the vendor's guide. Every traxy step below comes from the traxy docs pages linked in each section: routes, saved views, tags, notes and assignments and Slack, checked November 13, 2026.

How do I route LinkedIn leads to the right sales rep automatically?

Pick one routing rule your team agrees on (territory, segment or account owner), turn each rule into a saved, shared view of leads, and add one route per view to that rep's destination with Auto delivery. New leads that match a rep's view then go to that rep without anyone sorting them by hand. In traxy it works in four parts:

Find the leads. traxy finds high intent leads from LinkedIn activity: people who post, comment on or like posts about the problem you solve, people who engage with the competitors, creators, single posts and company pages you add to Tracking, profile viewers once you switch on Profile views under Targeting > Signals, and plain-English social intent search over 71M+ scanned LinkedIn likes, posts and comments. A person counts as a lead only with a 50%+ match to your ICP, and each lead shows the post or comment behind it with a Warm, Related or Activity label.
Split them into views. Filter Leads for each rep's territory or segment and save the filter as a shared view. A view built from filters updates as matching leads arrive and change.
Route each view. A route connects one audience to one destination: a Slack channel, a webhook endpoint, or a HeyReach campaign or list. Webhook, Zapier, n8n and Clay connections are how leads reach your CRM or your own workflows. Choose Auto or Manual delivery, and for Auto, set the route's ICP match threshold.
Hand off with context. Assign each lead to its rep, add a shared note or tag, and let the rep open the lead to read the post or comment and its date before writing.

That is the first half. traxy runs your entire LinkedIn GTM end to end, from finding high intent leads from social intent to enriching and researching each one, to running relevant, personalized LinkedIn and email outreach to them on autopilot. The same territory view can feed a campaign that sends from the rep's own connected LinkedIn account and mailbox: you test it on sample leads with nothing sent, approve the launch and it runs on its own, or you approve every message in a review queue. Replies, unsubscribes and hard bounces stop the sequence.

Routing rules that work: territory, segment, account owner

A good routing rule is one any teammate can apply to a new lead without asking a manager. Most B2B teams use one of three, and some combine two.

Rule	What the view filters on	Fits when	Watch for
Territory	People and company fields that mark the region, or one tag per territory	Reps own regions, countries or time zones	Leads that fit no territory; give them a catch-all route
Segment	People and company fields	One rep sells to founders at small companies and another to sales leaders at larger ones	Segments that overlap, so one lead fits two views
Account owner	One tag per AE on the leads from their accounts, and a filter on that tag	AEs hold named account lists	Accounts that change owner; move the tag when the CRM changes
Signal	Signal fields	One rep works competitor engagers, another works people who engaged with your own team's posts	Reps who need territory and signal at once; combine the filters in one view

Three habits keep the rule clean:

Keep the views from overlapping. Each route sends its own view. If a lead fits two reps' views and both views have automatic routes, both reps may receive it. Check that the filters split the leads, for example by tag or company field, before you switch routes to Auto.
Add a catch-all. A route can use All leads instead of a saved view. Point one at a shared team channel so leads that fit no rep's view still reach someone, and have a manager assign them.
Set the lead criteria once for the whole team. Lead criteria cover roles, departments, seniority and locations for people, and size, industry, revenue, funding and keywords for companies. Routing splits the qualified leads; it does not decide who qualifies. Keep one ICP and split it by view, rather than a different ICP per rep.

For named accounts, you can also add each key account's company page to Tracking by domain. traxy then reads the company page's LinkedIn posts for engagers who fit your ICP. That finds people who engage with the company's posts, not every employee at the company.

Round robin is the one rule this setup does not cover by itself. traxy's docs describe assigning leads by hand or in bulk, not rotating them between reps automatically. If you want leads spread evenly across a team, route them to your CRM and let the CRM's own assignment rules set the owner. The guide to routing LinkedIn engagement signals into HubSpot walks through that version.

One saved view per rep or territory

The saved view is the unit that routing works on. Campaigns and integration routes both use shared views, so the view you build for a rep is the same one that later feeds their outreach.

How to save a territory view

Open Leads and start from a built-in view, such as active leads.
Add the filters for the rep's patch: people, company and signal fields, or the tag you use for the rep's accounts, alone or combined.
Review the leads that match. If the list looks wrong, fix the filters before you save.
Choose Save as new view, name it after the territory and the rep, for example "DACH, Lena" or "Mid-market SaaS, Omar", and set it to shared.

A Filtered badge means you changed the filters but haven't saved them. Save before you build a route on the view.

What to know about saved views

Filter views keep updating. A view saved from table filters updates as matching leads and their data change, so a new lead in the territory joins the view, and an automatic route can send it.
Searches saved by trax can be fixed lists. When you ask trax to save a search that depends on text, topics or a custom ICP score range, it saves the leads matched at that time. New people don't join that fixed audience. For routing, build the view from table filters so it keeps filling.
Shared views are team property. Members can update a shared view's name and filters, and only its creator can make it personal again. If you pick a personal view for a route, saving the route shares it.
Routes protect their views. A view that a route or campaign depends on can't be deleted or made personal until you remove that dependency. Deleting a view never deletes its leads.
Post scope sticks. A view saved while one post's leads are selected keeps that post scope. Check the post banner before saving a territory view.

Each rep also needs a view of their own queue. traxy's docs give the example of a saved view of active leads assigned to you that still need review. That is the list a rep opens each morning, and the guide to a daily lead list for SDRs shows how to pair it with trax's daily brief in Slack.

Routes to a rep's Slack channel or the CRM

A route connects one audience to one destination. Use separate routes when different views should go to different channels or endpoints, so a team of five reps has five routes, plus a catch-all if you add one. The same view can have more than one route, for example one to the rep's Slack channel and one to your CRM.

Add a route

Connect the integration and open its Routes tab.
Choose Add route.
Pick All leads or the rep's saved view.
Pick the destination: a Slack channel, a webhook endpoint, or a HeyReach campaign or list.
Choose Auto or Manual. For Auto, review the ICP match threshold.
Review the destination and save.

Routing to a rep's Slack channel

Connect Slack under Integrations > Slack, authorize it, set the default channel and use Test trigger. The default channel gets the notifications and tests set for it, and each route can use its own channel, so every rep can have one. Invite the traxy app to a private channel if it doesn't show in the picker; you can also create a channel from the picker when that option appears.

Each new lead that enters the rep's view posts to the rep's channel, and the rep opens the lead in traxy to see its ICP match, its Warm, Related or Activity label and the post or comment behind it. Slack can also carry more than new leads:

Lead replies. Turn on Post lead replies for LinkedIn, email or both, to the default channel or another one. With Reply from Slack on, the notification has a reply box with Send on LinkedIn or Send email, and View conversation opens it in traxy.
Repeat engagement. New activity from a lead who already qualified. It is not a new lead; it tells the team that someone they already have is active again.
Daily summary and brief. A daily summary to the channels you choose, and trax's daily brief in Slack at the time you pick.

For an agency sending a client's leads to the client's own reps, the guide to client Slack lead alerts covers the same steps inside the client's workspace.

Routing to the CRM

traxy is not a CRM. To get a rep's leads into yours, connect Webhook, Zapier or n8n, enter the HTTPS endpoint, send a test payload and check it at the receiver, then add a route from the rep's view. Your Zap or workflow creates or updates the contact.

Two ways to set the owner. Give each rep's view its own route and have that flow set the owner to that rep, or route one wider view and let the CRM's own assignment rules decide. The first keeps the rule in traxy; the second keeps it in the CRM.
Map from the sample. Events carry event metadata and the available lead, company, contact and engagement fields. Use the payload samples under Payload & help for the exact field names, and only map what the sample shows.
Two kinds of event. First delivery and repeat engagement are separate events. Map the first to a new or updated contact and the second to an activity on the record you already have.
Plan for repeats. Delivery can retry temporary failures, so make your flow safe when the same event arrives twice, for example by matching on email, then LinkedIn URL, before creating a contact.
Verify the sender. Requests include X-Traxy-Signature and X-Traxy-Timestamp. Follow Payload & help to verify them with the signing secret.

From an AI chat connected through the traxy MCP, you can also create a Webhook, Clay, n8n or Zapier destination and queue a selected lead for delivery.

Set a threshold per route

The route threshold controls delivery to that one destination. It does not change who qualifies as a lead. That lets you send a rep's Slack channel only the strongest matches while a CRM route on the same view takes a wider band.

Check that leads arrive

A queued result means traxy accepted the request for delivery. Open the result to tell queued, delivered and failed apart. A route can pause itself after repeated failures; fix the connection or the receiving system, then resume it from the route menu. Deleting a route stops future routing, and leads already sent stay in the receiving system. Disconnecting an integration can stop all of its routes, and a successful test confirms the test request, not every later delivery.

Assignments and notes so the context travels

A route gets the lead in front of the right rep. Assignment records who owns it, and notes record what the team knows, so the reason the lead qualified doesn't stay in one person's Slack channel.

Assign. Open a lead and choose Assign to pick an active member, or Assign to me. You can assign a selection of leads in bulk, so a manager can select a territory view and assign it to its rep in one step. Assignment shows who is working the lead and does not change its qualification or recorded source.
Tag. Lead tags group leads by your own process, such as "EMEA", "named account" or "event follow-up". Filter by a tag and save the filter as a view to make a routing rule out of it. Lead tags are separate from the tags on tracked profiles.
Note. Notes on a lead are shared with workspace members. Only the author can edit or delete a note, and deleting one is permanent.

None of these use lead capacity or change qualification scores. Ownership by territory or account is also the first habit in how to stop two reps contacting the same lead, which covers the rest of the rules that keep a team off the same person.

What the reason looks like

The reason a lead qualified is already on the lead: its ICP match, its Warm, Related or Activity label, and the post or comment behind it with the date. A rep opens the lead to read its overview, signals, details and activity before writing. A short note on top tells the next person what has happened since. An example with made-up values:

Why this lead: commented on a tracked competitor's post about switching outbound tools. ICP match 78%, Warm. VP Sales at a 90-person B2B software company in Munich, DACH territory. Assigned to Lena. Lena connected on LinkedIn on Nov 13, no reply yet.

For the CRM side, put the same reason in a note or property built from the payload fields, so the owner sees it on the contact record. If a value isn't in the payload sample, have the rep open the lead in traxy instead.

Sending leads that were already in the view

Automatic routes do not backfill. They apply to leads that enter the audience after the route is saved, and saving or editing a route does not send every lead already in the view. So when you split an existing workspace into territories, each rep's backlog has to go out by hand once.

Open Leads and pick the rep's saved view.
Use the selection control in the table header to choose all matching leads, the current page, or the first number of leads in the current order. Check the filters and sort first if you pick the first results.
Open Send to and choose the named route.
Check the channel, endpoint, campaign or list before you confirm.
Open the results to confirm which leads were delivered and which failed.

A sensible order for a new rollout: build the views, add the routes on Auto, then send each backlog with Send to. From then on, the routes cover new leads. If you would rather review every lead before it reaches a rep, keep the route on Manual and send each batch yourself.

From the rep's leads to LinkedIn and email outreach

Routing tells a rep who to contact. The second half of traxy is the outreach to those leads, from the same views. A campaign's audience is a shared view, so a territory view can feed a campaign that sends from that rep's own connected sender accounts (create a campaign).

Create the campaign in Outbound > Campaigns, or ask trax. Pick the rep's view as the audience and the rep's LinkedIn account and mailbox under Senders and delivery.
Choose the research. Research on each lead is optional. When you use it, the campaign researches each lead for the facts you name, groups leads by signal and prepares a personalized message variant for each group.
Test on sample leads. A test prepares research and previews with nothing sent.
Review the launch. You see who joins, who is skipped because another unfinished campaign holds them or a completed campaign contacted them before, the sender, the steps and the delivery mode.
Pick the delivery mode. Approve every message in the review queue, or let the approved campaign send on its own.

That is how the outreach runs on autopilot: the campaign is approved once and then runs by itself, or you approve each message. Replies, unsubscribes and hard bounces stop the sequence, LinkedIn and email replies land in one inbox, a lead can be in only one active sequence at a time, and campaigns run in priority order so two unfinished campaigns don't work the same lead. With several reps, run a campaign per rep or per signal; how to run several LinkedIn outreach campaigns at once covers the order. You can also run campaigns from Claude, ChatGPT, Codex, Cursor or Grok through the traxy MCP, which asks for your yes before anything sends. More on the sending side: LinkedIn outbound with traxy.

Limits to know before you set it up

No automatic round robin in traxy. Assignment is by hand or in bulk. For rotation, let your CRM set the owner after the route delivers the lead.
One route, one destination. More reps or channels means more routes.
Automatic routes start from the day you save them. Send existing leads with Send to.
Fixed audiences don't grow. A search saved by trax on text, topics or a custom ICP score range keeps the leads it matched at that time.
Overlapping views can send one lead to two reps. Check your filters before switching routes to Auto.
A route threshold is not a qualification rule. It only decides what reaches that destination.
traxy is not your CRM. The CRM stays the system of record; traxy finds and qualifies the leads, routes them and can run the outreach.

FAQ

Can traxy assign LinkedIn leads to reps automatically?

traxy routes leads automatically: each rep's saved view sends new matching leads to that rep's Slack channel or CRM flow with an Auto route. The assignment field itself is set by hand or in bulk. If you need the owner set automatically, let your CRM's assignment rules do it after the lead arrives.

Can each rep get their own Slack channel?

Yes. Each route sends one view to one destination, and routes can use their own channels, so give each rep a view and a route to their channel. Invite the traxy app to private channels first.

Do automatic routes send leads that were already in the view?

No. Automatic routes cover leads that enter the view after you save the route. Send the existing ones from Leads > Send to.

Does the route's ICP match threshold change who becomes a lead?

No. A person becomes a lead at a 50%+ ICP match. The route threshold only controls what that route delivers, so you can set it higher for a rep's channel than for your CRM.

Can the same lead go to Slack and the CRM?

Yes. Add two routes on the same view, one to the rep's Slack channel and one to a Webhook, Zapier or n8n flow for the CRM.

How does the rep see why a lead qualified?

Each new lead in the rep's view posts to the rep's Slack channel, and the rep opens the lead in traxy to see its ICP match, its Warm, Related or Activity label and the post or comment behind it, with its date. Shared notes add what the team has done since.

What happens if a destination stops working?

A route can pause after repeated failures. Fix the connection or the receiving system, then resume the route. Inspect results to tell queued, delivered and failed leads apart.

Can the rep's outreach run from traxy too?

Yes. The rep's view can be the audience of a LinkedIn and email campaign that sends from the rep's own connected accounts, after a test on sample leads and your approval of the launch, or you approve every message.

Can an agency route a client's leads to the client's reps?

Yes. An agency can run traxy for its clients. Keep each client in its own workspace, save the client's views there and route them to the client's channels. See the client Slack alerts guide.

Back to all articles