WhatsApp and SMS Gateway Settings

Search Your Gateway

Messagebird Gateway Settings

Both SMS and WhatsApp

##SMS##
Your order {{wc-order}} is shipped on {{date}}

##WHATSAPP##
template-name => order-shipped
namespace => 32995840_dfdb_45b5_91c3_41tyh5fe7a84
language => en
1 => {{wc-order}}
2 => {{date}}

Just WhatsApp

##SMS##

##WHATSAPP##
template-name => (the template name you define on Messagebird)
namespace => (this value is provided by Messagebird)
language => en
1 => {{wc-order}}
2 => {{date}}

Just SMS

Your order {{wc-order}} is shipped on {{date}}

Breakdown of the above template


–  SMS##
 and ##WHATSAPP## are used to define the channels. To make sure this template works, you need to add both of these headers but you can leave any of those empty to not trigger that particular one (examples provided above)

– template-name – is the name you define in your Gateway panel and is provided by Messagebird

– namespace – this value is provided by Messagbird and is generally unique to your account

– 1: 2: – these are the series of variables you define in your Messagebird’s WhatsApp template, in WPNotif settings, use our placeholders listed here

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

WhatsApp Cloud API (Meta Inc., Free) Gateway Settings

Just WhatsApp

##SMS##

##WHATSAPP##
template-name => (the template name you define on Meta/Facebook)
namespace => (this value is provided by Meta/Facebook)
language => en
1 => {{wc-order}}
2 => {{date}}

Breakdown of the above template


–  SMS##
 and ##WHATSAPP## are used to define the channels. To make sure this template works, you need to add both of these headers but you can leave any of those empty to not trigger that particular one (examples provided above)

– template-name – is the name you define in your Gateway panel and is provided by Messagebird

– namespace – this value is provided by Messagbird and is generally unique to your account

– 1: 2: – these are the series of variables you define in your Messagebird’s WhatsApp template, in WPNotif settings, use our placeholders listed here

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

360Dialog Gateway Settings

Both SMS and WhatsApp

##SMS##
Your order {{wc-order}} is shipped on {{date}}

##WHATSAPP##
template-name => order-shipped
namespace => 32995840_dfdb_45b5_91c3_41tyh5fe7a84
language => en
1 => {{wc-order}}
2 => {{date}}

Just WhatsApp

##SMS##

##WHATSAPP##
template-name => (the template name you define on 360Dialog)
namespace => (this value is provided by 360Dialog)
language => en
1 => {{wc-order}}
2 => {{date}}

Just SMS

Your order {{wc-order}} is shipped on {{date}}

Breakdown of the above template


–  SMS##
 and ##WHATSAPP## are used to define the channels. To make sure this template works, you need to add both of these headers but you can leave any of those empty to not trigger that particular one (examples provided above)

– template-name – is the name you define in your Gateway panel and is provided by 360Dialog

– namespace – this value is provided by 360Dialog and is generally unique to your account

– 1: 2: – these are the series of variables you define in your 360Dialog’s WhatsApp template, in WPNotif settings, use our placeholders listed here

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

DamCorp Gateway Settings

Both SMS and WhatsApp

##SMS##
Your order {{wc-order}} is shipped on {{date}}

##WHATSAPP##
template-name => order-shipped
1 => {{wc-order}}
2 => {{date}}

Just WhatsApp

##SMS##

##WHATSAPP##
template-name => (the template name you define on DamCorp)
1 => {{wc-order}}
2 => {{date}}

Just SMS

Your order {{wc-order}} is shipped on {{date}}

Breakdown of the above template


–  SMS##
 and ##WHATSAPP## are used to define the channels. To make sure this template works, you need to add both of these headers but you can leave any of those empty to not trigger that particular one (examples provided above)

– 1: 2: – these are the series of variables you define in your DamCorp’s WhatsApp template; in WPNotif settings, use our placeholders listed here

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

2Factor Gateway Settings

Both SMS and WhatsApp

##SMS##
Your order {{wc-order}} is shipped on {{date}}

##WHATSAPP##
template-name => order-shipped
1 => {{wc-order}}
2 => {{date}}

Just WhatsApp

##SMS##

##WHATSAPP##
template-name => (the template name you define on 2Factor)
1 => {{wc-order}}
2 => {{date}}

Just SMS

Your order {{wc-order}} is shipped on {{date}}

Breakdown of the above template


–  SMS##
 and ##WHATSAPP## are used to define the channels. To make sure this template works, you need to add both of these headers but you can leave any of those empty to not trigger that particular one (examples provided above)

– 1: 2: – these are the series of variables you define in your 2Factor’s WhatsApp template; in WPNotif settings, use our placeholders listed here

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

Karix Gateway Settings

Both SMS and WhatsApp

##SMS##
Your order {{wc-order}} is shipped on {{date}}

##WHATSAPP##
template-name => order-shipped
namespace => 32995840_dfdb_45b5_91c3_41tyh5fe7a84 
language => en
1 => {{wc-order}}
2 => {{date}}

Just WhatsApp

##SMS##

##WHATSAPP##
template-name => (the template name you define on Karix)
namespace => (this value is provided by Karix)
language => en
1 => {{wc-order}}
2 => {{date}}

Just SMS

Your order {{wc-order}} is shipped on {{date}}

Breakdown of the above template


–  SMS##
 and ##WHATSAPP## are used to define the channels. To make sure this template works, you need to add both of these headers but you can leave any of those empty to not trigger that particular one (examples provided above)

– template-name – is the name you define in your Gateway panel and is provided by Karix

– namespace – this value is provided by Karix and is generally unique to your account

– 1: 2: – these are the series of variables you define in your Karix’s WhatsApp template; in WPNotif settings, use our placeholders listed here

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

Spoki Gateway Settings

Just WhatsApp

For  Message Type
##SMS##

##WHATSAPP##
type => message
template => 123
custom_field_name => value
For  Automation Type
##SMS##

##WHATSAPP##
type => automation
automation => 123
custom_field_name => value

Breakdown of the above template

 

– type – Spoki has two different types of methods to send messages “message” and “automation”, we recommend that you use “message” type.

– template/automation – this is the unique ID provided by Spoki

– custom_field_name – you need to replace this with the name of your custom field and for the value part you can use our shortcodes listed here

For example:

ACCOUNT_NAME => {{wp-first-name}}
ZABAIONE => Come posso aiutarti?

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

Wati Gateway Settings

Just WhatsApp

For  Message Type
##SMS##

##WHATSAPP##
broadcast-name=> name
template-name => name
param1 => value

Breakdown of the above template

 

– broadcast-name – This is a unique name provided by Wati for every approved template

– template-name – Another unique value provided by Wati for every approved template

– param – you need to replace this with the shortcode or parameter name you are using in your Wati Approved Template and for the value part you can use our shortcodes listed here

For example if your template in Wati looks like, “Hi {name}, your order {orderid} has been shipped”, then in our settings the template will look like 

##SMS##

##WHATSAPP##
broadcast-name=> 5ff5b00e407553a45ee55b30
template-name => 5ff5b00ecb5074858d94a43f
name => {{wp-first-name}}
orderid => {{wc-order}}

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

Gupshup Gateway Settings

Both SMS and WhatsApp

##SMS##
Your order {{wc-order}} is shipped on {{date}}

##WHATSAPP#
template-id => 12312312 1 => {{wc-order}} 2 => {{date}}

Just WhatsApp

##SMS##

##WHATSAPP#
template-id => 12312312 1 => {{wc-order}} 2 => {{date}}

Just SMS

Your order {{wc-order}} is shipped on {{date}}

Breakdown of the above template


–  SMS##
 and ##WHATSAPP## are used to define the channels. To make sure this template works, you need to add both of these headers but you can leave any of those empty to not trigger that particular one (examples provided above)

– template-id – is the ID provided by Gupshup gateway for your template

– 1: 2: – these are the series of variables you define in your Gupshup’s WhatsApp template; in WPNotif settings, use our placeholders listed here

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

Twilio Gateway Settings

Both SMS and WhatsApp

##SMS##
Your order {{wc-order}} is shipped on {{date}}

##WHATSAPP#
Your order {{wc-order}} is shipped on {{date}}

Just WhatsApp

##SMS##

##WHATSAPP#
Your order {{wc-order}} is shipped on {{date}}

Just SMS

Your order {{wc-order}} is shipped on {{date}}

Breakdown of the above template


With Twilio, you just need to replace Twilio’s placeholders with WPNotif placeholders listed here.

NOTE:

– You can have your SMS template as you like, no need for it to be similar to your WhatsApp template.

– You can also mix and match different Gateways for SMS and WhatsApp, just make sure you follow the appropriate template for the selected ones. 

Msg91 Gateway Settings

Due to introduction of DLT templates in India Msg91 has changed how its API works and just because of that we had to implement those changes so you don’t face any issues regarding message delivery.

For Msg91 every SMS you send with them should contain a Template ID. Template ID is provided by Msg91 and is unique for all your message templates, be it promotional or transactional.

To make our message templates compatible with Msg91 you need to define the templates in WPNotif settings in the below mentioned format.

Just SMS

message => Your order {{wc-order}} is shipped on {{date}}
template-id => 1569851XXXXXXXXXX78

Breakdown of the above template


–  message
 is the approved template with DLT, just replace the variables of DLT template with our placeholders listed here

– template-id – is the unique template ID provided by Msg91 gateway for your template

AWS SNS & Pinpoint Gateway Settings

Just SMS

message => Your order {{wc-order}} is shipped on {{date}}
template-id => 1569851XXXXXXXXXX78

Breakdown of the above template


–  message
 is the approved template with DLT, just replace the variables of DLT template with our placeholders listed here

– template-id – is the unique template ID provided by AWS for your template

Fast2SMS Gateway Settings

Due to introduction of DLT templates in India Fast2SMS has changed how its API works and just because of that we had to implement those changes so you don’t face any issues regarding message delivery.

For Fast2SMS every SMS you send with them should contain a Template ID. Template ID is provided by Fast2SMS (known as message id on their platform) and is unique for all your message templates, be it promotional or transactional.

To make our message templates compatible with Fast2SMS you need to define the templates in WPNotif settings in the below mentioned format.

Just SMS

template-id => 123456
1 => {{first-name}}

Breakdown of the above template


– template-id – is the unique message ID provided by Fast2SMS gateway for your template, can be found here https://www.fast2sms.com/dashboard/dev-api when you select your DLT template

– 1: 2: these are the series of variables you define in your Fast2SMS DLT template; in WPNotif settings, use our placeholders listed here


If you dont see your gateway listed here then it probably means that your gateway does not need any special settings. 

If you are still having issues with your gateway then please create a support ticket here.