Fictional studio example / annotated wireframe
An inspectable design specimen, not a client screenshot, completed provider integration or measured result. Interface choices illustrate the task described in this guide.
Fictional studio prototype
Try the interface decisions below. Entries stay in this page and disappear when it is reloaded. Nothing is ordered, booked, submitted to a company or saved to an account.
Appointment / request, confirm and cancel
Fictional showroom visit. The sample starts with a request; confirmation is a separate simulated staff action. These are demonstration states, not appointment availability or cancellation terms.
No request made.
Acceptance criteria
- A request is visibly different from a confirmed appointment.
- The selected slot is retained through confirmation.
- Cancellation produces a separate canceled state and allows a new request.
- Changing a slot clears the previous state instead of silently moving a confirmed appointment.
Show the appointment choice and confirmation state
Show service fit, the intended slot, preparation and the receiver’s booking state before calling an appointment confirmed. Keep a request separate from a reservation and give conflicts a useful recovery action. The showroom-visit prototype can demonstrate the flow while actual price, deposit and cancellation conditions remain owner-supplied.
Worked example — illustrative data.
| Screen | Specimen content | State to confirm |
|---|---|---|
| Service choice | Individual showroom visit; scope supplied by owner | Actual service and suitability |
| Availability | Date/time selection with time zone where relevant | Current scheduler availability |
| Preparation | What to bring and where to arrive | Owner-approved instructions |
| Confirmation | Reserved appointment or request received | Actual receiver state |
| Change route | Supported reschedule/contact action | Approved policy and provider behavior |
Start with the business’s actual appointment action and list the facts needed before it. Keep price, duration, deposit and cancellation conditions out of the specimen until the owner approves them. Show where the customer moves to an external provider and keep the business identity consistent. Test one available slot, an unavailable slot and a failure state with synthetic appointments. Include a supported route for questions that do not fit the booking form.
Show the boundary between requesting and reserving
Write the exact state above the final button: request an appointment or reserve this available time. In the showroom example, rehearse a slot conflict and show how the customer chooses another time without losing their service choice. The confirmation should repeat the date, relevant time zone, destination and supported change route only when the booking system has actually accepted them.
A selected slot may disappear before confirmation
Availability can change between selection and confirmation. Explain a conflict and offer a fresh choice instead of showing a successful booking for a slot the receiver did not reserve.
Accept the journey when service fit, location, preparation and booking state are clear. This studio concept makes no clinical claims and demonstrates no actual appointment integration.
What if the business has walk-in and appointment hours?
Show the schedules beside the action they govern. A showroom may accept visits while consultations require a reserved appointment. Confirm those rules with operations and avoid using one broad opening-hours statement to promise a bookable slot.
Continue with Guides for stores, software teams and local businesses, Website design for local businesses and Write a website brief for a local business.