The pattern is familiar. A business connects WhatsApp, sends templates, and calls it automation. Six weeks later, a member of staff is answering every thread by hand, because the customer replied with something the flow did not expect. The channel was treated as an outbound pipe when it is the place the transaction wants to happen.
The link is where you lose people
A message that ends in a link asks the customer to leave a conversation they are already in, open a browser, and possibly sign in. Every one of those is a step where people stop. When the same action can be completed in the thread — pick one of three times, confirm the address, pay the deposit — completion goes up for the obvious reason that nothing was asked of them beyond replying.
Design the reply, not the send
Templates are the easy half. The work is in what arrives back: dialect, mixed script, a voice note, a photograph of a receipt, an answer to a question you asked two days ago. A flow that only understands button presses will hand off to a human on first contact with a real customer. Reading free text, restating the intent in plain words, and confirming before acting is what keeps a thread automated without making it feel automated.
One ledger or you will reconcile forever
The most consequential decision is whether a message that changes state writes to the same records as everything else. If WhatsApp gets its own store, you now have two versions of every booking and a person whose job is to keep them agreeing. In the club platform we built, a booking made in a thread is the same record the member's app lists and the coach's roster prints, tagged with the channel it came from. That tag is useful. A second database is not.
Staff are the underrated half
Everyone builds the customer side. Field and floor staff will use WhatsApp long before they open an app, and their journeys are simpler and higher volume: today's roster, marking attendance, accepting cover, confirming a collection. Two of the five interfaces in our club platform are staff on WhatsApp, and they are the ones an operator reacts to in a demonstration, because that is the part they know is hard to get people to adopt.
The test for any WhatsApp project is one question: can the customer finish, without leaving the thread? If not, it is a notification service.