The most common misunderstanding: people expect to download something.<\/p>\n
There is no app.<\/strong> The WhatsApp Business Platform is an interface your systems talk to. Messages are sent and received by software, not by a person opening a phone.<\/p>\n Which means you need one of two things:<\/strong><\/p>\n A provider’s interface.<\/strong> Most businesses use this \u2014 a web application where agents see conversations, plus tools to manage templates and contacts.<\/p>\n Your own integration.<\/strong> You connect it to your ERP, CRM or helpdesk directly.<\/p>\n Most companies use both: a provider interface for agents, and an integration for automated messages from their systems.<\/p>\n Five things you need. Getting them in the right order saves weeks.<\/p>\n A Meta Business account.<\/strong> The container for everything.<\/p>\n Business verification.<\/strong> Meta confirms your business is real, using documents. This is the long pole<\/strong> \u2014 days to weeks depending on your paperwork.<\/p>\n A phone number.<\/strong> Not already registered on WhatsApp. Once used here, it cannot be used in the normal app.<\/p>\n A Business Solution Provider.<\/strong> Your route in, plus interface, support and billing.<\/p>\n Approved templates.<\/strong> Before you can message anyone outside an open conversation.<\/p>\n FIGURE 1: THE ORDER TO SET THINGS UP<\/p>\n Meta Business account<\/p>\n Business verification<\/p>\n Number and provider<\/p>\n Templates approved<\/p>\n They differ more than the marketing suggests. Six questions.<\/p>\n What does the agent interface look like?<\/strong> Your team will live in it. Ask for a demonstration with real conversations, not a slide.<\/p>\n Does it integrate with your systems?<\/strong> Ready-made connectors for your ERP or helpdesk, or an API you would build against.<\/p>\n How is pricing structured?<\/strong> Meta charges per conversation or message. Providers add their own fee \u2014 per user, per month, per message, or a mix. Model the total on your expected volume<\/strong>, not the headline number.<\/p>\n How do templates get managed?<\/strong> Some providers make submission and tracking easy. Some do not.<\/p>\n What happens when something breaks?<\/strong> Support hours, response times, and whether you reach a person.<\/p>\n Can you export your data?<\/strong> Conversation history and contacts. Ask before you commit, not when you are leaving.<\/p>\n It governs the whole design, so it is worth stating precisely.<\/p>\n A customer messages you.<\/strong> A service window opens \u2014 commonly 24 hours. Inside it, you reply freely with any content.<\/p>\n The window closes.<\/strong> Now you can only send an approved template.<\/p>\n Two design consequences:<\/strong><\/p>\n Support works naturally.<\/strong> The customer starts it, so you are always inside a window.<\/p>\n Proactive messaging needs templates.<\/strong> Every notification you initiate is a template, approved in advance.<\/p>\n A pattern worth knowing:<\/strong> a template can reopen the conversation. Send an approved order update, the customer replies, and now you have a service window for a normal exchange.<\/p>\n FIGURE 2: DESIGNING AROUND THE WINDOW<\/p>\n Works naturally<\/p>\n Needs a template<\/p>\n Three things worth knowing before you write any.<\/p>\n Variables are positional.<\/strong> The template has placeholders filled at send time \u2014 a name, an order number, a date. The surrounding text is fixed.<\/p>\n Categories matter.<\/strong> Utility, marketing and authentication have different rules and different costs. Submitting a promotional message as utility gets it rejected<\/strong>, and that is the most common rejection reason.<\/p>\n Changes need re-approval.<\/strong> Editing a template means submitting it again. Design them to last \u2014 put anything variable in a variable rather than in the fixed text.<\/p>\n Meta scores your number based on how recipients react \u2014 blocks, reports, and whether messages get read.<\/p>\n Why it matters:<\/strong> a falling rating reduces your messaging limits. Keep falling and the number can be restricted.<\/p>\n What damages it:<\/strong><\/p>\n What protects it:<\/strong><\/p>\n Check it regularly.<\/strong> It falls before you lose access, which makes it a warning you can act on.<\/p>\n The point of the platform, and where the value is.<\/p>\n Outbound.<\/strong> Your ERP sends an order confirmation. Your booking system sends a reminder. Your accounting system sends an invoice link.<\/p>\n Inbound.<\/strong> A customer’s reply creates or updates a support ticket, with their history attached.<\/p>\n What makes this work well:<\/strong> the customer record in your system and the WhatsApp contact need to be linked. Match on phone number, and store it in a consistent format<\/strong> \u2014 country code included, no spaces or punctuation.<\/p>\n Inconsistent phone number formatting is the single most common cause of messages not matching to the right customer.<\/p>\n FIGURE 3: FOUR THINGS THAT DECIDE WHETHER IT WORKS<\/p>\n Start verification early<\/p>\n Consistent phone formats<\/p>\n Templates written as utility<\/p>\n Somebody watching quality rating<\/p>\n Three layers, and companies routinely budget for only one.<\/p>\n Meta’s charges<\/strong>, per conversation or message, varying by category and country.<\/p>\n Your provider’s fee<\/strong>, structured differently by provider.<\/p>\n Your integration work<\/strong>, if you connect it to your systems.<\/p>\n Check current Meta pricing with your provider.<\/strong> It has changed more than once and any article’s figures go stale.<\/p>\n Verification started too late.<\/strong> The project waits on paperwork.<\/p>\n A number already on WhatsApp.<\/strong> It has to be freed first, or you use a different one.<\/p>\n Templates written as marketing.<\/strong> Rejected, rewritten, delayed.<\/p>\n Inconsistent phone formats.<\/strong> Messages not matching customer records.<\/p>\n No opt-out process.<\/strong> Legal and reputation risk together.<\/p>\n Nobody watching the quality rating.<\/strong> The warning goes unheard.<\/p>\n The Business Platform is an interface, not an app. You need a Meta account, business verification, a clean phone number, a provider, and approved templates.<\/p>\n Start verification first<\/strong> \u2014 everything waits on it.<\/p>\n The service window governs the design.<\/strong> Inside it, talk freely. Outside it, use a template.<\/p>\n Store phone numbers consistently<\/strong>, protect your quality rating, and check current pricing rather than trusting any article.<\/p>\n Setting up WhatsApp for customer notifications?<\/p>\n Get in touch. We will start with verification and your phone number data, because those two hold up more projects than anything else.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":" It is not an app The most common misunderstanding: people expect to download something. There is no app. The WhatsApp Business Platform is an interface your systems talk to. Messages are sent and received by software, not by a person opening a phone. Which means you need one of two things: A provider’s interface. Most […]<\/p>\n","protected":false},"author":3,"featured_media":9390,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[],"class_list":["post-9389","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-automation"],"yoast_head":"\nThe pieces<\/h2>\n
\n
\n
\n
\n
Choosing a provider<\/h2>\n
The service window, again<\/h2>\n
\n
\n
Templates in practice<\/h2>\n
Quality rating<\/h2>\n
\n
\n
Connecting it to your systems<\/h2>\n
\n
\n
\n
\n
What it costs<\/h2>\n
What usually goes wrong<\/h2>\n
The short version<\/h2>\n