Stop Losing WhatsApp Sales While You Sleep: A Plain-English Troubleshooting Guide

More and more South African businesses are selling entirely on WhatsApp — no website, no checkout page, just a chat. Ads send buyers straight into a conversation, an automated bot qualifies them, and a payment link closes the deal. Done right, it runs 24/7 and never sleeps.

The problem? When it breaks, it breaks silently. Your dashboard still shows a reassuring green "Connected" light while leads quietly disappear, your product catalogue shows up empty, and customers pay but never get a confirmation. No error, no alert — just fewer sales.

This guide walks through the four most common silent failures, in plain English, so you (or whoever runs your tech) can spot the leak and plug it.

Why "Connected" doesn't mean "Working"

An automated WhatsApp funnel is a chain of moving parts: the ad, the WhatsApp Business API, the bot that asks qualifying questions, the product catalogue, and the payment link. A green status only tells you the first link is alive. Any of the links after it can fail without changing that light.

Below are the four symptoms to watch for — and what to actually do about each one.

Symptom 1: Your messages say "Sent" but never arrive

Your system reports questions as "Sent," but replies have dried up to zero.

What's really happening: "Sent" only means WhatsApp accepted your message — not that it reached the customer's phone. WhatsApp can accept it and then quietly block delivery.

The usual culprits:

• Your number's quality rating dropped. WhatsApp watches how often people block or report you. If your rating slips from green to yellow or red, it throttles or blocks your outgoing messages.
• Wrong message template. Outside the 24-hour reply window, you can only send pre-approved templates. Sending a promo using a template approved only for order updates gets blocked.
• Daily limits. WhatsApp caps how many marketing messages a person can receive in a day across all businesses. Hit the cap and your message just won't land.

What to do:

1. Check your number's quality rating in WhatsApp Manager. If it's red, pause any bulk campaigns immediately.
2. Make sure every automated message points to an active, approved template — and that you're only sending marketing to people who opted in.
3. Have your developer check the delivery logs (the "webhook") for whether messages actually move from sent to delivered, instead of trusting the dashboard.

Symptom 2: The bot ignores people

A customer clicks your ad or taps a button, and… nothing. The bot goes quiet.

What's really happening: When someone taps a button, WhatsApp tries to notify your automation system. If that handoff fails, the customer's tap vanishes into thin air.

Common causes:

• The app is in "test mode." If the underlying Meta app is set to Development rather than Live, only your own test numbers get replies. Real customers are ignored.
• Your server is blocking WhatsApp. Security firewalls on cheaper hosting often mistake WhatsApp's rapid messages for an attack and drop them.
• Processing delays. Occasionally WhatsApp itself queues these notifications and delivers them minutes or hours late.

What to do:

1. Confirm the Meta app is set to Live, with business verification complete and a privacy policy linked.
2. Ask your developer to test the connection with a tool like webhook.site. If messages show up there but not in your system, the problem is your hosting/firewall — not WhatsApp.
3. Make sure your server replies to WhatsApp quickly. Slow replies trigger retries, which can spam customers with duplicate messages.

Symptom 3: Your product catalogue is empty or wrong

A customer taps the shopping icon and sees nothing — or sees old prices that don't match your stock.

What's really happening: To show products in WhatsApp without a website, your inventory has to sync to Meta's Commerce Manager. That sync runs on a connection that quietly expires or fails validation.

Common causes:

• An expired login token. Many store-to-WhatsApp connections use tokens that expire every 60 days. When one lapses, the sync stops with no warning.
• Missing importer details. Some regions require specific business/importer info before WhatsApp will display a catalogue. Leave it blank and the whole catalogue is hidden.
• Your host blocks the feed. Some hosting providers block the exact files WhatsApp needs to pull your product data.

What to do:

1. Re-authorise the connection between your store and Meta, and switch to a long-lived token where possible.
2. Fill in the required importer/business details in your sync settings completely.
3. In Meta Business Manager, confirm your catalogue exists and that your integration has full permission to manage it.

Symptom 4: Customers pay, but get no confirmation

Someone completes a payment through your link — but the automated "order confirmed" message never fires.

What's really happening: When a payment succeeds, your payment provider (like Stripe or Paystack) is supposed to ping your system to trigger the confirmation. If that ping gets intercepted, the order just hangs.

Common causes:

• Caching gets in the way. Caching tools or a CDN like Cloudflare can intercept the payment notification and reply "all good" without passing it to your system. The payment provider thinks it succeeded; your app never hears about it.
• One-off vs subscription mismatch. Some setups are coded only for subscriptions. A single product purchase makes the code look for a subscription that doesn't exist, and it crashes.
• Firewall blocks the notification. If your payment provider's servers aren't whitelisted, your host may drop the message.

What to do:

1. In your payment provider's dashboard, open the webhooks section and look at the "Failed" tab. HTML or redirect responses are a dead giveaway that caching is intercepting things.
2. Exclude the payment-notification address from all caching and firewall challenges.
3. If you sell one-off products, make sure your code handles one-time payments, not just subscriptions.

Quick reference: common WhatsApp error codes

If your developer is digging into logs, these are the codes that come up most often.

Error	What it means	What to do
131048	Flagged for spam / sending too fast	Pause bulk sends, clean your list, confirm everyone opted in
131049	Recipient hasn't accepted WhatsApp's latest terms	Don't retry — reach them by SMS or email instead
131047	The 24-hour reply window has closed	Switch to an approved template message
131042	Billing problem on the WhatsApp account	Update payment details in WhatsApp Manager
190	Login token expired or revoked	Generate a new long-lived token
131009	Invalid value in the request (e.g. wrong catalogue ID)	Check the catalogue ID and message details against your settings

Five habits that keep the leaks closed

1. Track real delivery, not "sent." Set up an alert if your delivery rate drops below 90%, so you find out before your sales do.
2. Only message people who opted in. It's the single biggest factor in keeping your number healthy and out of spam jail.
3. Use long-lived tokens. Avoid the temporary developer tokens that expire and silently break everything.
4. Run real scheduled jobs. Don't rely on website traffic to trigger your automations — use proper server-side scheduling so payments and syncs process on time.
5. Always have a fallback. If WhatsApp delivery fails mid-sale, automatically follow up by SMS or email within a couple of minutes so you don't lose the customer.

---

A WhatsApp funnel that works is one of the cheapest, fastest sales engines a small business can run. But "set and forget" is a myth — these systems need someone watching the right signals, not just the green light.

If you'd rather not babysit webhooks and error codes, that's exactly what we do.