✅ Twilio Whatsapp - New Plugin from Zeroqode

Showcase
23

As below, it appears your plugin functionality is due to be depracted in Nov 2024, but it may be that form a new account it doesnt work. Clearly as you have seen from the Loom video, it does not work as described even with the simplest use case.

Hello David,

Thank you for your reply.

WhatsApp messages are subject to certain rules and restrictions that do not apply to standard Twilio Programmable SMS and MMS messages. It’s important to understand how “templates” and “sessions” work with WhatsApp, and design your messaging flow to follow WhatsApp’s rules.

Templates and Sessions:

All messages sent from your WhatsApp number (or from the Twilio Sandbox) must follow a pre-approved template , unless the end user has messaged you first. After a user sends you a message, you have a 24-hour session to send session messages (or freeform messages) to that user. Session messages do not need to follow a template, and can include media attachments. The 24-hour session restarts each time that user sends you a new incoming message.

Twilio currently has two template creation platforms, detailed below:

  • Content Template Builder: Create rich content (text, media, CTA buttons, quick reply, list picker and more) through console or API and send templates using a template SID across multiple channels including WhatsApp, SMS, MMS, Facebook Messenger and Google Business Messages.
  • WhatsApp Templates: Create basic templates (text, CTA buttons and quick reply) through the console for use on WhatsApp. Message body must match template body to send. This platform will be deprecated on November 1st, 2024, therefore, if you are just starting out you should only use Content Template Builder. See here for more information.

A note about Opt-in and Opt-Out with WhatsApp:

Similar to SMS, you must receive explicit opt-in from end users before sending them a WhatsApp message. WhatsApp requires the opt-in to be active , which means that it can not be assumed. Please review the information here for more details on how to correctly handle opt-in: Rules and Best Practices for WhatsApp Messaging on Twilio (https://support.twilio.com/hc/en-us/articles/360017773294-Rules-and-Best-Practices-for-WhatsApp-Messaging-on-Twilio)

Hope this helps – let me know if you have any further questions or concerns.

Best,
Andres
Twilio Support

24

Hi David,

Thank you for the information :pray:.

We’ll further discuss this with our developers to explore potential adjustments in response to any upcoming API changes. We aim to ensure our plugin continues to function effectively. Rest assured, we will update you on any decisions made. The current API we utilize is still active and should operate without issues.

Our thorough testing on a sandbox account, utilizing Twilio’s provided templates, demonstrates successful template sending. This is evident on both WhatsApp and our demo page, with only the body content being sent, not requiring the ContentSID parameter introduced by the newer API.

Screenshots

image
image1238×512 17.7 KB

IMG_3271
IMG_32711284×1209 182 KB

Could you please verify if your templates were created through the WhatsApp Template Console rather than the new Content Template Builder? This difference could be a factor in the issue you’re experiencing.

Best regards :hibiscus:

25

Hi @d.pearce,

Thank you for your patience!

After discussing with our developer, we understand that the current behavior is expected until the API becomes deprecated, which shouldn’t impact the plugin’s functionality.

Could you please let us know where the templates were created so we can explore further options? Your feedback would be greatly appreciated.

Best regards :sunflower: