Start with the written scope
Identify the entry points, intended route, people responsible, communications and exclusions. Agree on what “ready” means before reviewing the screens. Otherwise a polished demonstration can hide a disagreement about the actual job.
Use fictional information for a rehearsal. A live test may create appointments or send messages; arrange the exact test with the system owner rather than entering real customer information just to see what happens.
Walk through more than the ideal case
On a small screen, swipe or scroll sideways to read the full table.
| Scenario | What to inspect |
|---|---|
| Normal inquiry | Correct destination, useful context, owner and next action |
| Missing information | A clear request for what is needed, with an accountable owner |
| Owner unavailable | A realistic backup and visible unresolved work |
| Appointment changed or cancelled | Current instructions and removal of obsolete actions |
| Customer declines further contact | The request is recorded and unnecessary follow-up stops |
Check what each person can actually see
Read the customer-facing wording on a phone. Then inspect the team’s view. Does the responsible person have enough context? Can they distinguish waiting for the customer from waiting for the business? Are private details shown only where needed?
Check links, required fields, keyboard focus and what happens when a page or embedded service does not load. There should be an understandable way to recover or contact the business.
Keep a short result record
Scenario tested: appointment rescheduled.
Expected: new time visible to customer and assigned team member.
Observed: record the actual result.
Issue owner: name the person fixing a mismatch.
Ready decision: record who approved the agreed scope.
Keep “not checked” separate from “passed.” A saved configuration, a displayed widget and an observed completed action are different levels of evidence.
Separate readiness from purchase and access
For BusinessOS, a call, scope agreement, setup payment, installation review, monthly activation and client access are distinct steps. Booking a conversation does not start the service. The written agreement controls the commercial details.
This checklist helps a buyer ask useful questions; it is not a substitute for an authorized operational test or a promise that every system is ready.
Rehearse missing information and interrupted work.
Add two fictional cases to your rehearsal. First, give the reviewer a draft that turns a requested appointment into a confirmed booking. The reviewer should find the unsupported commitment and resolve it before the message can be used. The reply-review example supplies a practice case.
Second, make the usual record unavailable in a safe practice setting. The team should know where temporary work belongs, who owns it and what must be reconciled before resuming. Use the interruption-plan worksheet. Keep these rehearsals separate from live customer actions; a successful practice does not establish actual recovery performance.