A handover is an action, not a notification

A notification can be easy to ignore. A real handover identifies the conversation, preserves its context and tells a particular person what they are responsible for doing next. Without those elements, the team can assume that somebody else replied, while the customer sees no progress.

This is especially important when an assistant is involved. The assistant may correctly identify that somebody wants a quote, but it cannot turn that recognition into a quote without an owner, a workflow and the right commercial judgement. The system should make the human responsibility visible rather than hiding it behind automation.

What we routed to people

In our WhatsApp assistant testing, product questions, booking requests and quote requests triggered human-follow-up paths. We added monitoring emails and handover alerts so the conversations became visible outside the chat itself. The record could include contact details, reply status, interest and the intended follow-up.

For technical, custom or payment-intent questions, Muzi was looped in. That does not mean one person should own every type of query in every business. It demonstrates the design question that each business must answer: which kinds of customer decision need which person, and what information must they receive before they can act?

A four-step ownership framework

Step 1: classify the next action, not just the topic. ‘Needs quote’, ‘needs booking confirmation’ and ‘needs technical answer’ are more useful than a vague ‘customer query’.

Step 2: name the responsible person or role for each action. If the responsible person is unavailable, define a backup rather than leaving the alert in a group chat.

Step 3: include the minimum context: what the customer asked, their contact detail, any stated location or timing, and what the assistant has already said.

Step 4: record the outcome. The team needs to know whether the quote was prepared, the booking was confirmed, the question was answered or more information was requested.

A South African WhatsApp example

In a South African business where customer communication happens mostly through WhatsApp, a shared group chat can look like a system while still leaving work unowned. Consider a Cape Town supplier that receives a request for a custom product, a delivery location and a price question after hours. The assistant can capture the enquiry, but a named sales or operations person must decide stock, delivery conditions and the actual quote.

The useful handover is an alert with context and an accountable owner, not a flood of screenshots sent to an informal group.

Ownership does not mean promising instant replies

Giving an alert a named owner is not a promise that every customer will receive an immediate answer. Staff may be off duty, a quote may require a supplier check, or the question may need a technical decision. The point is to make the delay visible and intentional rather than accidental.

Avoid claiming a universal response time unless the business can support it. Also avoid routing every ordinary question to a senior person. Clear categories protect the team from alert fatigue while reserving human attention for the conversations where it matters.

Build the ownership table before launch

Create a small table with three columns: customer event, named owner and expected next action. For example: quote request—sales owner—prepare or clarify quote; booking request—service owner—confirm time or ask for availability detail; technical question—technical owner—provide the approved answer. Keep the table visible to everyone who receives alerts.

Then test it with a few dummy WhatsApp conversations. Check whether the owner receives enough context and whether a backup person knows what to do. If the workflow depends on everyone remembering an unwritten rule, it is not ready for a customer-facing assistant.

Name the person before you add the alert

The next action for any AI assistant project is simple: list the customer events that need human attention and put a responsible name or role beside each one. Add the context that person needs, then agree how the outcome gets recorded.

The assistant can make handovers easier to notice. Only a clear owner makes them dependable.