HighLevel Black Friday + Cyber Week, Nov 23 to Dec 6: 50% off your first 3 months, plus upgrade and add-on deals and a bonus from Yotomations.HighLevel 50% off for 3 months, Nov 23 to Dec 6. Find my deal
The GoHighLevel practice of Yotomations LLCAI development, custom software and websites at yotomations.com
New to GHL? Start here

How do I split leads evenly between reps in GoHighLevel workflows?

GoHighLevel's Split action now has even and weighted modes. Here is how to share leads between reps or test a new text without a spreadsheet.

People sitting at the table
By Yaakov (Koby) Oranski, Certified GoHighLevel Admin and Partner | | 6 min read

Short answer: The Split action in GoHighLevel workflows now has two modes: Even split, which sends contacts down each path in turn, and Weighted split, which lets you favor some paths over others. Use Even split to share inbound leads between reps. Use Weighted split to try a new message on a smaller group, or to give a new rep fewer leads at first. Neither mode knows who is available, so add business hours and a fallback path.

Prefer to watch? The 47-second version

GoHighLevel's Split action now has Even and Weighted modes so you can share leads between reps or test a new message without a spreadsheet.

Watch it on its own page, with the transcript.

One lead, split between two repsONE LEAD, SPLIT BETWEEN TWO REPSNew leadForm, call or Yelp leadenters the workflowSplit actionEven split or WeightedsplitPath A: first repAssign user, tag, notify,first textPath B: second repAssign user, tag, notify,first textRep is out todayThe split does not checkavailabilityBookedOpportunity moves,reminders startentersturn oneturn twoif rep is outThe Split action chooses a path by rule, not by who is free, so the fallback has to be built around it.

What the two split modes do

HighLevel announced the change in its November 13, 2026 changelog. The Split action now supports Even split and Weighted split, giving you more control over how contacts move through your workflow paths. The Even split sends contacts to each path in turn, so the distribution stays balanced. The Weighted split lets you decide how heavily each path is favored.

The practical meaning is simple. If you have two estimators and a form that sends every lead into one workflow, you no longer need a spreadsheet, a manual assignment or a random split that happens to give one person six leads in a row. The workflow does the dealing.

The changelog excerpt we have is short, so check the action's settings panel in your own account for the exact options. We describe the behavior here and tell you what to test, not every field on the screen.

Sharing leads between reps with an Even split

This is the pattern we build most often for home service companies with two or three people taking calls or quotes. The workflow trigger is your lead source: a form submission, a Yelp lead, a missed call. The first action after any cleanup is a Split set to Even, with one path per rep.

Each path does the same four things:

  1. Assign the contact (and the opportunity) to that rep with the assign-to-user step.
  2. Add a tag such as lead-rep-maria, so you can count later who got what.
  3. Send an internal notification, by text or email, to that rep only.
  4. Send the first text to the lead, signed with that rep's first name.

The tag is the part people skip. Without it, your only evidence of fairness is the contact list filtered by owner, which breaks the moment someone reassigns a lead by hand. With a tag per path, a smart list shows exactly how many contacts each path received.

If a rep should not get speed-to-lead leads during off hours, read our speed to lead system first. The split decides the owner, but the five-minute response rule still needs a timer and an escalation.

Trying a new message with a Weighted split

A weighted split is the safer way to change something that works. Say your reactivation text has been booking jobs and you want to try a shorter version. Send most contacts down the old path and a smaller share down the new one. If the new path produces replies and bookings, shift the weights. If it produces opt-outs, you stopped the damage early.

The same idea works for people. A new rep gets a lighter share of leads in their first weeks, then you raise the weight once they are comfortable. You change one setting instead of rebuilding the workflow.

Tag every path here too. A weighted test with no tags tells you nothing, because you cannot tell which message a contact received. If you want built-in comparison reporting, look at the dedicated workflow A/B test action as well, and choose the one that matches how you want to read results.

Where a split breaks

A split is a dealing machine, not a manager. It does not look at who is on vacation, who already has six open quotes or whether it is 11 p.m. A lead dealt to an absent rep sits there, and that is the exact problem you were trying to remove.

SituationUseAdd around it
Two reps share every lead equallyEven splitTag per path, task if no reply from the rep
New rep ramping upWeighted splitRevisit the weights on a calendar date
Testing a new first textWeighted splitTag per path, review replies and opt-outs
Lead goes to the rep who owns the territoryIf/Else or Router, not SplitCondition on zip code or service type
Rep out for the weekRemove their pathFallback owner, or a task for the office manager

Two more things to test before you trust it. First, check the workflow's re-entry setting, because a contact who enters the workflow a second time may land on a different path and get a second rep and a second text. Second, run a handful of test contacts through and read the execution log to confirm which path each one took. Do this with real phone numbers you control, and only then connect the live lead source.

Split, Router or If/Else: which one

If the contact's own data should decide the path, a service type, a zip code, a source, use If/Else or the Router action, which can run every matching branch. If you do not care who the contact is and only care that the load is shared or tested, use Split.

Many real builds use both. A Router sorts roofing from gutter leads, then each branch has a Split that deals the lead to whichever estimator handles that work. That keeps each workflow short, and short workflows are easier to audit later, which matters when stages need to move themselves and nobody wants to open a 160-workflow account to find out why.

What we would do first

We would map who should receive which leads, write down what happens when a rep is out, and build one workflow with a Split, a tag per path and a fallback task. Then we would test it with a few numbers before any live lead touches it. If your real problem is that leads wait too long for a first reply no matter who owns them, the Speed to Lead Sprint (starting at $1,950) covers the whole path from lead to first text to booked call. For one-off workflow work, see our GoHighLevel automation service.

Yaakov (Koby) Oranski

Yaakov (Koby) Oranski, Founder and CEO of Yotomations

Certified GoHighLevel Admin and Partner. Koby designs CRM migrations, two-way integrations, billing systems and AI agents for service businesses, and writes from the engagements described on this site.

Published

Frequently asked

What is the Split action in GoHighLevel?

It is a workflow action that sends contacts down different paths. HighLevel's November 13, 2026 changelog says it now supports Even split and Weighted split, which give you more control over how contacts move through your workflow paths.

Can GoHighLevel round robin leads between sales reps?

For booking, calendars have their own round robin for team members. For leads that enter a workflow, an Even split with an assign-to-user step on each path gives you a similar result, and you should confirm the behavior with test contacts in your own account.

What is the difference between a Split and the Router action?

A Split decides where a contact goes by distribution: in turn, or weighted. The Router action evaluates conditions and can run every matching branch. Use Split when you do not care who the contact is, and Router when the contact's data decides the path.

Is a weighted split the same as an A/B test?

They overlap. A weighted split lets you send a smaller share of contacts to a new path, which is a common way to test. HighLevel also has a dedicated A/B Test action for workflows, covered in our separate article, so pick the one that gives you the reporting you need.

Keep reading

Is this happening in your account?

Book a 30-minute call. We look at the account live and tell you what is broken, what we would fix first and what it would cost.

No pitch deck. We look at your current setup and tell you what we would do and what it would cost.

Need more than GoHighLevel? Yotomations, our parent company, also builds AI agents, custom software and websites.