| Table of Contents |
|---|
...
Twilio
Twilio is used to send text messages to your customers. You will use this to manage your company's SMS numbers.
...
5. Scroll down to Messaging. Messaging automation needs to be set up in order to for SignupApp to get the information.
Under Messaging complete the following fields:
...
CONFIGURE WITH | Select Webhooks, TwiML Bins, Functions, Studio, or Proxy | ||
A MESSAGE COMES IN | Select Webhook, then, copy and paste the URL below.
|
...
Required information for SUA to talk to Twilio:
...
Phone Number |
|
Account SID | Located on the main dashboard page in Twilio |
Auth Token | Located on the main dashboard page in Twilio |
...
| Info |
|---|
You won’t be setting up the adapters in Blueshift but you will need to provide the below information via a ticket to get it set up. |
Phone Number |
|
API Key SID | Located under settings in Twilio |
API Secret | This pops up when you create an API key. You will need to copy it save it then or else it will be lost. |
Account SID | Located on the main dashboard page in Twilio |
Auth Token | Located on the main dashboard page in Twilio |
...
You will need to coordinate the following with Twilio.
Blacklisting | You will need to coordinate with our Twilio rep, Dominique Kaittinat <dkiattinat@twilio.com> on the handling of your own opt-in/opt-outs. This needs to be setup correctly/requested appropriately on the application. "Correctly" in this instance means the blacklisting feature is NOT being utilized. SUA is handling the opt-ins/outs, not Twilio. |
Validation | You will need to add free Twilio validation service to the forms for your phone numbers to ensure the customer is added to correct list. This will ensure no international customers sign up to domestic lists. The following documentation from Twilio will help you set this up, but feel free to engage Dominique for direction first. |
...
https://www.twilio.com/docs/sms/api/message-resource#delivery-related-errors
...
SignupApp
Next, you will need to set up the Twilio information in SignupApp. SignupApp is used as the scaffolding or the structure that is going to handle the lifecycle of people that get signed up for SMS campaigns. SignupApp will also manage the opt-ins for SMS signups.
...
Log in to SignupApp
Select SMS lists at the top of the page then click on SMS CODE SETUP.
Click + sign in the lower right-hand corner of the screen to set up a new SMS code.
Complete the following fields:
...
SMS Provider | Select Twilio | |||
Twilio Account Token (Called "Auth Token" in Twilio) | Varies, copy and paste from the Auth Token field in Twilio. This will be found of the main dashboard. To copy, select Show, then select and copy the token. | |||
Twilio SID (Called "Account SID" in Twilio) | Varies, copy and paste from the Account SID field in Twilio. This will be found on the main dashboard. | |||
Code Type | Select Long for full length phone numbers and Short for short codes. | |||
SMS Code | Varies, copy and paste from the Phone number field in Twilio. | |||
Basic Default Messaging Keywords: | These messages will be sent as replies when the corresponding keyword is sent to the phone number. These default messages can by overridden, but all verbiage (including default messages) must be approved by legal before go-live. | |||
Save | A message will be sent instructing the customer to contact customer service. | |||
Help | This message provides the customer with instructions on unsubscribing when they request help. | |||
Info | This message will be sent to the customer when they request more info. They will be sent a link to the terms and conditions. | |||
Unsubscribe | Confirmation customer will receive when successfully unsubscribed.
| |||
Fallback | "Fallback" is used as a catchall and will be sent when SignupApp doesn't understand the request. | |||
...
Navigate to SMS LISTS.
Click + sign in the lower right-hand corner of the screen to set up a new Paid SMS List.
Complete the following fields:
...
List Code | Enter a list code for identification purposes. Customers will be required to include this list code in their text responses. The SMS codes (phone numbers) are most likely going to be used for multiple list. This will identify which list the customer is contacting us about. (Opt in, unsubscribes, etc) This is a free form field. | ||
List Description | Enter a descripiton of the list here. | ||
List Channel | This will default to SMS. | ||
List Type | The list type of Paid should be selected. | ||
SMS Code | Select the phone number (SMS code) set up previously. | ||
Item Number | Enter the paid list that this phone number will be supporting. This field is required for profile validation and is helpful when creating segments in Blueshift. If the item number is not added or is added incorrectly, it could be added to the wrong customer number and email pair.
| ||
Default Messages | These messages are specific to the individual list (rather than the phone number which might have multiple lists attached) and will be sent when a reply from the customer is required and/or when a reply from the customer is received. Update all of the placeholders within the default messages. All messages must include the list code. These default messages can be overridden, but all verbiage (including default messages) must be approved by legal before go-live. | ||
Opt In | Customers will be required to confirm or opt in to their subscription. They will be reqired to reply with "COMFIRM" followed by the list code. (Example: COMFIRM XYZSMS) There is no time limit to opt in, but failure to do so or failure to do so correctly will prevent the signup process from completing. If a customer attempts to signup again in the interim, the original signup and opt in will be replaced by the new one. If they have already opted in to the original signup, nothing will happen with the new signup. Customers will not exist in Blueshift until they opt in. | ||
Unsubscribe | Comfirmation customer will receive when successfully unsubscribed.
| ||
Welcome | Welcome message sent to a customer when they submit a signup. This message include various instructions including confirming a signup/opting in. Instructions to unsubscribe, get info, and get help are also included. If a customer is requesting to unsubscribe and replies STOP without a list following, they customer will be unsubscribed from all lists attached to that phone number instead this specific list. | ||
Info | This message will be sent to the customer when they request more info. They will be sent a link to the terms and conditions. | ||
Help | This message will be sent to the customer when they request help. The message includes information on how to unsubscribe, as well as customer service contact info. |
...
Meaning, if a customer is subscribed to an SMS list with email1@domain.com and phone number 123-456-7890 and tries to signup for another SMS list with the same email address (email1@domain.com) and new phone number 098-765-4321, they would not be able to signup since there is already an email to phone number relationship that exists in SUA2123-456-7890 and tries to signup for another SMS list with the same email address (email1@domain.com) and new phone number 098-765-4321, they would not be able to signup since there is already an email to phone number relationship that exists in SUA2.
However, if a customer subscribes and opts-in to an SMS list with email1@domain.com and phone number 123-456-7890, then opts-in to a different SMS list with a different email address (email2@domain.com) but the same phone number (123-456-7890), the signup will go thorough. In the event that a customer is opted-in to an SMS list, then subscribes to the same SMS list using a different email address but the same phone number, the new signup becomes the new record and the original record is unsubscribed. Additionally, the fulfillment_sms_unsubscribe event is sent to Blueshift for the original record. This way the customer would not receive two SMS messages to their phone for the same list.
In the refactored instances of Blueshift we are doing additional validation so, post migration, counts will differ from the legacy instances. In the legacy instances we were recording signups with email addresses regardless of whether they were associated with a subscription. For the initial data migration to the the refactored instances, we will only bring over email addresses tied to a subscription.
Post migration, we’ll make a MW API call and use the subscription reference to make sure the correct email address is associated with the signup. This will account for email and L type logins.
...
Blueshift
Next, you will need to set up the content, campaigns, and connection to Twilio in Blueshift. Blueshift is used to create SMS content and target subscribers. The content will then be sent from Blueshift and out through Twilio.
...
We have broken the SMS events out into two separate events. The first one for the initial signup (prior to opting in) and the second one is sent after the customer has completed the opt-in process be by sending in the correct confirmation message. Doing this allows you to target customer via email if they have not completed the opt-in process. See the SMS Campaigns section below for more details.
...
If a customer unsubscribes to the SMS list, the fulfillment_sms_unsubscribe event is added to the user profile and the sms_active attribute is and subscribed attributes are set to false.
| Info |
|---|
The phone number attribute at the user level is updated with the phone number that was present in the fulfillment_sms_subscribe event. |
...
Navigate to segments.
Click +SEGMENT
Under the “What type of segment do you want to create?” section select Basic or Advanced Segment
Under the “What do you want to segment on?“ section select the Transactions radio button and then subscriptions from the drop down menu
Enter a name for the segment.
Click + to add a condition.
Make the following selections:
...
Transaction is: | subscriptions | ||
With the following attributes:
| item_code | is equal to | [enter the pub code from SUA here] AND sms_active | is equal to | True |
...