Salesforce automated messages allow you to initiate an outbound digital message on Natterbox via an Apex class available within Salesforce flows.
Salesforce Actions
Check Consent
The Check consent action allows you to provide two phone numbers which are then checked against the Consent object in Salesforce if valid consent exists for the provided numbers. Valid consent is defined as explicit opt in or implied opt in valid, more information on consent can be found here.
Inputs
From Number - The number you are sending the message from.
To Number - The number you are sending the message to, typically this is your customers phone number.
Message
Inputs
Channel Type - The channel type in which the message will be sent on, this can be “SMS“ or “WhatsApp”
From Number - The number you are sending the message from.
Message Body - The contents of the message you wish to send.
Person Record - The record that this automated message will relate to, this is also used for if a conversation is created. This must be a Contact, Account, or a Lead.
To Number - The number you are sending the message to, typically this is your customers phone number.
Shared Inbox Id - An optional value should a conversation not already exist, this allows you to define which shared inbox this conversation will belong to.
User Id - An optional value should a conversation not already exist, this allows you to define which Users personal inbox this conversation will belong to.
Template
Inputs
Channel Type - The channel type in which the message will be sent on, this can be “SMS“ or “WhatsApp”
From Number - The number you are sending the message from.
Person Record - The record that this automated message will relate to, this is also used for if a conversation is created. This must be a Contact, Account, or a Lead.
Template Name -
To Number - The number you are sending the message to, typically this is your customers phone number.
Shared Inbox Id - An optional value should a conversation not already exist, this allows you to define which shared inbox this conversation will belong to.
Placeholder Map -
User Id - An optional value should a conversation not already exist, this allows you to define which Users personal inbox this conversation will belong to.
Placeholder Mapping
Placeholder names are case sensitive.
Automated Messages behaviour
Below are a list of behaviours that automated messages will follow.
Numbers not in E164 format
If the provided phone numbers are not in E164 format this will result in an error and the message will not be sent.
Phone Numbers must have a value
If either of the phone number fields are empty then this will result in an error and the message will not be sent.
Invalid Channel Type provided
The allowed channel types are SMS and WhatsApp (not case sensitive), any other value will result in an error and the message will not be sent.
A Template placeholder is not provided
If a template placeholder is not provided with a value then the template will be sent as normal and the placeholders default value will be used.
An invalid placeholder name is provided
If a template placeholder name is provided that is not found on the template this will be ignored and the message will be sent as normal.
FAQ
What minimum Natterbox Salesforce package version must I be on?
The minimum version for the Salesforce Automated Message feature is 1.340. More information can be found here.