Jump to content

Building a WhatsApp notification module — Cloud API direct, no gateway lock-in. Looking for input


Recommended Posts

Hi all,

 

The WhatsApp client notifications request on the feature tracker has 559 votes and is still open, so I started building a notification provider module for it.

 

What I'm aiming at is different from the options I found. Every one of them routes you through a paid gateway - Twilio, or the vendor's own service - with a fee on top of what Meta already charges. I want to remove that layer:

 

- Connects straight to Meta's WhatsApp Cloud API with your own credentials. No middleman, no markup on top of Meta's own per-message cost.

- One-time purchase, not a subscription.

- Ships with ready-made message templates for the usual WHMCS events, so you are not writing and submitting templates to Meta from scratch.

 

Before I go further I would rather ask than guess:

 

1. Are you already sending WhatsApp notifications somehow? If yes, what are you using and what annoys you about it?

2. Which events actually matter to you? I am assuming invoice created, payment received, overdue reminder, service due and domain expiry - but I would rather hear it from people running this daily.

3. Would you prefer a one-time purchase or a subscription? I am planning one-time, but tell me if that is wrong.

 

Also: if anyone is willing to test an early build on a real install, I will give you a free lifetime licence. Honest feedback is worth more to me than the sale.

 

Thanks,

Semih

Link to comment
Share on other sites

  • 1 month later...

Events worth adding: service suspension/termination and maybe a login or password-reset alert. Invoice created and overdue reminders are the ones people actually act on; payment received mostly duplicates the email receipt, so keep it optional per event.

 

The part that usually breaks in DIY modules isn't the API call, it's the template lifecycle: approval, language variants and the 24-hour customer service window. Give admins a per-event mapping of template name plus language, and a fallback to email whenever Meta returns an error, otherwise notifications vanish silently during an outage.

 

One-time pricing fits this audience better than a subscription stacked on Meta's own charges.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated