Who this is for
Hot-lead routing starts once your engagement signals are firing (graded opens, repeat opens, positive replies). This is how to get them to the right rep with enough context to act on it inside the 4-hour window.
Hot-lead detection is half the workflow. The other half is routing the alert to the right rep with the right context, fast enough to act. For solo founders or 1-2 person teams, the routing is trivial, the alert goes to one person. For 5-15 rep teams, the routing decisions matter: which rep owns the account, what context they need to respond well, whether to pass it on in a team channel or a direct message, and how to handle the rep-unavailable case.
The right routing pattern depends on team size and ownership model. Account-owned-by-one-rep is the simplest case. Multi-stakeholder accounts (BDR + AE + CSM touching the same contact) require territory-and-stage-aware routing. Coverage on rep PTO needs explicit fallback rules.
Hot-lead alerts often fire with ad-hoc routing: the alert fires, the rep sees it eventually, and by then the moment has often passed. The failure mode is that the alert is technically in the rep's queue but not in their attention. Routing fails on three patterns: wrong rep (alert went to BDR but the deal is now AE-owned), insufficient context (rep gets the alert but has to dig for the engagement history), and timing (alert sat in Slack while rep was in a meeting).
Write the rules down: prospecting-stage accounts belong to the assigned BDR, active-deal accounts to the assigned AE, customer accounts to the assigned CSM. Outsolvi doesn't read deal stages from a CRM and doesn't reassign anything; its alerts go to whoever sent the email. So the rule is really about hand-offs: when the sender isn't the owner, the sender passes the signal on.
A direct message to the owner is the lowest-friction hand-off for high-priority signals (hot leads, positive replies). A shared team channel works for team-wide accountability or for accounts where several reps need visibility. Lower-priority signals can wait in Outsolvi's tracked emails list for an end-of-day pass. Outsolvi doesn't post to Slack or Microsoft Teams, so whoever got the pop-up does the posting.
The hand-off needs the prospect's name, the engagement context ("opened your pricing follow-up twice in the past 35 minutes"), the assigned rep, and a link to the thread. Each tracked email's page in Outsolvi lists every open with its time and a plain-English reason, such as "opened in Gmail", so the context is a copy and paste away. Without it the rep has to dig before responding, and the 4-hour window erodes.
When the assigned rep is on PTO or otherwise unavailable, their accounts need a named backup or a shared coverage channel. Agree on this in advance; discovering mid-vacation that nobody was watching is too late. Outsolvi has no out-of-office rerouting, so before a rep goes on leave they hand their live threads to the backup in person.
The KPI for routing effectiveness is median latency from alert fire to rep response. Healthy teams hit median under 2 hours during business hours. Teams with median over 6 hours usually have a routing problem (alerts going to wrong rep, lack of context, or rep-unavailability not handled).
Outsolvi handles the detection half and leaves the routing to you. It has no Slack or Microsoft Teams integration, no routing rules and no PTO rerouting. Every open is graded as a person or a machine with the reason shown, and an email becomes a hot lead once it has five counted opens and two clicks. The rep who sent it gets a desktop pop-up from the Gmail extension or the desktop add-in for classic Outlook, sees a flame on the email in the tracked emails list, and finds it counted in the weekly summary email. Replies are labelled Positive, Negative, Neutral or Out of office by keyword rules, and a reply stops any follow-ups still due to that address.
The desktop pop-up from the Gmail extension or the classic Outlook add-in is the whole routing. No decisions needed.
Each rep acts on the hot leads from their own sends. Anything that belongs to someone else gets posted by hand in a shared #hot-leads channel so the team can claim it. Daily standup reviews routing latency.
Stage-aware hand-offs: a BDR passes an account that has moved to an AE by direct message. On Pro, team analytics shows each rep's sent emails, opens, clicks and open rate, which is enough for a manager's coaching and gap-spotting; the individual alerts stay with each rep.
Hard-assigned ownership by account-rep mapping, kept in your CRM or a shared sheet. No claiming in shared channels. A backup rep for each named account, agreed in advance.
Depends on accountability model. Direct messages work when ownership is clear and unambiguous (account-based, named-account). Channels work when team-wide visibility matters or when reps need to claim unowned leads. Hybrid is common: a direct message for assigned accounts, the channel for unowned ones. Either way a person posts it, because Outsolvi doesn't post to Slack or Microsoft Teams.
Agree on a backup rep for each person in advance. Outsolvi doesn't reroute alerts when someone is away; pop-ups go to the computer of the rep who sent the email. So before leaving, the rep lists their live threads for the backup. Don't rely on discovering PTO mid-alert; that's too late.
Outsolvi doesn't send to Slack or Microsoft Teams anyway. Hot-lead alerts pop up from the Gmail extension and the desktop add-in for classic Outlook, hot emails get a flame badge in the app, and the weekly summary email counts them.
No. The hot-lead rule is fixed at five counted opens and two clicks on one email, for everyone, and there are no per-rep priority or routing settings. Each rep can set quiet hours so pop-ups don't arrive overnight. Beyond that, priority is a habit: act on pop-ups as they arrive and work through the rest of the tracked emails list before you log off.
Median latency from alert fire to rep response is the cleanest KPI. Healthy teams hit median under 2 hours during business hours. Track as a 30-day rolling number; surface team-wide and per-rep in retrospectives.
Hot-lead routing is where most companies' tracking investment dies in transit. The signal exists, the tracker fires, an event lands in a webhook, but the routing to the right rep through the right channel within the right window doesn't happen, because the rest of the GTM stack wasn't wired for it. The lead-to-rep handoff that takes 47 minutes on average kills most of the conversion lift the tracker should have delivered.
The teams getting this right have one rule: the alert reaches the rep where they already work, not a separate dashboard they have to remember to open. In Outsolvi that's a desktop pop-up from the Gmail extension or the desktop add-in for classic Outlook, on the computer the rep sends from. Adding any friction to the handoff costs you the next 60 minutes of attention. Removing it makes hot-lead capture feel automatic instead of forced.
Outsolvi doesn't route alerts between people. The hot-lead flag goes to the rep who sent the email: a pop-up on their desktop if they send from Gmail with the extension or from classic Outlook with the desktop add-in, a flame on the email in the tracked emails list, and a count in their weekly summary email. Getting it to anyone else, an account owner or a teammate covering a vacation, is a team habit, not a setting. The lift is the unglamorous operational kind, no new strategy, no headcount, no message change, just the right signal reaching the right rep sooner. Nobody has published a reliable figure for what that's worth, so measure it on your own pipeline.
Free tools, articles, glossary entries, and features that pair with this pattern.
14-day free trial, no credit card. Graded opens, hot-lead alerts, reply labels, Outlook and Gmail add-ins.
Start 14-Day Free TrialNate built Outsolvi after watching every email-tracking tool he had ever used lie to him about opens. Outsolvi grades every open as a person or a machine, in Outlook and Gmail, so the number on the dashboard is one a rep can actually act on.
We update these pages when the underlying mechanics change. new mailbox-provider rules, new tracker behavior, new measurement gaps. The dates above are real revisions, not auto-touches.