DEV Community: Wabbiyo

6 Bugs in WhatsApp Appointment Reminder Systems (and How to Fix Them)

Wabbiyo — Fri, 30 Oct 2026 11:28:41 +0000

Appointment reminders look like a cron job and a message. In production, these six bugs show up first.

Reminder after a cancellation
The patient cancelled, but the T-24h job still fires. Fix: unschedule pending jobs on every cancel or reschedule.
Wrong time zone
The appointment was stored in local time and the server runs UTC, so the reminder arrives at the wrong hour. Store timestamps with the time zone and convert once.
Duplicate reminders
The booking was edited twice and three jobs exist. Fix: one job per appointment per stage, keyed on appointment_id + stage.
Sent at 2 AM
A booking made late at night for an early slot triggers a T-2h reminder in the middle of the night. Add quiet hours and skip or shift those reminders.
Reply not linked to the booking
The patient taps “Reschedule”, but the webhook can’t tell which appointment it’s for. Put the appointment ID in the button payload.
Diagnosis in the message
“Reminder: your knee MRI follow-up…” is health information on a lock screen. Keep reminders generic: date, time, clinic, reference number.

Bonus for physiotherapy clinics: send the home exercise plan as a link after each session. It’s helpful for patients and a good reason for them to keep the chat open.

Wabbiyo handles reminders, reply buttons and rescheduling on the official WhatsApp API for WordPress sites. See the physiotherapy clinic setup, or wabbiyo.com.

6 Mistakes That Make Your WhatsApp Campaign Reports Wrong

Wabbiyo — Thu, 29 Oct 2026 05:35:06 +0000

If your WhatsApp campaign numbers look too good, or don’t match your sales, check for these six reporting mistakes.

Counting sends as success
sent only means Meta accepted the message. Use delivered as your base.
No campaign ID on orders
If you can’t tell which message led to an order, you can’t measure revenue per campaign. Store the campaign ID per message, then attribute orders by phone number and time window.
Ignoring failed statuses
Failures hide real problems: numbers not on WhatsApp, per-user marketing limits, paused templates. Group failures by error code after every campaign.
No opt-out tracking
“STOP” replies and blocks are the early warning before your number’s quality rating drops. Track them per campaign.
Changing the attribution window
7 days one month, 30 days the next, and the trend line becomes meaningless. Pick one and keep it.
Counting bot chats as sales
A chatbot conversation isn’t a conversion. Only count orders, bookings or payments.

Wabbiyo’s WhatsApp analytics for WordPress tracks delivered/read/reply rates and attributes WooCommerce revenue per campaign, flow and cart reminder: Click here to know more.

Thinking of Self-Hosting Your WhatsApp Integration? 6 Checks First

Wabbiyo — Wed, 28 Oct 2026 10:40:16 +0000

Self-hosting your WhatsApp Business API integration (for example, as a WordPress plugin) removes a SaaS layer, but your site now has to handle webhooks reliably. Check these six things first.

HTTPS on your site
Meta only delivers webhooks to HTTPS URLs with a valid certificate.
Cron / queue actually running
Broadcasts and scheduled reminders depend on background jobs. On low-traffic sites, WP-Cron may not fire on time, so set up a real server cron that hits wp-cron.php, or use Action Scheduler with a system cron.
Hosting accepts webhooks
Some security plugins, firewalls or “under construction” modes block inbound POST requests. Whitelist the webhook route and test it.
Backups include the chats
Check that your backup plugin includes custom tables, not just posts and media.
Plugin kept updated
Meta updates the Graph API versions. Keep the plugin current so you aren’t on a deprecated version.
PHP 8.1+
Modern plugins need it. Check under Tools → Site Health.

If all six are fine, self-hosting is usually smooth. If not, a SaaS platform may be easier.

We build Wabbiyo, a self-hosted WhatsApp plugin for WordPress. Comparison with SaaS options: Click here to know more

6 Hidden Costs in Your WhatsApp Business API Bill

Wabbiyo — Tue, 27 Oct 2026 11:49:56 +0000

If your WhatsApp API bill is higher than expected, one of these is usually why.

Per-message markup
Some platforms add a margin to every template message on top of Meta’s rate. At thousands of messages a month it adds up. Ask for the exact Meta rate and the platform rate separately.
Per-agent seat fees
The team grows from 3 to 8 agents and the bill doubles, without sending a single extra message.
Promotions billed as marketing
“Your order shipped! Use SAVE10 on your next order” isn’t a utility message anymore. Meta can recategorise it and charge the marketing rate. Keep utility templates clean.
Failed sends retried blindly
Retrying failed messages to numbers that aren’t on WhatsApp wastes effort, and resending templates that already delivered costs again. Check the status webhook before retrying.
Unsegmented broadcasts
Sending every promo to every contact means paying for messages to people who never buy, and more blocks, which hurt your number’s quality. Segment.
Paid chatbot or automation add-ons
The chatbot or flow builder you assumed was included is a separate monthly charge.

Quick win: reply fast. Replies inside the 24-hour customer service window are free, and utility templates sent while that window is open are free too.

Wabbiyo is a self-hosted WordPress plugin where you pay Meta directly with no markup and no per-message fees from us. Plans include agents, flows and broadcasts by tier: Click here to know more.

6 Mistakes in WhatsApp Chatbot Flows (and How to Fix Them)

Wabbiyo — Mon, 26 Oct 2026 10:00:36 +0000

Building WhatsApp flows is easy. Building ones customers actually finish is harder. These six mistakes cause most drop-offs.

Too many steps
Eight questions before anyone helps you feels like a phone menu. Keep qualification to three to five steps.
No way out to a human
If “agent” doesn’t break the flow at every step, customers get stuck and leave. Check for escape keywords before processing the step.
Free text where buttons fit
“Type your city” gets “chn”, “Madras” and “chennai 600017”. Use list messages for fixed choices and keep free text for genuinely open answers.
Answers not saved
The flow collects need, city and budget, then the agent asks again. Save every answer to the contact and show it in the inbox.
No timeout handling
The customer leaves mid-flow, comes back two days later, types “hi” and lands on step 4. Reset or resume deliberately after a timeout, and remember the 24-hour window for follow-ups.
Flow never updated
Products, prices and FAQs change, and the flow doesn’t. Review drop-off points monthly and fix the step where most people leave.

If you’d rather build flows visually inside WordPress, Wabbiyo’s flow builder covers buttons, lists, conditions, tags, webhooks and handoff: Click here to know more

6 Reasons Your WhatsApp Template Was Rejected (and the Fix for Each)

Wabbiyo — Sat, 24 Oct 2026 08:29:13 +0000

Your WhatsApp template came back REJECTED and the reason is one line. Here are the usual causes and fixes.

Variable at the start or end
{{1}}, your order is ready → Hi {{1}}, your order is ready.
Your code: {{1}} as the entire body → add context around it.
Too many variables
{{1}} {{2}} {{3}} {{4}} at {{5}} could say anything. Write real sentences and use only the variables you need.
Missing sample values
Every {{n}} needs an example in the example.body_text array, in the right order and count.
Wrong category
“Your order shipped! Use code SAVE10 next time” is not utility. Split it into two templates: a pure utility shipping update, and a separate marketing offer.
Misleading or vague text
Hi {{1}}, you have a surprise waiting gets rejected. Say what it is and who it’s from.
Duplicate content
Submitting the same body under a new name, or an existing template with tiny changes, can be rejected. Edit the existing template instead.

Debugging tip: subscribe to the message_template_status_update webhook and log the rejection reason for each template. Patterns show up quickly.

If you want pre-written templates and status tracking inside WordPress, Wabbiyo includes a template library on the official Cloud API: Click here to know more

6 Ways Click-to-WhatsApp Ad Tracking Breaks (and How to Fix Each)

Wabbiyo — Fri, 23 Oct 2026 12:03:49 +0000

You’re capturing the referral object from WhatsApp Click-to-WhatsApp ads, but revenue-per-ad numbers still look wrong. These are the usual reasons.

Referral not saved
It only arrives with the first message from an ad click. If your webhook handler skips it, or only processes text, the source is lost for good. Save it before anything else.
Phone format mismatch
WhatsApp sends 919876543210. WooCommerce stores +91 98765 43210 or 09876543210. Normalise both sides to digits with the country code before matching.
Repeat buyer, old ad
A customer clicked ad A in March and ad B today. Overwriting the source loses history, and never overwriting credits the wrong ad. Store every touch with a timestamp and pick by your attribution rule.
Order placed from another number
The chat came from one number, and the order used a family member’s. Add a fallback match on email, or ask for the order number in chat.
No ad ID in reports
Reports show “Click-to-WhatsApp” as the source but not which ad. Store source_id and map it to campaign and ad names.
Counting chats, not sales
The dashboard still ranks ads by conversations. Make revenue per ad the default view.

Wabbiyo’s WhatsApp Ads module, a WordPress plugin on the official Cloud API, handles referral capture, matching and revenue reports for WooCommerce: Click here to know more.

6 Ways a WhatsApp AI Chatbot Goes Wrong (and How to Prevent Each)

Wabbiyo — Thu, 22 Oct 2026 10:51:40 +0000

Adding an LLM to a WhatsApp support line takes an afternoon. Making it safe to leave running takes longer. These are the six failures to design for.

It invents a discount
A customer asks “any offers?” and the model makes one up. Fix: answer only from retrieved content, and add a hard rule that prices and offers come from your product data.
It guesses order status
“Your order will arrive tomorrow” with no lookup behind it. Fix: route order questions to a database lookup by phone number. Never let the model answer them from context.
There’s no way to reach a human
The customer types “agent” three times and gets three AI answers. Fix: check for handoff keywords before calling the model at all.
It answers off-topic questions
Someone asks it to write an essay or solve homework. Besides wasting tokens, Meta’s WhatsApp Business terms (since January 2026) don’t allow general-purpose AI assistants. Fix: scope the system prompt to your business and refuse anything else politely.
Outdated product information
The bot quotes last month’s price. Fix: re-index content when products or pages change, not on a weekly schedule.
Wrong language
The customer writes in Hindi or Tamil and gets an English reply. Fix: tell the model to reply in the customer’s language, and test it with real mixed-language messages (“size M available hai?”).

Bonus: log everything
Store the question, retrieved sources, answer and handoff reason for every message. You’ll find content gaps within a week.

Wabbiyo’s WhatsApp AI chatbot, a WordPress plugin on the official Cloud API, handles retrieval from your site, order lookups and human handoff: Click here to know more

6 Bugs You’ll Hit Building a Shared WhatsApp Inbox

Wabbiyo — Wed, 21 Oct 2026 11:47:03 +0000

If you’re building a team inbox on the WhatsApp Cloud API, these are the bugs that show up in the first week of real use.

Two agents reply at once
Both opened the chat and both typed a reply. Add ownership: assign on first open (or by a routing rule), and block or warn when a non-owner sends.
Replying after the 24-hour window
The API rejects free-form messages sent more than 24 hours after the customer’s last message. Track the last inbound timestamp and switch the composer to template-only when the window closes. Don’t let agents type a reply that will fail.
Chats stuck with an absent agent
An agent goes on leave with 30 open chats. Add a “reassign all” action, and auto-reassign chats that go unanswered for a set time.
Duplicate contacts
“919876543210”, “+91 98765 43210” and “09876543210” become three contacts. Key contacts on the wa_id from the webhook, not on whatever the user typed in a form.
Internal notes sent to the customer
If notes and replies share a table and a send function, one wrong flag sends “this customer is difficult” to the customer. Make notes a separate type that the send path can never pick up.
Media URLs expire
The media URL from the API is short-lived. If you store the URL instead of the file, images and documents break later. Download and store the file when the webhook arrives.

Wabbiyo’s team inbox, a WordPress plugin on the official Cloud API, handles ownership, the service window, reassignment and media storage: Click here

Why Your WhatsApp Broadcast Didn’t Deliver: 6 Causes and How to Debug Them

Wabbiyo — Sat, 17 Oct 2026 10:38:32 +0000

You sent a WhatsApp broadcast to 5,000 contacts through the Cloud API. The API returned success for every request, yet delivery reports say far fewer were delivered. Here are the usual causes.

1. The number isn’t on WhatsApp
The API accepts the request, then the status webhook returns a failure. Flag these numbers so you don’t keep paying to retry them.

2. Meta’s per-user marketing limit
Meta limits how many marketing messages a person receives from businesses within a period. If a user has hit that limit, your message fails with a specific error code. That isn’t a bug in your code. Look at the error code in the webhook payload, not just the “failed” status.

3. Messaging limit tier reached
Each business number can only start conversations with a limited number of unique users per 24 hours. Large audiences on a new number will hit this. Spread the campaign across days.

4. Template paused for low quality
If recipients block or report a template, Meta can pause it. Every send then fails until you fix or replace it. Watch template status webhooks.

5. The contact never opted in
This isn’t an API error, but it is the root cause of points 2 and 4 over time. Don’t put contacts without consent records into marketing sends.

6. Bad phone formatting
“+91 98765-43210”, “098765 43210” and “9876543210” are the same person. Normalise to digits with the country code before sending, or you’ll see failures and duplicates.

Debug checklist

Store the message ID returned for every send.
Log every status webhook with its error code.
Group failures by error code after each campaign.

Wabbiyo, a WordPress plugin on the official Cloud API, handles queueing, delivery tracking and opt-outs for broadcasts if you’d rather not build this yourself: Click here to know more

WooCommerce Order Updates on WhatsApp: 6 Bugs I’d Watch For

Wabbiyo — Fri, 16 Oct 2026 12:19:46 +0000

Sending a WhatsApp message when a WooCommerce order changes status sounds like a 10-line job. In production, these six problems show up first.

Sending inside the request
If you call the WhatsApp API directly inside woocommerce_order_status_changed, a slow API response slows down checkout or the admin order screen. Push the work to Action Scheduler with as_enqueue_async_action() instead.
The same message twice
Admins move an order from processing to on-hold and back. Your hook fires each time. Save a meta flag such as _wa_sent_processing and check it before sending.
Bad phone numbers
Customers type “098765 43210”, “+91-98765-43210” or a number without the country code. Normalise using the billing country, strip everything except digits, and drop the leading zero.
No consent
Sending without opt-in risks your number’s quality rating. Add a checkbox at checkout, save it to order meta, and check it before every send.
Template category drift
“Your order shipped! Use code SAVE10 on your next order” looks harmless, but Meta will treat it as marketing. Keep order templates purely transactional so they stay in the cheaper utility category.
Silent failures
The API returns a message ID even if delivery later fails. Subscribe to the status webhook, write the result to the order notes, and fall back to the WooCommerce email when it fails.

php
add_action( 'woocommerce_order_status_changed', function( $id, $from, $to, $order ) {
$tpl = $map[ $to ] ?? null;
if ( $tpl && has_opt_in( $order ) && ! $order->get_meta( "wa_sent$to" ) ) {
as_enqueue_async_action( 'send_wa_order_update', [ $id, $tpl ] );
}
}, 10, 4 );

If you’d rather not build and maintain this, Wabbiyo is a WordPress plugin that does it on the official WhatsApp Cloud API, with a free plan: Click here to learn more

6 Edge Cases That Break Abandoned Cart Reminders (and How to Handle Them)

Wabbiyo — Thu, 15 Oct 2026 11:21:52 +0000

Sending a reminder when a cart is abandoned sounds simple. In production, these six cases cause most of the complaints.

They already ordered (race condition)
The customer pays a few seconds before the reminder job runs.
Fix: cancel scheduled jobs on order creation and re-check for an order inside the job before sending.
They ordered on another device
Cart on mobile, order on laptop. Your cart ID never gets linked to the order.
Fix: before sending, look for a recent order matching the phone number or email, not just the cart ID.
The cart changed after capture
They added two more items after you saved the first snapshot.
Fix: update the snapshot on every checkout update and reset the timer each time.
An item went out of stock
Reminding someone to buy something they can’t buy is worse than no reminder.
Fix: check stock in the job; skip the message or remove that item from it.
The message lands at 2 AM
Timers don’t know the customer’s time of day.
Fix: add quiet hours and push messages into the next allowed window.
The customer replied STOP
Consent can be withdrawn at any time.
Fix: store consent per contact, handle opt-out replies, and check consent right before every send.

Bonus: duplicate carts. One shopper can create several carts in a session. Deduplicate by phone so they get one sequence, not three.

If you’re building this yourself, the architecture (Action Scheduler + WhatsApp Cloud API) is here: read on Hashnode

If you’d rather see the full recovery strategy (timing, copy, coupons): WhatsApp cart recovery for WooCommerce