GoHighLevel lead routing assigns each new lead to a team member automatically with the Assign to User workflow action: select several users and it rotates between them equally by default, or unevenly with weights such as 3:3:1, with a toggle that limits assignment to contacts that have no owner yet and a Dynamic option that takes a user ID from a field or webhook. Routing by source, territory or service is the same action placed behind an If/Else branch; routing for bookings is the round robin calendar; and re-assignment when nobody responds is a Wait step with a timeout followed by Remove Assigned User and a second Assign to User. A routing design has to answer four questions before anything is clicked: who gets which lead, what happens when nobody answers, how the contact owner and the opportunity owner stay in sync, and how you will see response time. Every HighLevel fact here was checked at help.gohighlevel.com on November 2, 2026; titles and dates are in the Sources section.
How does GoHighLevel lead routing work?
GoHighLevel routes leads inside workflows: a trigger such as Contact Created or Form Submitted fires, optional If/Else branches sort the lead by source, territory or service, and an Assign to User action sets the contact owner, rotating between the chosen users.
| Routing method | How it is built | Best for | Rules worth knowing |
|---|---|---|---|
| Round robin, equal | Assign to User with several users selected; Split Traffic left on Equally (the default) | A sales or intake team where any rep can take any lead | Rotates in order; turn on Only Apply To Unassigned Contacts so returning customers keep their rep |
| Weighted round robin | Assign to User, Split Traffic set to Unevenly, a weight per user | Senior reps who should get more, new reps who should get fewer | Weights of 3, 3 and 1 send three leads to the first user, three to the second, one to the third, then repeat |
| By source | If/Else on the lead source or attribution field, then a different Assign to User per branch | Ads leads to closers, referrals to the owner, partner leads to the partner manager | Set the source on the form or ad trigger so the field exists before the branch runs |
| By territory | If/Else on a custom field (zip, state, city, service area) collected on the form, then Assign to User per branch | Multi-location businesses, franchises, field service | Use a dropdown or validated field; a free-text city field breaks the branch |
| By service or deal size | If/Else on a service dropdown or on opportunity value | Specialists per service, big deals to senior reps | The field has to be on the contact or the opportunity in context |
| Dynamic (from another system) | Assign to User switched from Standard to Dynamic, with a user ID merge tag in the text field | Routing decided by a scoring tool, a form logic step or a webhook | User IDs are under Settings, My Staff, below each user's email |
| Calendar team (bookings) | A Round Robin calendar with the team as members; Optimize for Availability or Equal Distribution, priority per member | Booking-led businesses where the appointment is the lead | Turn on Always Book with Assigned User so a known contact lands with their rep; you can also assign the contact to the member they booked with |
| Manual | Assigned-to dropdown on the contact or opportunity, or bulk assign from a list | Tiny teams, exceptions, imports | Keep it for exceptions; manual ownership is how leads get lost |
One limit to design around: the Assign to User action sets the contact owner. The opportunity owner is a separate field, set by the Add Owner to Opportunity action or by syncing contact and opportunity owners in Opportunity Settings. If the two are not synced, a rep can own the contact while the deal on the pipeline shows nobody.
- User A (weight 3)3 of 7
- User B (weight 3)3 of 7
- User C (weight 1)1 of 7
Source: the Unevenly option in HighLevel's Assign To User action; the example weights are HighLevel's
How to set up round robin lead assignment in GoHighLevel
Create a workflow with a Contact Created or Form Submitted trigger, add Assign to User with the team selected and Split Traffic on Equally, turn on Only Apply To Unassigned Contacts, add an Internal Notification to the Assigned User after the assignment, then publish.
- Create the workflow. Automation, Workflows, Create Workflow, Start from Scratch. Name it "Routing: new leads".
- Add the trigger. Contact Created is the simplest and catches every source. For a narrower rule use Form Submitted, Facebook Lead Form Submitted or an inbound call trigger, one workflow per entry point if the first message differs.
- Optional: branch. Add If/Else with a condition on the source or territory field (Contact Details in the condition picker). One branch per team.
- Assign to User. In each branch add Assign to User. Select the Users for that team. Leave Split Traffic on Equally, or switch to Unevenly and set a weight per user.
- Protect existing owners. Turn on Only Apply To Unassigned Contacts. With it off, every run reassigns contacts that already have an owner and overwrites the previous assignment.
- Notify the right person. Add Internal Notification after the assignment, choose the channel (email, in-app, SMS or WhatsApp) and set the recipient to Assigned User. HighLevel's own recipe stresses that the notification must come after Assign to User or it goes to the wrong person. If the contact has no assigned user, or no phone number for SMS, the step is skipped and the workflow continues.
- Create or update the opportunity. Add Create/Update Opportunity in the right pipeline and stage, then Add Owner to Opportunity if owners are not synced. Its own Only Apply to Unassigned Opportunities toggle works the same way as the contact one.
- Send the first message. The speed matters more than the routing; the sequence is in GoHighLevel speed to lead.
- Add the no-response fallback described in the next section.
- Publish and test. Turn on Publish, save, submit three test leads and confirm they land with three different users and that each one got the notification.
What happens when the assigned rep does not respond?
Build an SLA branch: after the first message, a Wait step waits for a user reply with a timeout (HighLevel's example is five minutes), and the timeout branch notifies a manager, creates a task, or removes the assigned user and runs Assign to User again so the next rep gets the lead.
HighLevel's User Replied trigger article describes the pattern: start with a Customer Replied trigger, add a Wait set to the User Replied condition with a timeout, and attach escalation actions to the timeout branch. For new leads the same pattern starts from the routing workflow instead:
- Wait for a user reply. After the first text or email, add Wait, choose the reply or condition option, and set a timeout of 5 to 15 minutes in business hours. The Wait action can hold until a contact reply, a user reply, a contact action or a custom condition, and can release the contact on timeout.
- Escalate once. On the timeout branch, Internal Notification to the Assigned User a second time plus the manager, and a task on the contact.
- Re-assign if still silent. A second Wait of 15 to 30 minutes, then Remove Assigned User (it clears the owner but keeps the assignment history), then Assign to User with the rest of the team, Only Apply To Unassigned Contacts on so the fresh assignment lands, then the notification again.
- Stop the chase when someone answers. Add a Goal Event on User Replied so the contact exits the remaining escalation steps the moment a rep responds.
- Record it. Add a tag such as "routing-reassigned" so you can count how often the first rep missed the window.
For leads that come in as calls rather than forms, the fallback is missed call text back followed by the same assignment rule.
Which notification options does the assigned rep get?
Internal Notification can reach a user by email, in-app alert under the bell icon, SMS or WhatsApp, addressed to All Users, Particular Users, the Assigned User, a role or a team, with a default cap of 500 notifications per user every 5 minutes.
| Channel | Who can receive | When to use it | Rule from HighLevel |
|---|---|---|---|
| In-app | Assigned User, roles, teams, particular users | Reps who live in the HighLevel app or mobile app | Shown under the bell icon; counts toward the 500 per 5 minutes cap |
| SMS | Assigned User, all users, particular users | Field teams and after-hours reps | User needs a valid phone number or the step is skipped; billed as outbound SMS, see usage costs |
| Assigned User, all users, particular users | Desk teams, managers, records | Needs a subject line | |
| Assigned User, roles, teams | Teams already on WhatsApp Business | Needs a connected WhatsApp Business Account and approved templates | |
| Calendar notifications | Assigned User by default on non-event calendars | Bookings rather than leads | Set per calendar on its Notifications tab; see calendar setup |
Notifications above the cap are queued or may be dropped, so a workflow that fires per lead is fine but a bulk import of 2,000 contacts through the routing workflow is not; pause the routing workflow during imports or exclude imported contacts with a tag filter.
How do you report on lead response time?
Set up Conversation SLAs, then read the SLA Performance dashboard under Conversations, Analytics, SLA Performance, which shows SLA Met percent, SLA Breached percent and Average Response Time by user and by channel; the SLA widgets add an average first response time trend to dashboards.
- SLA Performance dashboard. Requires Conversation SLAs to be configured for the sub-account first. Average Response Time counts only messages that received a reply, and messages still inside an active SLA window are excluded, so read it after close of business, not at 10 AM.
- SLA widgets. Dashboards and custom reports can show average first response time by day, week or month, which is the number to put in front of the sales manager.
- Call Reporting. Answered, missed and call duration by user for teams whose leads call.
- Routing tags. The "routing-reassigned" tag from the fallback gives a count of leads the first rep missed, which is a cleaner conversation than an average.
Routing rules by team size
One rep needs no routing but still needs the no-response fallback; two to three reps need equal round robin with an owner check; four to ten reps need branches by source or service; more than ten, or several locations, need territory branches, team-level notifications and one routing workflow per location.
| Team | Routing rule | Fallback | Owner sync | Notification |
|---|---|---|---|---|
| 1 rep or owner-operator | Assign to User, one user, or none and rely on the inbox | Wait 15 minutes, then SMS the owner again; AI first reply if nobody can answer in business hours | Sync contact and opportunity owner | SMS plus in-app |
| 2 to 3 reps | Equal round robin, Only Apply To Unassigned Contacts on, Always Book with Assigned User on the calendar | 5-minute user-reply wait, escalate to the other rep, then the owner | Sync | In-app plus SMS to Assigned User |
| 4 to 10 reps | If/Else by source or service, weighted round robin inside each branch for seniority | 5-minute wait, re-assign within the branch pool, manager alert on the second miss | Sync, with Add Owner to Opportunity when deals are created later by another workflow | In-app to Assigned User, email digest to the manager |
| More than 10, or several locations | Territory branch on a validated location field, then a routing workflow per location so each manager can edit their own pool | Per-location manager escalation, then a central desk | Sync, plus a location field on the opportunity for reporting | Team recipient for the location, role recipient for managers |
Multi-location structure, including how the location field and the pipelines line up, is in GoHighLevel for franchises; a worked example of routing by job type and zip code is in GoHighLevel for contractors; the fields the branches depend on are covered in custom fields and tags.
Common GoHighLevel lead routing mistakes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| Wrong person gets the notification | Internal Notification placed before Assign to User, or recipient set to a named user | Move the notification after the assignment and set the recipient to Assigned User |
| Returning customers get a new rep | Only Apply To Unassigned Contacts is off | Turn it on; use a separate workflow for deliberate reassignment |
| One rep gets everything | Only one user selected, or weights set unevenly by accident | Check Select the Users and Split Traffic on the action |
| Nobody owns the deal on the pipeline | Assign to User sets the contact owner only, and owners are not synced | Sync owners in Opportunity Settings or add Add Owner to Opportunity |
| Routing never runs | Workflow unpublished, trigger filters too narrow, or the contact entered through a path with no trigger | Publish, widen the trigger, check execution logs; see workflows not triggering |
| Territory branch sends everyone to the fallback | Free-text city field with typos, or the field is filled after the branch runs | Use a dropdown, and place the branch after the field is set |
| Imports flood the team | Contact Created trigger fires for every imported row | Pause the routing workflow during imports, or filter imported contacts by tag |
| Dynamic assignment does nothing | The merge tag holds a name, not a user ID | Pass the ID from Settings, My Staff; check for an empty value with an If/Else first |
| Booked lead lands with a stranger | Always Book with Assigned User is off on the round robin calendar | Turn it on and keep the rep on the calendar's Team Members tab |
| Rep says they never saw the lead | Notifications above the 500 per 5 minutes cap were queued or dropped, or SMS skipped for a missing phone number | Add the phone number to the user profile; spread bulk operations |
If you want this built
Lead routing, the no-response fallback and the response-time dashboard are part of our GoHighLevel CRM implementation, and we repair existing routing on a support plan. Book the free 30-minute call with a free account audit at contact our GoHighLevel team; every price is a written custom quote, with single-location builds at $500 to $4,000 at the time of writing.
Sources
- HighLevel help: "Workflow Action - Assign To User" (modified July 24, 2025; read November 2, 2026)
- HighLevel help: "How to Automatically Assign Users to Leads In Workflows" (modified February 23, 2024; read November 2, 2026)
- HighLevel help: "Workflow Action - Internal Notification" (modified March 31, 2026; read November 2, 2026)
- HighLevel help: "Workflow Action - Add Owner to Opportunity" (modified May 14, 2025; read November 2, 2026)
- HighLevel help: "Workflow Action - Remove Assigned User" (modified December 18, 2024; read November 2, 2026)
- HighLevel help: "Workflow Trigger - User Replied" (modified July 10, 2026; read November 2, 2026) and "Workflow Wait Action Setup and Options in HighLevel" (read November 2, 2026)
- HighLevel help: "Using If/Else Workflow Action to Automate Decision-Making" (read November 2, 2026)
- HighLevel help: "Managing Team Member Assignments in Round Robin Calendars" (modified May 26, 2025) and "Appointment Distribution Logic for Round Robin Calendars" (modified April 14, 2026) (read November 2, 2026)
- HighLevel help: "SLA Performance Dashboard in HighLevel Conversations", "SLA Widgets for Dashboards and Reporting" and "Call Reporting" (read November 2, 2026)
Frequently asked questions about GoHighLevel lead routing
How do I round robin leads in GoHighLevel?
Add the Assign to User action to a workflow that starts from Contact Created or Form Submitted, select the users, and leave Split Traffic on Equally. The action rotates new contacts between the selected users in turn. Put an Internal Notification to the Assigned User after it and publish the workflow.
How do I assign leads to a user automatically in GoHighLevel?
Use the Assign to User workflow action. One selected user receives every lead that reaches the step; several users are rotated. Turn on Only Apply To Unassigned Contacts so existing owners are kept, and add Add Owner to Opportunity if contact and opportunity owners are not synced.
Can I give some reps more leads than others?
Yes. Set Split Traffic to Unevenly and give each user a weight. With weights of 3, 3 and 1 the first user receives three leads, the second three, the third one, and the cycle repeats. Source: HighLevel's Assign To User article, modified July 24, 2025.
How do I route leads by location or source?
Collect the location or source in a field on the form or ad trigger, add an If/Else condition on that field, and place a separate Assign to User in each branch with that territory's or channel's team. Use a dropdown for the field so typos cannot send leads to the wrong branch.
How do I avoid reassigning leads that already have an owner?
Turn on the Only Apply To Unassigned Contacts toggle on the Assign to User action. With it enabled only contacts with no owner are assigned; with it disabled the action reassigns contacts that already have an owner and overwrites the previous assignment.
What happens if the assigned rep does not respond?
Nothing, unless you build it. Add a Wait step that waits for a user reply with a timeout, then on the timeout branch notify the manager, and if still silent run Remove Assigned User followed by Assign to User with the rest of the team. A Goal Event on User Replied ends the chase when a rep answers.
Why did the wrong person get the notification?
The Internal Notification step ran before the Assign to User step, or its recipient was a named user rather than Assigned User. HighLevel's lead-assignment recipe places the notification after the assignment for this reason. If the contact has no assigned user the notification is skipped and the workflow continues.
Does a round robin calendar assign by skill or priority?
By priority, yes: each member can be High, Medium or Low, and higher-priority members are preferred when several are free, per HighLevel's Appointment Distribution Logic article. By skill, no. Route by skill with a calendar per skill or with Assign to User behind an If/Else before the booking link is sent.
Can I route by a rule in another system?
Yes. Switch Assign to User from Standard to Dynamic and enter a user ID or a merge tag that holds one, for example from a webhook or a scoring step earlier in the workflow. User IDs are under Settings, My Staff, below each user's email address. Check for an empty value first.
How do I see lead response time in GoHighLevel?
Configure Conversation SLAs, then open Conversations, Analytics, SLA Performance for SLA Met percent, SLA Breached percent and Average Response Time by user and channel. Dashboard SLA widgets show average first response time over time, and Call Reporting covers phone leads.
Can you design lead routing for my team?
Yes. Routing, the fallback and the response-time dashboard are part of our CRM implementation, and the 30-minute call and account audit are free.