See the problem, repeat the steps, and know what to check after a fix. Here is a compact example of the review you would receive.
Synthetic example · fictional website
Cedar & Coil is a local test site with a deliberately broken button. These results summarize a recorded browser rehearsal on September 17, 2026. They are not customer results. Evidence panels below are text summaries, not screenshots.
Cedar & Coil — customer journey review
REVIEW LPQ-SAMPLE-01 · SEPTEMBER 17, 2026
Agreed paths
Maintenance link, quote form, local receipt
Environments
Desktop browser + 390 × 844 mobile emulation
Test boundary
Local fixture, fixed synthetic data, no external delivery
ISSUE FOUND
Maintenance button
The button opened a missing page. The intended quote flow was blocked.
OBSERVED WORKING
Quote form
A valid test submission displayed a confirmation and unique reference.
REAL DELIVERY NOT VERIFIED
Inbox or CRM
A local test receipt matched. No real email or CRM was connected or tested.
FINDING 01 · PRIORITY: HIGH · BLOCKS THIS PATH
The maintenance button opens a missing page.
Issue found
Steps to reproduce
Open the fictional Cedar & Coil homepage.
Select Explore maintenance options.
Observe the destination /maintenance.
Expected result
A visitor reaches the maintenance quote form.
Observed result
The destination returns a missing-page response and shows “This page isn’t here.” The visitor cannot continue through this button.
Recommended action
Point the button to the intended quote form, with the maintenance service selected. Confirm that destination before publishing the change.
Recorded result · text evidence summary
Homepage → /maintenance
This page isn’t here.
The broken path was deliberately planted in the fixture. No real business defect is implied.
Retest: corrected path worked
The repaired button opened /quote?service=maintenance, with Seasonal maintenance selected. A subsequent synthetic submission generated a receipt matched in the local test inbox.
Retested in the local fixture
CHECK 02 · FORM SUBMISSION
The quote form shows a confirmation.
Observed working
Steps checked
Open Request a demo quote from the homepage.
Use the fixed fictional identity and select a service.
Acknowledge the synthetic test and submit.
Record the on-page confirmation and reference.
Observed result
The desktop Heating tune-up submission showed “Synthetic request received.” A mobile-emulation Plumbing check submission also produced a reference. Submitting without a service triggered the browser’s required-field message.
Interpretation
The exercised form paths worked in these test conditions. This does not establish every validation case, every device, or delivery to a real inbox.
Recorded desktop confirmation
Synthetic request received.
DEMO-E182BA1D7C21417AB7620A182B00176B
September 17, 2026 · 02:21:21 UTC Heating tune-up · Desktop rehearsal
On-page confirmation observed
Mobile environment
390 × 844 CSS pixels, using browser emulation. No physical phone was tested. This is functional evidence, not a claim of complete mobile compatibility.
CHECK 03 · RECEIVER CONFIRMATION
A local receipt matched. Real delivery stays unverified.
Limited evidence
Steps checked
Record the exact reference after the test submission.
Open the separate local rehearsal inbox.
Match the reference, selected service, and rehearsal label.
Observed result
The exact desktop reference above appeared in the local inbox with its service and label. The mobile and repaired-path retest references were also matched separately.
What this confirms
The local fixture stored matching test receipts in process memory. They disappear when that fixture server stops.
Delivery status, kept separate
Local fixture receipt
Matched in rehearsal
External email or CRM
Not tested · not verified
No external receiver was connected. On a customer review, authorized inbox or CRM evidence would be needed before marking real delivery verified.
Scope and limits
This sample covers the exercised local paths only. It excludes security testing, accessibility certification, performance benchmarking, real bookings or purchases, real email and CRM integrations, physical-device testing, and every page outside the agreed paths. The earlier fixture also had a form-origin problem that was repaired before the successful submissions above; successful results do not mean the fixture was always working.
Customer reports identify the tested environment, observations, relevant evidence, actionable findings, and untested areas. Evidence is gathered for the agreed scope; internal tooling does not automatically complete every browser check or prove destination delivery.
Know what you are paying to check.
The proposed $299 pilot includes one scoped report and one retest requested within seven days.