GoHighLevel Workflow A/B Testing: How to Set Up the New A/B Test Action

Short answer: GoHighLevel workflows now have an A/B Test action. You add it to a workflow, create 2 to 10 paths, pick one goal (such as an appointment booked, a form submitted or an invoice paid) and choose when the test ends. HighLevel splits contacts evenly across the paths, shows the conversion rate of each, and can automatically send every new contact down the winning path once the test is over. HighLevel listed it in its official LevelUp Day 2026 roundup and published a help article on October 27, 2026 (Official). No separate price or beta status has been announced.

What the A/B Test action does

Workflows have long had a Split action that sends a share of contacts down different branches. It splits traffic, but it does not tell you which branch worked. The new A/B Test action adds the missing half. According to HighLevel's help article (Official), it:

• Splits contacts evenly across 2 to 10 paths. Custom percentages are not offered.
• Measures every path against the same winning criteria, so the comparison is fair.
• Shows Entered, Converted, Conversion % and the Winner for each path on a Statistics tab.
• Ends the test after a number of contacts, a number of goal completions, or on a date and time you choose.
• Then either sends new contacts to the winning path, or keeps splitting and simply shows the result.

Contacts already inside a losing path finish their sequence; only new contacts are rerouted. On the canvas the winner gets a Winner badge and the other paths are muted.

How to set it up

1. Go to Automation, then Workflows, and open or create a workflow.
2. Click the plus icon to add an action and choose A/B Test.
3. Name the action and add 2 to 10 paths. Give each path a clear name, such as "SMS first" and "Email first".
4. Under Winning Criteria, choose a Goal event (email activity, trigger link clicked, appointment status, form submitted, payment received or invoice paid) or a Custom condition based on a contact or custom field, such as a lead status of Qualified.
5. Under Test length, choose when the test ends: total contacts entered, goal completions, or a date and time in the account's time zone.
6. Under After the test ends, choose Send new contacts to the winning path or Keep splitting and show the result.
7. Save the action, build the actions inside each path, then save and publish the workflow.

You can stop early with Declare winner. If two paths tie, HighLevel names the first tied path the winner. Reset test starts a fresh comparison, and saving after a reset clears the old results.

What to test first

Pick something where a small change can move booked jobs or paid invoices, not just opens. Good first tests for a service business:

• First touch on a new lead: an instant text versus an instant email plus a text five minutes later, with the goal set to appointment booked. If you are still building that first response, our speed to lead guide covers the basics.
• Quote follow-up: three short texts over a week versus one text and one email with photos of past work, with the goal set to invoice paid or a pipeline stage. See our quote follow-up automation guide.
• No-show rescue: a rebooking link right away versus a call task for staff, with the goal set to a new appointment status.
• Old lead reactivation: an offer versus a simple check-in question, with the goal set to reply or booking.

Change one thing per test. If path B has a different message, a different channel and a different delay, you will not know which change won.

Mistakes to avoid

• Ending too early. HighLevel does not set a minimum sample size and notes that path counts can differ early on. With 20 contacts per path, one booking can flip the result. For most small businesses, set the test to end after at least 100 to 200 contacts, or on a date a few weeks out.
• Choosing a goal that fires too easily. An email open is a weak goal; Apple Mail privacy features inflate opens. Prefer a booked appointment, a submitted form or a payment.
• Testing inside a workflow that already sends the wrong message. Fix the base workflow first. Our guide on why a GoHighLevel workflow sent the wrong message helps there.
• Forgetting compliance. Every SMS path still needs consent and opt-out language. A test does not change your A2P obligations.
• Resetting by accident. Saving after Reset test wipes the results. Write down the numbers before you reset.

A/B Test vs Split: which to use

Use Split when you only need to divide traffic, for example sending half your leads to one sales rep's sequence for workload reasons. Use A/B Test when you want an answer: which sequence produces more bookings or payments, and you want the workflow to act on that answer automatically.

What it means for agencies

For agencies, the A/B Test action turns "we think this follow-up works" into a number you can show a client. Build tests into your snapshots with sensible defaults (two paths, a booking goal, a test length of 200 contacts) so every new account starts learning from day one. Report the Statistics tab in monthly reviews alongside your normal SMS and email reporting.

Where this fits in LevelUp 2026

Workflow A/B testing is one of about 175 releases in HighLevel's LevelUp Day 2026 roundup, alongside Workflow Maps, Meeting Room and new Managed Agents features. We track them with Official or Reported labels on our LevelUp 2026 live announcements page. If you want help choosing what to test, our GoHighLevel account audit reviews your workflows, and the speed to lead sprint builds and tests your first-response sequence for you. You can also book a free discovery call at meet.yotomations.com.

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 2026-10-28