PathsentraEvery lead journey, verified.
AGENCY OPERATIONS

A practical HighLevel QA checklist for every client sub-account.

Use this before launch, after material configuration changes, and on a recurring schedule for the journeys that directly affect enquiries and appointments.

Pathsentra field guideUpdated 19 August 2026

Define the test before touching the account

  • Name the exact client location and assets in scope.
  • Agree on a clearly labelled synthetic identity format.
  • Select the form, funnel or entry point and expected calendar.
  • Record timezone, test window and cleanup procedure.
  • Disable customer-facing notifications for synthetic testing where appropriate and authorized.

Lead Path

  • Submit a unique labelled test contact through the actual prospect-facing entry point.
  • Verify the exact contact inside the intended sub-account.
  • Record contact ID, creation time and source when available.
  • Confirm required fields and routing behaved as expected.
  • Separate contact creation from downstream workflow checks.

Booking Path

  • Open the actual prospect-facing booking link.
  • Confirm an expected slot is available in the correct timezone.
  • Create one controlled appointment on the intended calendar.
  • Verify appointment ID, time, calendar and confirmed status.
  • Check only the notifications explicitly included in the agreed scope.

Evidence to retain

  • Location name or internal identifier.
  • Test-run identifier and timestamps.
  • Exact contact and appointment identities.
  • Pass or failure at each stage.
  • Failure response and the last verified successful step.

Failure handling

Stop the run at the first unambiguous failure. Record the affected location, failed stage, observed response and time. Do not repeatedly rerun a combined test if doing so would create uncontrolled duplicate contacts or appointments.

Recommended cadence

Run after launches and material changes, then choose a recurring frequency based on lead value, change frequency and operational risk. Daily checks may suit high-value booking paths; lower-risk locations may need less frequent verification.