- Home
- Skills
- APIs & Backend
- Read Receipt: Find Why WhatsApp Messages Don't Arrive
More screenshots
Works with the AI Agents you already use
Read Receipt: Find Why WhatsApp Messages Don't Arrive
Subscribers get updates with release notes when the rules change.
$5
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
Read Receipt: Find Why WhatsApp Messages Don't Arrive
Example session with this skill installed
Customers say our WhatsApp order updates never arrive, but our logs say sent. Here's the send function: const r = await axios.post(GRAPH_URL, {messaging_product:'whatsapp', to: phone.startsWith('0') ? '27'+phone.slice(1) : phone, type:'text', text:{body}}); await db.markSent(orderId, r.data.messages[0].id); return {ok:true}; We don't handle status webhooks yet. Some customers last messaged us weeks ago.
- Read your context and instructions
- Compiled the read receipt
Summary
Your code calls markSent when Meta accepts the request, and Meta returns a wamid before any delivery happens. Customers who last messaged you weeks ago are outside the 24-hour window, so those free-form texts most likely fail later, on a status webhook you don't receive yet. Your phone logic can also send a foreign customer's update to the wrong person.
What is wrong
| Problem | Effect |
|---|---|
markSent runs on the API response | Logs say sent for messages that fail |
| No status webhook | You can't see failures |
| No window check | Closed-window texts fail |
| Local numbers rewritten | A UK number turns South African |
What the answer covers
Corrected send logic, a signed webhook, a template for closed windows, and how to audit the rows you already marked as sent.
The skill gives your agent the corrected code.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP
About this skill
The WhatsApp API and your own gateway can both report success while the customer gets nothing.
Your agent checks for
- Sends marked successful from the API response alone
- Messages sent outside the 24-hour window
- Phone formatting that sends a foreign customer's message to the wrong person
- Inbound routes that silently lose every new enquiry
- Webhooks that pass the verify handshake and fail on every delivery
- Stored XSS through message text and voice note transcripts
- Number moves that Meta's new account model no longer allows
Why it's a subscription
Meta changes this platform often. Part of our first draft went out of date before we'd finished it. Subscribers get updates with release notes when the rules change.
How it was tested
The checks come from a production multi-number WhatsApp gateway and were reviewed against Meta's documentation in November 2026.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Meta changes its rules often, so check the changelog before a migration.
The older number migration steps come from one migration.
Reviews code and configuration. It doesn't send messages for you.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed
- Accounts
- WhatsApp
Permissions
File Scopes
Any API calls go only to graph.facebook.com or your own gateway, using the token you supply.