HighLevel is software agencies can use to manage contacts and automate follow-up. Suppression is a record that prevents future email sends. This guide separates recorded actions from messages independently received in an inbox.
1. Start with a clear subscription request
Our form collects an email address and requires an initially unchecked consent box. The wording describes five first-workflow lessons over seven days and says the reader can unsubscribe. We collect no phone number and enroll no one in SMS through this form.
We enabled native email verification. In our recorded tests, submission without consent was blocked. Consent without completed verification was also blocked. An incorrect verification code was rejected; the correct code marked the controlled address as verified. HighLevel describes this feature in its email-validation documentation.
This verifies the form behavior we observed. It does not prove that every possible bypass is prevented. We checked enrollment separately because a saved form submission alone does not establish that a lesson was sent.
2. Define both the series and its exits
- Verify the address and record the subscription request.
- Check eligibility and mark the contact as enrolled.
- Send lessons on days 0, 1, 3, 5, and 7, checking suppression before each send.
- On unsubscribe, preserve the suppression record and remove the pending lesson enrollment.
Before each send, our workflow checks that email do-not-disturb is absent and that neither an email-suppression marker nor a support-hold marker is present. Initial eligibility also excludes contacts already marked enrolled. Reentry is disabled; Stop on Response is enabled.
Those are saved conditions in our setup. The next step was to test behavior: whether messages arrived, where their links went, and what happened after a recipient opted out.
3. Run a restricted copy with shortened waits
We created a separate test copy limited to two owner-controlled addresses. We shortened its waits to minutes, then returned it to draft after testing. This let us inspect the sequence without exposing an accelerated campaign to subscribers.
One address received all five lessons. We inspected sender identity, content, publisher footer, affiliate disclosure, unsubscribe information, and unresolved placeholders. The recorded message checks showed SPF and DKIM passes (email-authentication checks). One lesson appeared in Gmail's Promotions category; authentication does not promise a particular inbox placement.
We opened every distinct lesson destination: the lead-follow-up guide, usage-cost guide, calculator, and trial checklist. The all-five run established delivery through the accelerated copy. It did not establish seven elapsed days of production delivery.
4. Unsubscribe, then try the form again
The other address received lesson one and used its native unsubscribe link, including the confirmation step. Contact and workflow history then showed the suppression marker, checked email do-not-disturb, and removal from the active lesson sequence.
A bounded mailbox check after the canceled next-send time found only the first lesson. We also resubmitted the verified form for that opted-out address. Suppression remained in place, and the recorded history showed the original finished enrollment without a new run.
This is evidence that the tested repeat signup did not silently undo that opt-out. It does not establish every duplicate, bounce, complaint, or reply-handling variation.
5. Repeat the essential path in production
A separate controlled address used the production form and original day-based schedule. It verified its email, consented, entered the series, received lesson one, and unsubscribed. Contact readback confirmed suppression and email do-not-disturb.
After updating the visible brand to Agency Fieldbook, we repeated verification, first-lesson delivery, and unsubscribe. The new verification email and first lesson showed the intended brand, and workflow history confirmed removal. All five updated sender/footer configurations were read back. The later uninterrupted production test below established receipt of all five messages; it did not include a full content, footer, link and header inspection of every delivered message.
September 30-October 8: production timing verified
On September 30, a separate controlled reply reached our public business mailbox through the configured forwarding route and appeared in its native Conversation. We verified the received message in the mailbox; we did not rely only on the saved forwarding setting.
A new consenting test enrollment kept the original day-based schedule. Its day-0 lesson reached the business inbox on September 30 at 09:30, with SPF and DKIM passes. The day-1 send executed on October 1 at 09:32:00, and the corresponding inbox receipt displayed 09:32. Times are America/Tijuana (UTC-7); exact receipt seconds and authentication headers were not rechecked for day 1. These are controlled test receipts, not customer enrollments.
On October 8, we confirmed all five lessons from the original production schedule in the controlled business inbox. The final lesson executed October 7 at 09:32:15 America/Tijuana, and the enrollment finished at 09:32:17. Its independently observed INBOX receipt displayed 09:32, with minute precision. This establishes the completed seven-day cadence for one controlled address; it does not establish customer delivery rates or referral attribution.
| Lesson | HighLevel recorded send action | Independent INBOX receipt |
|---|---|---|
| Day 0 | September 30, 09:30:49 | September 30, 09:30 |
| Day 1 | October 1, 09:32:00 | October 1, 09:32 |
| Day 3 | October 3, 09:32:02 | October 3, 09:32 |
| Day 5 | October 5, 09:32:12 | October 5, 09:32 |
| Day 7 | October 7, 09:32:15 | October 7, 09:32 |
What this test proves-and what it leaves open
| Area | Observed | Still unverified |
|---|---|---|
| Signup | Consent and email-code validation behaved as described. | Every possible validation bypass. |
| Five lessons | All arrived in the accelerated run; all five original-production sends and independent INBOX receipts verified. Enrollment finished October 7. | Delivery rates across genuine subscribers and other mailbox providers. |
| Current branding | Updated verification and first lesson delivered; current-design day-0 message inspected September 30. | Full content, footer, link and header inspection of every delivered message. SPF/DKIM evidence for this production cohort is day 0 only; DMARC pass remains unestablished. |
| Unsubscribe | Suppression and enrollment removal occurred. | Every bounce or complaint variation. |
| Repeat signup | The opted-out test address did not restart. | Every duplicate or reentry scenario. |
| Replies | Controlled reply observed in Conversations and the forwarded business inbox September 30. | Every reply-routing or mailbox-provider variation. |
What can an agency approve with this evidence?
Acceptance criteria are the checks an agency and client agree must pass before handover. Use two separate controlled scenarios for a new project: one address completes the uninterrupted schedule, and another tests opt-out. Unsubscribing the cadence address prevents it from proving full timing. This is a proposed test design for your project; preserve completed test records.
- Entry
- Complete consent and verification, then confirm the correct enrollment. If entry conditions fail, fix them before accepting subscribers.
- Timing and receipt
- Record the native action and independent mailbox receipt for every due lesson, with time zone and timestamp precision. Investigate missing evidence; a successful action alone cannot pass delivery.
- Content
- Read delivered branding, placeholders, destinations and disclosures. Keep content approval open when only receipt has been checked.
- Exit
- In a separate controlled opt-out test, verify suppression, removal of pending sends and repeat-signup behavior. Hold expansion until the agreed exit checks pass.
- Business outcomes
- Record genuine subscribers and independently supported referrals separately, excluding every test. Operational QA alone does not establish conversion.
Give each unresolved check a named owner, due date and handover decision. Use the agency client onboarding guide to agree those responsibilities before rollout.
Method and platform reference
Our timestamps and receipts are controlled first-hand observations. HighLevel documents how Execution Logs and Enrollment History expose workflow progress and entry/exit status. Reference reviewed October 15, 2026. The approval checklist is Agency Fieldbook's proposed agency decision aid.
A checklist for your own email series
- Use an address you control and complete the actual signup form.
- Read the delivered message rather than relying only on a successful send action.
- Open the real lesson links and check that a reader can access them.
- Unsubscribe and inspect both suppression state and pending enrollments.
- Test repeat signup without clearing the opt-out record.
- Document which schedule, sender version, and scenarios you actually tested.
Keep accelerated results separate from elapsed production days, authentication separate from inbox placement, and delivery separate from business outcomes. Our later public-launch checks confirmed anonymous access to the guide and signup destinations. They do not establish search rankings or genuine subscriber demand.
Our observations are recorded from our own controlled test. Recipient addresses, verification codes, and private account records are withheld. Email opens and clicks can be tracked by HighLevel; this is separate from our optional website measurement. Read our privacy explanation.