Packed, awaiting dispatch
- Order
- 1042
- Customer
- Maya Chen
- Source
- Order record
- Next step
- Await dispatch
Answer from the order record. Keep the next step in the same conversation.
Carry a customer’s question into the right business action. Keep replies, service-window rules and human ownership connected to the same task.
Choose a reply and follow the same order through the conversation.
Answer from the order record. Keep the next step in the same conversation.
Pass the order and the question to your team. The customer keeps their place.
Keep customer replies connected to their task.
Preserve the supplied phone or business-scoped identity and explicit reply identifiers. A contact card can describe another person; outgoing metadata does not automatically return in an inbound reply.
The customer-service window lasts 24 hours from customer activity and resets on new messages. Use supported service content while it is open; use an eligible approved template to restart a closed exchange.
A booking or order change succeeds when its owning system confirms it. Keep pending and failed actions visible, and transfer the goal and attempted steps when a person takes over.
Organize teams in workspaces, control API access, and trace changes through audit logs.