Running WhatsApp broadcasts without landing in Meta's spam filter comes down to three disciplines: clean subscriber data, correctly configured templates, and disciplined send pacing. Retail and trade counter businesses that get this right turn WhatsApp into a reliable re-engagement channel; those that treat it like a bulk email blast tend to trigger account restrictions within weeks. Stitch, the WhatsApp business communication platform, works with retail and trade counter clients on exactly this problem, and this guide sets out the operational steps that keep a WhatsApp Business Account (WABA) healthy while still reaching customers at scale.
Before diving into the steps, it's worth understanding why this is harder than it looks: Meta's restrictions aren't purely about volume, they're about how recipients respond to what you send.
Before running a bulk broadcast campaign, make sure you have:
Bulk import failures are one of the most common causes of botched campaigns, and they usually come down to phone number formatting. Excel frequently strips the plus sign from international numbers or converts them into decimals, which breaks the import entirely, particularly with UK numbers starting with +44 or 447. To avoid this:
Getting this step right isn't just an administrative convenience — a properly formatted, verified contact list is the foundation everything else in this guide depends on, because messy data is what leads to bounced sends, failed personalization, and ultimately, spam reports.
Every broadcast to a contact outside the 24-hour customer response window must use a Meta-approved template. Templates that don't follow Meta's formatting rules get rejected or delayed, so it pays to get the structure right the first time.
Template naming and structure requirements:
- Names must be lowercase, use numbers and underscores only, and be a minimum of five characters
- Variable fields cannot appear at the start or end of a template
- Templates support text-only formats or text combined with one media type — image, PDF document, or video
- Variable fields use numbered curly brackets (e.g., {{1}}) to personalize content such as customer name or offer details
Template classification affects cost. Meta classifies templates as either utility (around 1.6p per message) or marketing (around 3.8p per message), based on the content of the message itself. Wording changes can shift a template from one classification to the other, so it's worth testing phrasing if cost matters to your campaign economics.
Approval timing: most templates are approved by Meta within 5 to 10 minutes, though approval can occasionally take up to 24 hours. Build this into your campaign planning rather than assuming instant turnaround.
With your template structure sorted, the next question is how to make it actually perform once it lands in a customer's inbox.
Quick-reply buttons increase engagement and give customers a low-friction way to respond, but they carry a formatting constraint: each button is limited to roughly 27 characters and cannot include emojis. Typical options include "Yes," "No," and critically, "Stop."
The "Stop" button is not optional in any meaningful sense. It is the single most important control against being reported or blocked by recipients. When a contact sends "stop" (case-insensitive) or taps a quick-reply button labelled "stop," they are automatically unsubscribed and cannot be messaged again. This keyword is hardcoded into the platform's unsubscribe logic — it isn't something a broadcast admin needs to configure manually.
A few operational notes on managing this:
Static call-to-action URLs can also be embedded in templates, for example a "Register here" or "Book a demo" button, which is useful for driving traffic without relying solely on quick replies.
Untargeted, one-size-fits-all broadcasts are more likely to generate complaints than segmented ones. Tags let you filter your contact list using logical operators — AND, OR, IS NOT — to build precise audiences before you send. A retail or trade counter example: tagging contacts as "opportunity" or by campaign ("valuation_chase_Jul26"-style naming) lets you target only the customers relevant to a specific offer, rather than blasting the entire list.
Templates themselves can also be configured to display only for pre-subscribers (contacts who haven't yet messaged you), only for subscribers (contacts who have), or both. This distinction matters for compliance, since pre-subscriber broadcasts carry higher scrutiny from Meta than messages to customers who have already engaged. It is also vital to understand how UK GDPR and Data Residency Rules apply to WhatsApp business messaging when handling subscriber data for these campaigns.
Once your audience is properly segmented, the final and most consequential decision is how fast you actually send to them.
This is the step most likely to get an account restricted if skipped. Meta's spam detection isn't purely volume-based — it responds heavily to concentrated blocks and reports arriving in a short window. Sending a large batch all at once, even to a list you believe is engaged, concentrates that risk.
Recommended pacing:
Meta evaluates account quality based on engagement levels and organic inbound traffic, and this quality score is what determines whether your daily sending limit scales from 1,000 messages/day up toward 10,000+. In other words, pacing isn't just about avoiding a ban — disciplined sending is what earns you a higher ceiling over time.
Broadcast sends are only one side of account health. Driving organic inbound conversations — customers messaging you first — signals to Meta that your account is legitimate and actively engaged, which supports your overall sending reputation. Practical ways to generate this:
Having multiple team members send templates, rather than concentrating all outbound activity on one user, also helps spread account activity and reduces the risk of a single user's sending pattern being flagged. Many businesses find that how trade counters use WhatsApp for stock availability and order enquiries provides the perfect balance of organic utility and marketing reach.
A few additional principles worth building into your standard operating procedure:
My bulk import keeps failing or numbers look wrong. This is almost always Excel reformatting phone numbers on save. Switch to a dedicated CSV tool, remove the leading "+" where the platform expects a bare country code, and verify any numbers with unusual prefixes manually.
My template was rejected or reclassified as marketing when I expected utility. Meta classifies templates based on content and wording, not intent, so review the message copy — small wording changes can shift classification and cost.
I'm seeing a spike in reports or blocks after a broadcast. This usually indicates the batch was too large, too cold, or lacked a clear opt-out option. Reduce batch size to 30-40 contacts (or as low as 10 for pre-subscribers), confirm every template includes a "Stop" quick reply, and slow the pace of subsequent sends.
A contact says they never received a message after unsubscribing then re-engaging. Resubscription only happens when the contact messages the business again — it isn't automatic, and re-adding them manually as a fresh contact risks resetting their subscription status incorrectly.
Compliant WhatsApp broadcast marketing rests on data hygiene, template correctness, and pacing discipline working together, not any single fix. Clean, properly formatted contact lists prevent import failures and reduce downstream risk; templates built to Meta's structural rules with a working "Stop" option keep recipients in control and your account out of trouble; and batching sends over days rather than hours protects your account's standing while it earns the right to scale. Retail and trade counter businesses that build these three habits into their standard broadcast process are the ones who keep WhatsApp as a durable channel rather than losing it to a preventable spam block.
