How should AI be connected to a messaging channel like WhatsApp?

Messaging differs from email in ways that matter operationally. Replies are expected quickly, so a delay reads as being ignored. Messages arrive in a personal space, so the tolerance for irrelevance is much lower. Threads are short and contextual, so a message that ignores what was said two lines earlier is conspicuous. And the platforms impose their own rules about what may be sent, when, and after what kind of consent, which are conditions of access rather than best practice.

The connection should be through the official business channel. Running a business conversation through a personal account creates three problems: the history belongs to a person rather than to the business, the platform's rules for business messaging do not apply in the way anyone assumes, and there is no route to hand the conversation to a colleague. This is a decision worth making before volume makes it expensive to change.

The most useful applications are the same ones that work in email and they suit the channel better. Acknowledging receipt with a stated response time. Confirming an appointment. Answering a status question from a record. Collecting the details needed to open a job. Each of these is short, factual and assembled from things you already know, which is exactly what fits both the channel and the constraints on automatic sending.

The handover to a person needs to be explicit and easy to trigger. A customer who asks something the system cannot handle should reach a human quickly and know that they have, and the common failure is a loop where the system keeps answering variations of the wrong thing. A plain route out — a phrase that always escalates, a stated response time, a visible acknowledgement that a person is now involved — prevents the frustration that otherwise gets attributed to the business rather than to the tool.

Timing needs a rule that a message channel makes more consequential than email does. A message at eleven at night reads differently from an email at eleven at night, and an automated one reads worse because nobody was working. Holding non-urgent outbound messages to working hours costs nothing and avoids the impression that most damages the relationship.

Finally, keep the conversation history where the business can see it. A thread that lives only in the channel is invisible to whoever picks up the customer next, which reproduces exactly the problem the connection was meant to solve. Writing the exchange into the customer record, or at least a summary with a link, is what makes the channel part of the business rather than a separate place things happen.