Receiving a message does not always mean an order has been accepted. We map the steps between product selection, staff review and the business's agreed confirmation so the interface matches the actual commercial process.
Give the request a useful identity
The scope can include a stable reference, selected items, customer contact details and staff assignment. Customers see what has been received and what remains to be confirmed. Staff can identify incomplete details without recreating the order in a separate conversation.
Repeated attempts and interrupted sessions need explicit behaviour. We discuss how a customer can recognise an existing request and how staff distinguish it from a genuinely new one.
Review exceptions as well as success
Use fictional examples for a missing variant, changed quantity and delayed provider response. Acceptance should show who resolves each case and how the current position remains understandable.