LEAD RECOVERY / GUIDED PRACTICE

Handle communication opt-outs

Ensure opt-out state prevents further contact on the relevant channel.

Written by Ray / SETLYUpdated 1 October 2026

THE RESULT YOU'RE WORKING TOWARD

Done means it works.

The opted-out contact cannot reach the relevant sending action and its preference remains stored.

Practice project: Harbor enquiry recovery

01 / GET READY

Before you start.

Platform / editor
HighLevel workflows and contact records
Access & plan
Demo sub-account, test contacts and a known enquiry source. Real messages and calls require separate approval; use internal tasks or previews for dry runs.
Starting point
Complete the previous lesson or use an equivalent prepared demo project.

Keep a note of the exact account, project and version you use. Work with demo data and record the expected result before making changes. Never place passwords, verification codes or private customer records in your evidence.

02 / LEARN THE TOOL

Open the official walkthrough.

Use the publisher's instructions and available screenshots to locate the current controls. Then return here for the SETLY exercise and its result checks. These links open on the publisher's website.

Source credit belongs to the named publisher. These are external references, not SETLY recordings or a claim of affiliation. Screen names and plan availability can change.

03 / PUT IT INTO PRACTICE

Your task, step by step.

Use one labelled demo record or project so you can find your work again. Finish each action before continuing; if the screen differs, consult the matching official source rather than guessing.

  1. 01

    Step 1

    Identify the account's opt-out or do-not-contact fields for each enabled channel. Keep channel-specific preferences distinct.

  2. 02

    Step 2

    Check preference state before outbound steps and route opted-out contacts to a no-send outcome.

  3. 03

    Step 3

    Use the provider's supported test method to set an opt-out on a demo contact. Inspect queued work and the resulting workflow path.

  4. 04

    Step 4

    Verify an opted-in demo contact still follows the intended route. Do not override an opt-out merely to make a test pass.

04 / GET UNSTUCK

If something goes wrong.

Start with the likely cause

If one channel stops while another continues, check whether separate channel preferences and conditions are required.

My screen is different from the guide

Check the product, editor, account role and selected project first. Open the credited official instructions for your version. Record the difference and pause any action whose effect you cannot verify.

The screen looks correct, but the result is missing

Inspect the saved record, published page or execution log that should prove the action. A preview, success message or draft is not always evidence that data was stored or a message was delivered. Retest with one unique demo value.

05 / PROVE THE RESULT

Check it before you call it done.

The opted-out contact cannot reach the relevant sending action and its preference remains stored.

Keep useful evidence

Record the test date, project/version, expected result, observed result and a non-sensitive screenshot or record reference. Mark anything you did not test as untested. Your checkmarks do not certify an untested result.

Download the editable verification checklist ↓

Guide status: original written practice exercise with credited external references. SETLY screen recording and independent learner reproduction are not yet complete.

KEEP BUILDING

Next / 09Test duplicate submissions ↗