Support by email is slow and formal. Support by phone means waiting.<\/p>\n
Messaging is neither. The customer sends a question, gets on with their day, and comes back to the reply.<\/p>\n
And it is asynchronous for you too.<\/strong> One agent can hold several conversations at once, which a phone call does not allow.<\/p>\n The service window works in your favour here.<\/strong> The customer starts the conversation, so a window is open and you can reply freely for a period \u2014 usually 24 hours. No templates needed.<\/p>\n Three things. Without them, WhatsApp support becomes a worse version of a shared inbox.<\/p>\n Not a phone somebody carries. If support lives in an app on one person’s device, it disappears when they are on leave and there is no record of what was said.<\/p>\n Conversations should create or update records<\/strong> in your helpdesk or ERP.<\/p>\n Their orders, their invoices, their deliveries, their previous conversations.<\/p>\n Without this, agents ask customers to repeat information the company already has<\/strong> \u2014 which is the single most irritating thing in support.<\/p>\n WhatsApp creates an expectation of speed. A message sitting for two days is worse than an email sitting for two days, because the channel implies immediacy.<\/p>\n Decide who watches it and during what hours<\/strong>, and say so to customers.<\/p>\n FIGURE 1: BEFORE YOU OPEN THE CHANNEL<\/p>\n Conversations reach a system<\/p>\n Agents see the customer<\/p>\n Someone owns the queue<\/p>\n Hours stated publicly<\/p>\n The most useful thing you can do, and it costs nothing.<\/p>\n State your hours.<\/strong> In your business profile, and in the first automated reply.<\/p>\n Give a realistic response time.<\/strong> “We reply within two hours during business hours” is better than saying nothing and replying in three.<\/p>\n Acknowledge out of hours.<\/strong> A short automated message saying when somebody will reply.<\/p>\n Customers accept limits. They do not accept silence.<\/strong><\/p>\n Four things, in order of how safely you can adopt them.<\/p>\n Context for the agent.<\/strong> Assemble the customer’s history so the agent sees it immediately. No customer-facing risk at all<\/strong>, and it makes every reply better.<\/p>\n Suggested replies.<\/strong> Drafted from the question and the customer’s record. The agent edits and sends.<\/p>\n Routing.<\/strong> Reading the message and sending it to the right team with a summary attached.<\/p>\n A narrow bot<\/strong> for a defined set of factual questions, with a one-message escape to a person.<\/p>\n Start with the first.<\/strong> It improves your team without the customer noticing anything.<\/p>\n Anything unread going to a customer.<\/strong> A confident wrong answer sent automatically is worse than a slow correct one.<\/p>\n A bot that will not hand over.<\/strong> On WhatsApp this is more damaging than on a website, because the channel feels personal.<\/p>\n Pretending a bot is a person.<\/strong> People work it out.<\/p>\n Anything involving money.<\/strong> Refunds, credits, disputes. A person decides.<\/p>\n FIGURE 2: WHERE AUTOMATION HELPS AND WHERE IT HURTS<\/p>\n Helps<\/p>\n Hurts<\/p>\n WhatsApp usually increases contact volume. People message who would not have phoned or emailed.<\/p>\n That is not necessarily bad<\/strong> \u2014 it can mean problems surfacing earlier. But plan for it.<\/p>\n Three things that help:<\/strong><\/p>\n Templates for common replies.<\/strong> Saved responses agents can send and adapt.<\/p>\n A knowledge base.<\/strong> Every question answered publicly is one that arrives less often.<\/p>\n Clear hours.<\/strong> Volume outside working hours is manageable if expectations are set.<\/p>\n Conversations span time. A customer messages Monday, replies Wednesday, and a different agent picks it up.<\/p>\n Three things this needs:<\/strong><\/p>\n The full history visible.<\/strong> Not just this conversation \u2014 their orders and previous tickets too.<\/p>\n Notes from the previous agent.<\/strong> What was agreed, what is pending.<\/p>\n A clear status.<\/strong> Waiting on customer, waiting on us, resolved.<\/p>\n “Waiting on customer” matters more than it sounds.<\/strong> Without it, conversations blocked on a customer reply look like conversations your team is ignoring \u2014 and your response time reports become meaningless.<\/p>\n First response time.<\/strong> What customers feel most.<\/p>\n Resolution time.<\/strong> Whether conversations actually close.<\/p>\n Reopened conversations.<\/strong> The honest test.<\/strong> If this rises, you are answering faster and worse.<\/p>\n Volume by topic.<\/strong> What people actually contact you about. The most actionable number here, and the least used.<\/p>\n Blocks and reports.<\/strong> Threatens the channel itself.<\/p>\n Watch reopened conversations closely.<\/strong> Fast wrong answers look excellent on a response time report and cost you customers.<\/p>\n FIGURE 3: THE NUMBERS THAT MATTER<\/p>\n First response time<\/p>\n Reopened conversations<\/p>\n Volume by topic<\/p>\n Support on somebody’s phone.<\/strong> No record, no handover, no continuity.<\/p>\n Agents without customer context.<\/strong> Asking people to repeat what you already know.<\/p>\n No status for waiting-on-customer.<\/strong> Response metrics become meaningless.<\/p>\n Unclear hours.<\/strong> Customers expecting replies at midnight.<\/p>\n Volume without capacity.<\/strong> Opening the channel and not staffing it.<\/p>\n A bot deployed too early.<\/strong> Before anybody knew what customers actually ask.<\/p>\n Weeks 1\u20134.<\/strong> Manual only. Conversations reaching your helpdesk, agents with full context. Record what people ask.<\/p>\n Week 5.<\/strong> Add agent-side automation \u2014 summaries and suggested replies.<\/p>\n Week 6.<\/strong> Add routing.<\/p>\n Week 8.<\/strong> Review reopened conversations and volume by topic.<\/p>\n Week 10.<\/strong> Consider a narrow bot for the five most common questions.<\/p>\n The first four weeks are not wasted time.<\/strong> They tell you what to automate, which is not what you would have guessed.<\/p>\n WhatsApp support works because customers prefer messaging, and because the service window means no templates are needed once they contact you.<\/p>\n Conversations must reach a system, agents must see the customer, and somebody must own the queue.<\/strong> Without those three it is a shared inbox with a nicer app.<\/p>\n State your hours.<\/strong> Customers accept limits and not silence.<\/p>\n Start with agent-side automation<\/strong>, and watch reopened conversations rather than response time alone.<\/p>\n Customers messaging you and nobody sure who is answering?<\/p>\n Get in touch. We connect WhatsApp to your helpdesk so conversations become records \u2014 and agents see the customer before they reply.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":" Why customers like it Support by email is slow and formal. Support by phone means waiting. Messaging is neither. The customer sends a question, gets on with their day, and comes back to the reply. And it is asynchronous for you too. One agent can hold several conversations at once, which a phone call does […]<\/p>\n","protected":false},"author":3,"featured_media":9405,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[],"class_list":["post-9404","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-automation"],"yoast_head":"\nWhat has to be in place first<\/h2>\n
Conversations must reach a system<\/h3>\n
Agents must see who they are talking to<\/h3>\n
Somebody must be responsible<\/h3>\n
\n
\n
\n
\n
Setting expectations<\/h2>\n
Where automation belongs<\/h2>\n
Where automation does not belong<\/h2>\n
\n
\n
Managing the volume<\/h2>\n
The handover problem<\/h2>\n
Measuring it<\/h2>\n
\n
\n
\n
What goes wrong<\/h2>\n
A sensible rollout<\/h2>\n
The short version<\/h2>\n