Short answer
Use the Assign To User workflow action. It can assign every lead to one user, rotate leads across several users, or split traffic equally or by weight. Turn on Only Apply to Unassigned Contacts so a later trigger never overwrites an owner who already has the lead.
In this post
How do you assign leads automatically in GoHighLevel?
Build a workflow with a trigger for new leads, then add the Assign To User action. Give the action a descriptive name such as “Assign to Agents in California” so you can find it later. The action offers these modes:
| Mode | What happens |
|---|---|
| Single user | Every triggered contact goes to one person |
| Multiple users (round robin) | Contacts rotate through the selected users in order |
| Split Traffic, Equally (default) | Contacts spread evenly, aiming for equal totals over time |
| Split Traffic, Unevenly | You set a weight per user. Weights of 3, 3 and 1 send three contacts to the first, three to the second, one to the third, then repeat |
| Dynamic user IDs | Type user IDs or insert them as merge tags, useful when assignment logic lives outside HighLevel |
Round robin hands out one contact at a time. Equal split aims at equal totals across a period. For a small team the difference rarely matters. For a large team with uneven volume it does.
What does Only Apply to Unassigned Contacts do?
It protects existing owners. With it on, a contact is assigned only if nobody owns it yet. With it off, an already-assigned contact can be reassigned when the trigger fires, and the new assignment overwrites the old one.
Switch it on for any workflow that can fire on returning contacts. A repeat form submission is the usual cause of a surprise reassignment.
What should decide the owner?
Start with the fewest reliable inputs:
- Lead source, such as a form or a booking
- Service requested
- An existing owner
- Region or language, only if it genuinely changes who should respond
Each extra rule is another place for two conditions to match at once. If the service drives routing, collect it as a drop-down on the form so “CRM setup” and “CRM” cannot become different values. See contact vs opportunity custom fields.
How do you plan the routing rules?
Write a decision table before you open the builder.
| Condition | Action | Fallback |
|---|---|---|
| Contact already has an owner | Keep the owner, notify them | Review queue if the owner is inactive |
| Lead wants a specialist service | Assign to the specialist group | General intake owner |
| Ordinary new lead | Rotate across the sales team | Notify the team lead |
| Required field is empty | Send for manual review | Never guess an owner |
How do you build and order the steps?
- Pick the trigger for a new lead, for example a form submission.
- Add a condition branch for each route in your table.
- Add Assign To User on each branch, with Only Apply to Unassigned Contacts set deliberately.
- Add the internal notification after the assignment, so it reaches the person who now owns the lead.
- Add a branch for missing or odd values that notifies a human.
The Assign To User action covers the contact. HighLevel’s documentation for it does not cover opportunities, which have a separate Add Owner to Opportunity action. If your process depends on deal ownership, set both and check each record.
How do you test the routing?
Use clearly labelled test contacts with your own email and number. Test every route once, plus a missing field and a returning contact. Check the owner on the contact and on the opportunity, the notification recipient, tags and stage. Then open the execution log, see how to test a workflow before it goes live.
Frequently asked questions
Should every lead be assigned automatically?
No. Automate the ordinary cases that have reliable inputs. Send incomplete, unusual or high-value leads to a person.
Can I weight the split toward a senior closer?
Yes. Use Split Traffic, Unevenly and set the weights.
Is this the same as a round-robin calendar?
No. The workflow action assigns a contact owner. A round-robin calendar assigns an appointment, see how to set up a round-robin calendar.
If you want routing designed and tested end to end, see the services page or book a free 30-minute call.
Sources: HighLevel Help: Workflow action, Assign To User. Checked against the Help Center on 29 October 2026.
Want this set up for you?
30 minutes, a clear next step.
Anis Mahmud Anik
HighLevel Certified Admin. I set up and automate GoHighLevel for founders and owners.



