GoHighLevel lead routing assigns each new lead to a team member automatically, using 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 webhook. Round-robin calendars handle the same problem for bookings, distributing appointments by availability or equally. A good routing design answers four questions before any button is clicked: who gets which lead, what happens when nobody answers, how an owner is kept in sync between contact and opportunity, and how you will know it worked. HighLevel's articles were read October 18, 2026; some are old.
How does GoHighLevel lead routing work?
GoHighLevel routes leads with the Assign to User action, rotating equally between users by default, weighted unevenly when you set a ratio, or dynamically from a field or webhook.
| Method | How it routes | Best for |
|---|---|---|
| Assign to User action, several users | Rotates between selected users in turn; "Equally" is the default | Simple round robin for a sales or intake team |
| Assign to User, Unevenly | You set a weight per user, for example 3:3:1 | Senior reps who should get more leads, new reps fewer |
| Assign to User, Dynamic | Takes a user ID from a field or webhook instead of the dropdown; IDs are under Settings, My Staff | Routing by rules in another system |
| Round Robin calendar | Distributes appointments among assigned team members by availability or equal distribution | Booking-led businesses (consultations) |
| Add Owner to Opportunity | Sets the opportunity owner and can overwrite the contact owner if sync is on | Keeping deal owner and contact owner aligned |
Sources: HighLevel's Assign To User action, round robin calendars and Add Owner to Opportunity articles. Round robin calendars support only availability-based or equal distribution, not priority for particular staff.
- 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
- Trigger: Contact Created, a form, or a lead-source trigger.
- Assign to User: choose the users; leave Equally on or switch to Unevenly and set weights.
- Turn on "only unassigned" so existing owners are never overwritten. Turning it off lets a new trigger reassign contacts that already have an owner.
- Internal Notification: set the recipient to the assigned user and put it after the assign step.
- Create the opportunity and set the owner to match, using Add Owner to Opportunity if needed. Check whether contact owner sync is on.
- Add a fallback: if nobody has acted in a set time, notify a manager.
The step-by-step guide uses Contact Created, then Assign to User, then Internal Notification, and says the notification must come after the assignment so it goes to the right person.
Routing rules worth deciding before you build
| Rule | Options | Our default |
|---|---|---|
| By source | Same pool for all, or a pool per source (ads vs referrals) | A pool per source, because the first message differs |
| By location or service | One workflow with branches, or one workflow per location | Branch on a custom field; see custom fields and tags |
| By availability | Ignore, or remove off-duty users from the pool | Round robin calendars handle availability for bookings; for leads, keep the pool current |
| Existing customers | Route to the account owner | Check for an existing owner first |
| Fallback | Nobody acts in time | Escalate to a manager and add a task |
For the response that follows assignment, see GoHighLevel speed to lead; for the pipeline the opportunities land in, see pipeline setup.
Frequently asked questions about GoHighLevel lead routing
How do I round robin leads in GoHighLevel?
Use the Assign to User workflow action with several users selected. It rotates between them; Equally is the default.
Can I give some reps more leads than others?
Yes, choose Unevenly and set a weight per user, for example 3:3:1.
How do I avoid reassigning leads that already have an owner?
Turn on the toggle that limits assignment to contacts with no owner. With it off, a new trigger can reassign them.
Why did the wrong person get the notification?
The Internal Notification step must come after the assignment and use the assigned-user recipient.
Does a round robin calendar assign by skill or priority?
No, HighLevel says round robin calendars support availability-based or equal distribution only.
Can I route by a rule in another system?
Yes, with the Dynamic option: pass a user ID, for example from a webhook. User IDs are under Settings, My Staff.
Can you design lead routing for my team?
Yes, see our CRM implementation service; the audit is free.