Home

Accepting a website change from the customer's starting point

A developer can confirm the changed field works while a customer still cannot reach it. Define acceptance as a complete journey with an observable outcome and a person who can confirm it.

Customer action

For a service-page change, start from the actual campaign or navigation link on a phone. Read the offer, follow the enquiry button, try an invalid field, correct it and submit a labelled test. Ask sales to find that label at the destination.

Customer entry → Customer action → Receiving team
Customer entry → Customer action → Receiving team

Where did the revised customer journey first fail?

Keep one negative test alongside the successful path. A required field should explain how to correct an error without discarding the visitor's other entries.

Illustrative record: Expected next step (SKU-42 → FORM) / Observed next step (FORM · SKU ∅)
If tapping the enquiry button opens the form but drops the selected product, capture that first divergence. A successful submission later does not establish that sales received the right context.

Acceptance evidence · Observed next step

Keep the URL, device, expected result and first failed step together. Retest the failed step and the steps after it once fixed. Reuse the record the next time the same template changes.

Share the changed URL and intended outcome with DigiWeb for an acceptance checklist

Let’s start with
what you need.

Tell us about your project or the website issue you need to resolve. DigiWeb will work through the next steps with you.

info@digiweb.com.vn0902 604 802Nguyễn Đức Thái · Founder DigiWeb