The conversation stays intact when a person takes over.
The same inbound thread remains available in the team inbox with its message history and contact context. A teammate can review the answers already collected and continue from the point where the configured workflow handed over.
Collect the useful facts before the handoff.
Use structured questions, buttons, lists, and WhatsApp Flow forms to collect the requirement, booking choice, order reference, or reason for contact. Those messages remain in the thread for the teammate to inspect.
Make ownership visible to the whole team.
Assign the conversation, change its status, and use internal notes for information the customer should not see. Roles and instance grants keep workspace access scoped to the people who need it.
Status, notes, and audit trail.
Conversations carry a status (open, pending, resolved) and a thread of internal notes the customer never sees. Notes are timestamped, attributed, and searchable. Every reply, status change, and assignment is logged — if a customer complaint reaches you in two months, you can reconstruct exactly what happened.
Unmatched inbound messages still reach a person.
When no published workflow or approved AI action can handle the message safely, Waaru routes it to the human inbox instead of guessing or silently discarding the conversation.