Loading, empty, error, and success: explain each step
Distinguish waiting, empty content, no matches, failure, and completion, with useful messages and next steps.
A website is not always fully loaded and working along the ideal path. Booking availability may still be loading, a search may have no matches, or an inquiry may fail. A design system prepares shared behavior for these situations instead of leaving each page to invent a vague message.
Different states mean different things
| State | What customers need to know | Useful next step |
|---|---|---|
| Loading | What is being processed | Wait, with cancellation when appropriate |
| No content yet | Why nothing is available here | Explanation and a suitable alternative |
| No matches | Current conditions found nothing | Change or clear conditions |
| Error | Which step did not complete | Safe retry or another contact method |
| Success | What actually completed | View the result or understand what happens next |
“No available appointments” differs from “The booking tool could not load availability.” One can suggest other dates; the other needs a failure explanation and an alternative contact route.
What a useful message includes
Explain what happened, then what the customer can do. Do not present a server code as the whole explanation or overwhelm them with internal details. Provide a clear support route when needed; the team can record technical references separately.
Keep important messages available long enough to understand and act on. Relevant changes also need suitable notification for assistive technology, which the team implements.
Match success to the actual result
“Booking request received” and “Appointment confirmed” make different promises. If staff still need to respond, explain the actual next step and response arrangements. A success screen establishes only that the interface reached that state; real receipt or storage still needs verification.
After an inquiry times out, the original request might or might not have arrived. The team needs suitable confirmation and retry behavior to avoid both false success and repeated duplicate requests.
You supply business promises, alternative contact methods, and response arrangements. The team handles state changes, data outcomes, and recovery. See inquiries and booking forms and the wider acceptance guide .
Our product and UX design service can cover these states in the agreed browser prototype. Real data handling, delivery, and recovery behavior are identified separately for implementation and testing.