A Split action in GoHighLevel sends contacts down random paths by percentage, so two or three subject lines can go to separate groups, and the winner is the one that gets more RSVP clicks. The bottom line: judge the test by clicks and RSVPs, never by opens, and run it across several open houses, because one small list rarely tells you which subject line is actually better.
What the Split action does
GoHighLevel's help page says the Split action sends contacts down different paths by percentage, up to 5 paths, with the percentages totaling 100, and that its only criterion is random. To divide contacts by something specific, such as price range, use If/Else instead. Changes to a split apply only to contacts who enter afterward. A third party guide adds that the action can track stats for each path in the workflow. Confirm what your account shows.
Why not opens
Apple's Mail Privacy Protection preloads images, so opens are inflated, and Twilio SendGrid advises relying on clicks and conversions. For an open house invitation the conversion is clear: the recipient taps an RSVP link. Put a trigger link on the RSVP button and count clicks per path.
How big a test do you need
Small samples mislead. Suppose each subject line goes to 250 people and the true RSVP click rate is 20 percent. The standard error of one group's rate is the square root of (0.2 times 0.8 divided by 250), about 2.5 points, so a 95 percent margin is about plus or minus 5 points. The difference between two groups has a margin of about plus or minus 7 points. So 22 percent against 18 percent on 250 each is within noise. That is our arithmetic, and it assumes simple random groups. To get a clear answer, run the same test across several open houses and add the results, or test a bigger change than a word.
| Test | Version A | Version B |
|---|---|---|
| Specific against generic | Open house Saturday 1 to 3 p.m. at 123 Oak Street | You are invited to an open house this weekend |
| Question against statement | Want to see 123 Oak Street this Saturday? | 123 Oak Street open house, Saturday 1 to 3 p.m. |
| Detail against urgency | 3 bed, 2 bath open house Saturday | Open house Saturday only, 1 to 3 p.m. |
Subject line rules
- Be honest. CAN SPAM bars deceptive subject lines, and requires a valid physical address and an opt out.
- Keep to the property facts. Avoid phrases like family friendly or perfect for families, which can signal a familial status preference under the Fair Housing Act.
- Include the date and address. Specific subject lines are easier to act on.
Why open houses are worth testing
NAR's 2025 Profile reports that 48 percent of buyers used an open house as an information source. An invitation that gets more RSVPs puts more buyers in the door, and the sign in sheet is a source of leads, with consent language on it.
Build it in GoHighLevel
- Create a trigger link for the RSVP page, with the property in the destination.
- Build a workflow that starts when an open house is scheduled and a list of contacts is added with a tag.
- Add a Split action with 2 or 3 paths and equal percentages totaling 100.
- In each path, send the same email with a different subject line, and the same RSVP trigger link.
- Add a workflow with the Trigger Link Clicked trigger that tags the contact RSVP and records which path they came from in a field.
- After the open house, compare RSVP clicks per path, and keep a running table across open houses.
- Declare a winner only when the difference is larger than the margin above, or after several events.
Worked example
For example, over four open houses a team sends each subject line to 250 people each time, 1,000 per line in total (250 times 4). The margin on the difference between two groups of 1,000 is about plus or minus 3.5 points (1.96 times the square root of 0.32 divided by 1,000), so a gap of 5 points or more now means something.
Mistakes to avoid
- Judging by opens. Use RSVP clicks.
- Declaring a winner after one small test. Combine results.
- Changing two things at once. Test one difference.
- Misleading subject lines. They violate CAN SPAM.
How this was handled before
Agents wrote one subject line and guessed. Email platforms added A/B tests, and workflow splits now let a team test across several open houses, as long as results are judged by clicks and by enough volume.
What to measure after launch
Track sends per path, RSVP clicks per path, RSVPs by event, and attendance. Keep a running table across open houses.
Check before you switch it on
US text messages sent from a standard 10 digit number need A2P 10DLC registration. The HighLevel support portal says registration is required for texts to US recipients from 10 digit long code numbers and that toll free numbers do not require it. HighLevel's opt in guidelines also say a person cannot be forced to agree to text messages in order to submit a form, so keep the consent box optional. One compliance guide separates informational texts, which need documented consent, from marketing texts, which need prior express written consent. Ask your attorney which category your reminders fall into. Confirm each contact agreed to email, and keep the unsubscribe link in every message. This is general information, not legal advice.
Questions people ask
How does the GoHighLevel Split action work?
Its help page says it sends contacts down up to 5 paths by percentage, randomly, with percentages totaling 100.
Should I judge a subject line test by opens?
No. Apple Mail Privacy Protection inflates opens. Use RSVP clicks and conversions.
How big a sample do I need?
With 250 per group at a 20 percent rate, the margin on the difference is about 7 points, so small gaps are noise. Combine several open houses.
Ready to try it yourself? Start a GoHighLevel account here.
You can also see this in action in our GoHighLevel capabilities demo.