Anu Agency
PlaybookWork with Anu
07.04 Route each lead to one agent and alert them in minutes

07.04

Route each lead to one agent and alert them in minutes

Set a routing rule per lead source, assign automatically, and send the assigned agent an alert they will actually see.

40 minNeeds verificationChecked 2026-10-20

Video walkthrough

Coming soonWho gets the lead, and how fast do they know?
It will cover
  1. Write the routing rule in one sentence per source before touching software
  2. HighLevel: Assign to User with round robin, then Internal Notification
  3. Follow Up Boss: Lead Flow per source, round robin and first-to-claim groups
  4. The fallback: what happens when nobody responds
  5. Run three test leads and check the rotation
This chapter is complete without it. Every step is written out on this page.

What you're building

A written routing rule for each lead source ("Website sellers go to Dana; Meta buyer leads rotate between Sam and Priya"), set up in your CRM so assignment happens with no human step, followed by an alert to the assigned agent and a fallback if nobody acts.

Why it matters

A lead that belongs to everyone belongs to no one. Automatic assignment plus a direct alert removes the two slowest steps in most teams: someone noticing the lead, and someone deciding who takes it.

What you need

  • The list of sources from your system map
  • The agents who take new leads, each with their own CRM user
  • Each agent's preferred alert channel (text, mobile app push, email)
  • HighLevel: the Form Submitted workflow from the forms chapter. Follow Up Boss: owner or admin access to Admin > Lead Flow and Admin > Groups.

Time and cost

Time
40 minutes
Cost
$0 within your CRM plan

Internal SMS alerts in HighLevel are sent through your account's texting and billed per message.

Step by step

  1. Write the rule for every source in one sentence

    Use the template below. Decide three things per source: who receives it (one agent, a rotation, or first to claim), how fast they must act, and who gets it if they do not.

    Check: Every source on your system map has one routing sentence, including a fallback person.

  2. HighLevel: add Assign to User to the lead workflow

    Select one user to send every lead to that person, or several users for a round robin. With Split traffic: Equally, HighLevel rotates evenly; Unevenly lets you give each user a weight (how many leads they get before the rotation moves on).

    Turn on Only apply to unassigned contacts so a returning lead stays with the agent who already knows them. With it off, a re-triggered contact is reassigned and the previous owner is overwritten.

    Check: Three test submissions with three different test emails land on the users in rotation order.

  3. HighLevel: alert the assigned agent

    Place Internal Notification after Assign to User, so it knows who the assignee is. Choose the channel (email, in-app, SMS or WhatsApp) and set the recipient to the assigned user. Include the lead's name, source and message in the alert using merge fields.

    Internal Notification only reaches your users, never the contact. HighLevel limits each user to 500 notifications every 5 minutes; anything over is skipped.

    Check: The assigned agent receives the alert within 5 minutes of the test submission, showing the test lead's name and source.

  4. Follow Up Boss: create the group, then set Lead Flow per source

    Create a group, add its agents, and choose Round Robin (next person in line gets the lead; a green check marks who is next) or First to Claim (everyone is offered the lead; the first to claim gets it, and an unclaimed lead goes to a fallback agent or group after a wait of up to 30 minutes).

    Then open Admin > Lead Flow, find each source (it appears automatically after its first lead, or add it manually), and set its agent or group and, optionally, an action plan.

    Check: Admin > Lead Flow shows every source from your system map with an agent or group set, and none left unassigned.

  5. Set the fallback for leads nobody touches

    HighLevel: after Internal Notification, add a Wait of your chosen length, then an If/Else that checks whether the contact has an outbound message or call; if not, notify the team lead and reassign. Follow Up Boss: use First to Claim's fallback, or an automation that reassigns a lead with no contact attempt after your chosen time.

    The wait time is your standard, not an industry number. Write it in your routing sentence and measure it in Part 08.

    Check: A test lead nobody touches is reassigned or escalated at the time you set.

What success looks like

  • Every source has a routing rule written and configured.
  • Test leads are assigned with no manual step and in the expected rotation.
  • The assigned agent is alerted within 5 minutes on the channel they chose.
  • An untouched lead escalates to the fallback person on time.

Copyable templates

csvRouting rule sheet

Fictional names. The minutes are examples of a standard you set, not benchmarks.

Source,Who receives it,Method,Act within (minutes),Fallback if not acted on,Alert channel
Website - Home value form,Dana Reyes,Single agent,15,Team lead,Text + app
Meta - Buyer lead form,Sam Ortiz; Priya Shah,Round robin (equal),15,Dana Reyes,App
Portal - Buyer inquiry,Buyer team group,First to claim,10,Dana Reyes,App
Open house sign-in,Hosting agent,Single agent,1440,Team lead,Email
textInternal alert text

Use your CRM's merge-field picker; field names differ by account.

NEW LEAD for you: {{contact.name}} | Source: {{contact.source}} | Phone: {{contact.phone}} | Said: "{{message}}" | Text consent: {{contact.sms_consent}}. Open the CRM and reach out now.

Try it

New leadsource known
Routing ruleby source
Assigned agentalert sent
Wait your standarde.g. 15 minutes
Speed to leadPart 08 scorecard
Fallbackteam lead or next agent
  • New leadtoRouting rule
  • Routing ruletoAssigned agentassign + alert
  • Assigned agenttoWait your standard
  • Wait your standardtoFallbackno contact attempt
  • Assigned agenttoSpeed to lead
Routing with a fallback

How to test it

  1. Submit three test leads with three email aliases (+test0002, +test0003, +test0004).
  2. Write down who each was assigned to and when each agent got the alert.
  3. Leave the last one untouched and confirm it escalates at your fallback time.
  4. Submit +test0002 again and confirm it stays with the same agent.

Troubleshooting

HighLevel: every lead goes to the same person.

Only one user is selected in Assign to User, or the split is Unevenly with one large weight. Select all rotation users and set Split traffic to Equally.

HighLevel: the alert goes to the wrong person or nobody.

Internal Notification sits before Assign to User, or the recipient is a fixed user. Move it after the assignment and choose the assigned user.

Follow Up Boss: leads from one portal ignore your rotation.

That provider assigns leads directly to an agent, which bypasses Lead Flow. Change the routing inside the provider, or have it send to one address that Lead Flow controls.

Agents mute alerts because there are too many.

Alert only on new leads and replies, not every activity. Move everything else to a daily summary.

Advanced technical details

Optional. You can follow every step above without these.

Technical detailsRouting mechanics worth knowing
  • HighLevel's Assign to User rotates per assignment across the selected users. With several workflows assigning the same contact, the last one to run wins; keep assignment in one workflow per source.
  • Follow Up Boss: leads cannot be assigned to Round Robin or First to Claim groups through Mass Actions. Reassigning a single lead to a round-robin group gives it to the next person in line. Automations can reassign to an agent, a group, a pond or a lender.
  • For audits, read assignment changes from HighLevel workflow Execution Logs, or from Follow Up Boss peopleUpdated webhooks followed by a GET on the person.

Sources

Written from the best available information. One or more steps could not be confirmed; see the notes in the chapter. Last checked 2026-10-20.