THE RESULT YOU'RE WORKING TOWARD
Done means it works.
A repeated event does not create a second request for the same visit, while a valid later visit follows the documented rule.
Practice project: One verified business location01 / GET READY
Before you start.
- Platform / editor
- Google Business Profile; HighLevel only for workflow exercises
- Access & plan
- Authorized Business Profile access for link and QR tasks. A real customer experience is required to post a review; these exercises do not publish test reviews.
- 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.
- 01
Step 1
Choose a request key that identifies both the customer and completed service or visit. Define the allowed repeat interval.
- 02
Step 2
Record when a request has been queued or sent and check that state before creating another one.
- 03
Step 3
Replay the same completion event and inspect tasks or sends. Then test a genuinely different eligible visit.
- 04
Step 4
Document how failed sends are retried without marking an unsent request as successfully delivered.
04 / GET UNSTUCK
If something goes wrong.
Start with the likely cause
If retries duplicate requests, distinguish pending, failed and delivered states rather than using a single yes/no field.
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.
A repeated event does not create a second request for the same visit, while a valid later visit follows the documented rule.
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.