Let the workflow collect routine details, then send the conversation to your team when a person needs to decide or help. The customer stays in the same WhatsApp thread. Your teammate can read the history before replying.
In one line
WhatsApp human-in-the-loop means automation handles the repeatable steps and a person takes over for judgement-heavy work. Waaru keeps the conversation, contact, assignment, status, and internal notes in the shared inbox.
Platform free. AI features are paid separately.
The problem
A customer should not have to repeat an enquiry because the workflow and the support desk live in different places. The thread, collected answers, current status, and assigned owner need to remain visible together.
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.
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.
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.
Use open, pending, and resolved statuses to show what still needs attention. Add internal notes for decisions or details the next teammate needs. Keep those notes out of the customer-facing reply.
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.
It is an operating pattern where configured automation handles repeatable steps and a person takes over for decisions or exceptions. The customer remains in the same WhatsApp conversation.
The conversation remains in the shared inbox with its message history, contact context, assignment, status, and any internal notes already added by the team.
Add an explicit handoff step to a published workflow, use a configured fallback path, or let an unmatched inbound message enter the human inbox.
Yes. Routing rules support intent, tag, VIP segment, language, business hours, and team. Choose who should receive each type of request.
Yes. AI handoff can include a concise summary, and an approved human resolution can be stored as workspace-scoped context for a similar future intent. The team can inspect, edit, or delete that resolution.
Yes. Teammates use the shared inbox with assignments, conversation status, and internal notes that are not sent to the customer.
The runtime enforces workspace and instance isolation, scoped permissions, encrypted provider credentials, and private environment-specific media storage. Ask Waaru for the current DPA and deployment details for your review.
Public signup is open. The platform is free. AI features are paid separately. There is no subscription, trial, seat, or paid-plan access gate.
Ready to ship a WhatsApp flow that doesn't break?
Public signup is open. The platform is free. AI features are paid separately.
