Remember to have the Messaging Answer ready before creating the SMS Campaign.
Click on the top left corner of the screen.
Click Settings.
Under the Proactive Conversations category, click Proactive SMS.
The Proactive SMS page lists SMS Campaign(s) that have been created.
From the Proactive SMS page, click Create Campaign.
Enter the following information about the Campaign.
Campaign Name – Enter a name that helps you identify what the Campaign is for.
Description – Provide a brief description of what the Campaign is for.
Phone Number – Select the phone number the Campaign will use to send SMSes for the Campaign.
Note – You’ll only see SMS-able phone numbers on the list.
Note – Replies to an SMS Campaign route to the Inbox linked to the phone number.
Language – Select the language the Messaging Answer is created under.
Answer – Lists Messaging Answers created based on the language chosen. Select the appropriate Messaging Answer you created for this Campaign.
Campaign Schedule – Configure the time frame when SMS Campaign messages are allowed to go out.
Note – If the SMS Campaign’s start date/time (configured in the Add Recipients page) falls outside the Campaign’s schedule, then outreach begins on the next SMS send window. Messages are received based on the recipient’s prescribed timezone on the CSV.
Closed checkbox – Check the Closed box if you don’t want SMSes sent on a particular day. The Closed is checked by default, so uncheck the Closed box to allow SMSes to be sent on a particular day.
Click Create Campaign.
Once your SMS Campaign is created, next, you’ll need to add the recipients that will be contacted as part of the outreach for the Campaign.
To the right of the Campaign you created, click , then select Edit Recipients.
From the Campaign’s outreach status page, click Add Recipients. Enter the following information:
Campaign Details – This section shows the meta details of the SMS Campaign.
Recipients – Click CSV Template to download a CSV template to upload your recipient list. The template is pre-populated with rows with sample timezones and phone numbers in the correct format.
Edit the CSV template:
Enter the recipient’s timezone* in column A based on their primary location.
For column A/timezones, use the TZ database name found here .
Enter the recipient’s phone number in column B.
You must include the country code (1 for the US).
There is no need to include a “+” before the country code, as this is done programmatically in Gladly if it’s missing. The phone number format is country code – area code – phone number (e.g., 1-555-123-4567).
Enter the recipient’s name in column C.
For column C/name, the name used here is used to replace the Customer’s First Name variable in the Messaging Answer.
Save the CSV as Comma Separated Values.csv or CSV UTF-8 only, and use a name that allows you to identify the recipient list easily.
Once your CSV is saved, click Upload CSV to upload your recipient list (CSV).
Outreach Date/Time – Select a date/time when you want your Proactive SMS Campaign to begin. For example, If you are setting up your Campaign on the 3rd of the month but want to start the automated SMSes to go out on the 15th of the month, select the 15th as the start date. You can choose a time and any month in the future.
Should outreach end on a certain date/time? checkbox – Check this box if you want the SMS Campaign to end on a specific date/time, then you can specify the end date/time. Without an end date/time, a Campaign will be marked as “Completed” once it goes through the entire recipient list.
Note – If the outreach date and time fall outside the SMS Campaign’s schedule (on the SMS Campaign’s details page), outreach will begin on the next SMS send window.
Note – Some recipients may not be contacted if the outreach end/date time is reached before everyone is contacted. See SMS send limits for more information.
Click Save.
The outreach will begin on the outreach date/time you selected.
*Watch Out – Specify the correct timezone on the CSV
When entering the timezone on the CSV, use the TZ database name found here. The default timezone used to call Customers is set by your organization’s time. Because the Customers you SMS may be in different time zones, you will need to specify a timezone for each recipient on your list. Know where your Customers are to avoid contacting them at odd hours. For example, if your organization’s timezone is America/New_York (EST) and your SMS Campaign start time is 9 AM, if you have Customers on your recipient list that lives in Los Angeles (America/Los_Angeles) and you don’t enter their timezone as America/Los_Angeles, you’ll be SMSing them at 6 AM.
Tip – Return to the SMS Campaign list
Click < Proactive SMS on the top left area of the Campaign Status page to return to the SMS Campaign list.
An SMS Campaign can contain one or multiple recipient lists/CSV, and each CSV can contain up to 3,500 contacts. Every recipient list uploaded can have a different outreach date/time.
Click Add Recipients to upload another CSV of SMS contacts you’d like to contact as part of the SMS Campaign.
If your CSV cannot be uploaded due to an error, you may see an error message with a link to download the error log. Click Download error log to view the CSV log.
Look under column A in the error log to see what caused your upload to fail.
Number of recipients exceeds the maximum number allowed #
Ensure your CSV has 3,500 contacts or less.
Add a new recipient list if you have more than 3,500 contacts.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.