THE RESULT YOU'RE WORKING TOWARD
Done means it works.
The corrected behavior passes the original failing cases and routine cases still work.
Practice project: Harbor enquiry helper01 / GET READY
Before you start.
- Platform / editor
- HighLevel Conversation AI and supported knowledge-base tools
- Access & plan
- Demo account with the relevant AI feature enabled and an approved test budget. Voice AI and chat may have different configuration and usage requirements.
- 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 small set of labelled test conversations and categorize errors as missing knowledge, wrong action, poor routing or unclear wording.
- 02
Step 2
Inspect agent logs for the first incorrect decision and compare its input with the approved source.
- 03
Step 3
Change the relevant source or configuration, record the reason and preserve the previous setting for comparison.
- 04
Step 4
Rerun the same test set. Report passed cases and remaining failures without turning a small test into a claim about all customers.
04 / GET UNSTUCK
If something goes wrong.
Start with the likely cause
If results vary between runs, repeat the scenario and inspect tool outcomes rather than selecting only the best response.
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 corrected behavior passes the original failing cases and routine cases still work.
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.