Core onboarding · 2 of 6
Confirm the first workflow.
A first web app needs one customer path that works from start to finish. The intake response makes that path visible before any screen is generated.
Read the flow before the options
For a workshop service, the core flow might be: discover an experience, choose a date, make a clearly labelled test payment, then check My Bookings. For a bookstore, it may be browse, open a book, add it to cart, check out, then revisit purchases.
Customer startsFind the right item, service, or person.
Main actionBook, order, request, publish, or approve.
Saved resultOrders, bookings, history, or a personal area.
Operator viewConfirm, change status, and keep records moving.
Use the editable draft
The response separates the core flow from optional choices. Select Use and edit this draft when the direction is close. The message is copied into the conversation box, where you can remove an option, add a rule, or simply send it unchanged with “Make it now.”
Choose only the decisions that matter now
- Do customers need to sign in before the main action?
- Is payment a test boundary or a live operating requirement?
- Does someone need a staff workspace to review and change status?