We set up and check email sequences in GoHighLevel for clients. On one of those jobs we needed to prove a new email was right before it reached real customers: the right name filled in, the right footer, the right reply address. The test looked like it had failed. It had not.
Three things tripped us up, and each one has a simple fix. None of them needs any special skill, only knowing where to look.
1. The test email went to spam, not nowhere
GoHighLevel's "Test workflow" and "Run test" buttons do send real emails. Ours landed in the spam folder, so a search of the inbox found nothing at all, and it looked as if nothing had been sent.
What we checked first
- Searched the inbox only
- Found nothing
- Assumed the test had not sent
What we check now
- Search spam and all mail, not just the inbox
- Find the email that really went out
- Then decide whether there is a problem
Quick habit: before you call a test a failure, look in spam and in all mail. A missing test email and a test email in spam look exactly the same from the inbox.
2. You can read the exact email without waiting for it to arrive
What you really want to know is whether the email itself is right. You do not need it to land in anyone's inbox to check that. GoHighLevel keeps a record of every email it sends inside the contact's conversation history, and that record holds the full email.
Open the conversation for the test contact the email went to.
Pick out the email message in that conversation.
The record shows the subject line, who it came from, the reply address, who it went to and the whole body.
Confirm names filled in properly, the footer is there and replies go to the right address.
We did this behind the scenes, through GoHighLevel's connection for other software, because the screens we would normally click were not open to us that day. Even when that connection was not allowed to touch the sequences themselves, it could still read contacts, tags and conversations, which is all this check needs.
3. A contact that already went through will not go through again
This one is easy to miss. GoHighLevel will not put a contact through the same sequence twice. So if you reuse an old test contact, the new test simply does not run, and nothing tells you why.
One that has never been enrolled in anything. Fill in any custom details the email uses, so the name and other fields have something to show.
If your sequence is published and starts when a tag is added, the new contact is enrolled and a real email goes out.
Check it the same way as in step 2, then check spam and all mail if you want to see where it landed.
Testing with your own inbox can mislead you
It feels natural to send test emails to yourself to see whether your emails reach people. The catch: once your own mailbox has marked a sender as spam, Gmail keeps sending everything from that sender to spam. That is a judgement about your mailbox only, not about everyone else's.
For a fair answer, use a neutral check. A free tool such as mail-tester.com gives your email a score out of 10. Then check that your domain's sender records (SPF, DKIM and DMARC, the settings that prove an email really came from you) are in place, and look your domain up on the public blocklists Spamhaus DBL and SURBL.
If the records are set up and both blocklists are clean, your setup and reputation are fine. Emails landing in spam then usually come down to a new sending domain still warming up, or how people are engaging with it, rather than anything broken.
How This Fits Into a Balay ni Bruno & Co. Partnership
When we run email for a client, a real person on our team checks every new email before it reaches their customers, and our AI tools help that person read the exact email that went out instead of guessing from an inbox. It is one small part of making sure nothing reaches your customers that you have not seen and approved.
Common Questions
Does the GoHighLevel test button send a real email?
Yes. When we ran a test for a client, real emails went out. They simply landed in the spam folder, so a search of the inbox alone showed nothing. Always check spam and all mail before deciding a test failed.
Why won't my test contact get the email a second time?
GoHighLevel will not put a contact through the same sequence again once they have already been through it. An old test contact quietly blocks a new test. Create a fresh contact that has never been enrolled and add the tag that starts the sequence.
Is sending a test to my own inbox a good way to check if my emails reach people?
Not on its own. Once your own mailbox marks a sender as spam, it keeps sending that sender to spam, and that is about your mailbox only. A free tool such as mail-tester.com gives a neutral score out of 10, and checking your domain's sender records and the public blocklists tells you whether the setup itself is healthy.
Key Takeaways
- GoHighLevel's test buttons send real emails. Check spam and all mail before calling a test a failure.
- You can read the exact email a contact received, subject, sender, reply address and body, from their conversation record.
- A contact that already went through a sequence will not go through again. Use a brand new test contact.
- Your own inbox is not a fair test of whether emails reach people. Use mail-tester.com, your sender records and the public blocklists.