Skip to content

WHMCS notices on WhatsApp, with the provider you choose

WhatsApp Notifications for WHMCS

  • Version 1.8.0
  • WHMCS 8.13 – 9.0
  • PHP 8.1 – 8.3
  • Updated Nov 22, 2026

Notify your customers on WhatsApp about invoices, payments, tickets, services and domains, and notify yourself about orders and alerts. You send through the official WhatsApp API (Meta), through Chatwoot or through Evolution. Each customer confirms their number with a code and chooses which notices to receive.

  • 3 ways to send
  • 17 customer notices
  • Only to confirmed numbers
See plans and pricing
from $100MXN / month

Addon module for WHMCS 8.x and 9.x · In English and Spanish

WHMCS · WhatsAppNotify Provider You choose where notices go out from (Meta's official API, Chatwoot or Evolution) and connect your number. The token is not shown.

What it solves

WhatsApp is the first thing your customers check, so the module only writes to people who confirmed their number.

Choose how to send
The official WhatsApp API (Meta); Chatwoot, where each notice lands in the customer's conversation; or Evolution, which is unofficial and connects with a QR code.
Only confirmed numbers
A customer receives notices after confirming their number with a 6-digit code sent to them on WhatsApp. The code expires in 5 minutes.
Meta templates under control
With the official API, each notice is tied to its approved template. The panel tells you which ones are missing or still in review, and notifies you when Meta changes their status.
When something fails, it tells you what to do
A failed send stays in the log with an explanation in plain language: number without WhatsApp, template paused, expired token.

Provider · 1 of 5

Loading screen…

This screen could not be loaded. You can open the full image or pick another one.

Everything it includes

Notices

  • 17 customer notices: invoices, tickets, services, domains and payment receipts
  • Alerts for you: tickets, orders, payments, cancellations and failed service activations
  • Alerts from your other modules: low ResellerClub balance, Proxmox node down, charges summary
  • Editable messages in Spanish and English, with WhatsApp bold and italics
  • A button in the message, such as "Pay invoice"
  • Each customer chooses which notices to receive

Numbers, templates and control

  • Number confirmation with a code: at most 3 codes per hour and 5 attempts per code
  • Automatic phone formatting for Mexico, the US, Canada, Brazil, Colombia and Argentina
  • Meta templates: backup, import and sync from the panel
  • Message history with the phone number partly hidden, which cleans itself up
  • Keys and tokens are never shown on screen
  • With Evolution: reconnect by QR and a check that the number has WhatsApp

Panel sections inside WHMCS

  • Dashboard
  • Settings
  • Templates
  • Meta Templates
  • Logs
  • Info

Getting started

  1. Choose and connect your provider

    Select Meta's official API, Chatwoot or Evolution and enter its credentials. With Meta and Chatwoot, you tie each notice to a template approved by Meta.

  2. Your customers confirm their number

    From their client area they request a code, receive it on WhatsApp and enter it to get linked.

  3. WHMCS notifies

    Each event checks the customer's preferences and sends only to confirmed numbers.

Plans and pricing

The same module on all three plans: what changes is how you pay and how you receive the code. Prices in Mexican pesos (MXN), plus tax.

Monthly

$100 MXN per month

  • Every feature of the module
  • Updates and support while the license is active
  • Renews every month
  • Installation: $500 MXN, charged once
Get the monthly plan

Best value

Annual

$1,000 MXN per year

  • Pay for 10 months, use 12: you save $200 MXN a year
  • Installation included
  • Every feature of the module
  • Updates and support while the license is active
Get the annual plan

Open source

$3,000 MXN, one-time payment

  • Readable source code, not encoded
  • You can adapt it to your own operation
  • One payment, no renewals
  • Installation included
Buy the open-source version

Our team does the installation on your WHMCS: we upload the module, activate it and configure it with you. I have a question before buying

WhatsAppNotify changelog

Current version: 1.8.0. Last updated: Nov 22, 2026.

  1. v1.8.0

    • Improved: the settings screens no longer print stored keys, tokens or secrets in the page source. To change one you now tick "Replace the stored value", so a password manager cannot overwrite it by accident.
    • Improved: the connection test no longer sends the provider's full response back to the browser, since it could include tokens.
    • Improved: the module now defaults to version 25 of Meta's API, because the previous version is retired in January 2027.
    • Fixed: linking replies and the verification code no longer carry a hard-coded company name or portal address; they use your own company name and your WHMCS address.
    • Fixed: saving one template no longer overwrites the other languages; Canada was added to the country list and an alert switch that never did anything was removed.
  2. v1.8.0

    • Improved: the panel shows which sending provider is active, warns about events with no Meta template or with a pending one, and explains with a hint why each send failed.
    • Fixed: templates with a dynamic link button are no longer sent with an empty button value, which made Meta reject the whole message.
    • Improved: the whole module panel, manuals included, is in Spanish, and the settings screens show one setting per row with a single save button.
    • Improved: the manual now lists all 36 notices the module sends, and the template editor shows readable names instead of internal identifiers.
    • Fixed: the log tables no longer break words letter by letter.
  3. v1.8.0

    • New: the administrator is alerted when a customer places a new order, without waiting for it to be accepted or paid. With WhatsApp Cloud, the matching template must be created and approved in Meta.
    • Fixed: the "order paid" alert was failing because Meta rejected the message when the order number was missing from the button; the number now travels with the message.
    • Improved: the new-order alert is sent after checkout finishes, so it never slows down or interrupts the customer's purchase.
See the full history (9 more entries)
  1. v1.7.0

    • Fixed: most Meta template definitions stored in the module had lost their emojis and showed question marks. They were restored, and the module no longer lets you create or import templates with damaged emojis.
    • Improved: only the account owner can see and manage WhatsApp; a guest user can no longer unlink the owner's number, change their preferences or send codes to their phone.
    • Improved: the side menu and the event checkboxes appear in the customer's language.
    • Improved: three notices that Meta had reclassified as marketing now use approved utility templates.
  2. v1.6.0

    • Fixed: a local number from another country was wrongly turned into a Mexican mobile number, so the message or verification code could reach a stranger. Those numbers are now rejected, the customer is asked to fix their phone with the country code, and the country on the customer's record is used.
    • Fixed: the hourly limit on verification codes was never enforced; repeated sends are now blocked and only the most recent code is valid.
    • Improved: automatic linking by phone number was turned off, because it could erase valid verifications of foreign customers.
  3. v1.6.0

    • Fixed: Proxmox, ResellerClub and gateway-charges alerts meant to go out over WhatsApp were reaching nobody after the provider change. They are now sent through the active provider with templates approved in Meta.
    • New: the admin alert templates carry a button that opens the exact order, invoice or ticket.
    • Fixed: the variables in those alerts, such as the server or the error, were arriving as dashes instead of real data.
  4. v1.5.0

    • New: customers are notified when their domain is about to expire, when it has expired but can still be renewed at the normal price, and when a renewal is confirmed. The registrar is checked before alerting, and if a notice cannot be sent it is retried on the next run.
    • New: template buttons are finally sent along with the message when using Evolution API, with the text and link as a fallback if the button is not accepted.
    • New: once a day the module checks Meta for the status of pending templates, records it and alerts you on Telegram when one is approved or rejected.
    • New: Meta templates can be deleted from the panel, and the fetch and sync buttons also work with the Chatwoot provider.
    • Fixed: roughly one in five orders could fail because the new-invoice notice was sent in the middle of the process; it now goes out once the order completes.
  5. v1.4.0

    • New: a third sending mode, "Cloud via Chatwoot". Notices go out as WhatsApp templates through Chatwoot, are logged in the customer's conversation, and their replies land in the same thread.
    • Improved: if preparing the contact or conversation in Chatwoot fails, the send falls back to direct WhatsApp Cloud; if the message itself fails it is not retried, to avoid sending it twice.
    • Improved: linking with a verification code keeps working in this mode.
  6. v1.3.0

    • New: besides Evolution API, you can now send through Meta's official WhatsApp Cloud API. In this mode notices go out with Meta-approved templates, with one template assigned to each event.
    • New: Meta template backup and sync: export and import a backup file (it never includes keys), fetch the templates from Meta and create the missing ones, with a dry run and confirmation first.
    • New: a "Meta templates" tab in the panel to manage the definitions and their status.
  7. v1.1.0

    • New: a single notification preferences page for the customer, shared with the Telegram module, with its own entry in the account menu.
    • New: templates exist in Spanish and English, and each customer receives messages in the language of their account.
    • Fixed: turning off a notice in one language tab now turns it off in the other language as well.
    • Fixed: emojis in templates were turning into question marks, and the "Test connection" button no longer reported a false security error.
    • Improved: linking WhatsApp numbers is more reliable.
  8. v1.1.0

    • New: customers are notified when a domain transfer is pending, when a domain leaves their account and when they receive a new one.
    • Fixed: Argentine and Brazilian mobile numbers were formatted without the digit WhatsApp requires, so those sends failed; they now go through correctly.
    • Improved: the size of messages accepted by the webhook is capped, one recipient can no longer receive bursts of messages, and the provider key can no longer appear in error messages.
    • Improved: form protections were reinforced and automatic linking by phone number was turned off for security.
  9. v1.0.0

    • First release: customer notifications over WhatsApp about invoices, tickets, services and domains, plus admin alerts, sent through Evolution API.
    • Includes a template editor, per-customer preferences, a check that the number has WhatsApp, and automatic phone formatting for several countries.
    • Includes a QR code to reconnect the session and logs, documentation and requirements tabs inside the WHMCS admin.

Frequently asked questions

Which provider should I choose?

Meta's official API is the stable option and requires approved templates. Chatwoot uses that same API and puts each notice in the customer's conversation. Evolution is unofficial: it connects quickly, but WhatsApp can block the number if you send a lot.

Can I message any phone number in my customer database?

No. The module only sends to people who confirmed their number with a code. That protects your number and avoids messages to wrong phones.

Who approves the templates?

Meta. The module includes the definitions ready to submit for review and shows you the status of each one, but it cannot speed up or guarantee approval.

Does it work alongside Telegram?

Yes. With both modules, the customer manages both channels from a single preferences page.

Another question? Write to us and we will reply in English or Spanish.

Reach your customers on WhatsApp

Automatic notices only to confirmed numbers, with messages you edit and a log that tells you what happened with each one.