The SMS delivery vector allows you to collect customer feedback via SMS Invitations. This functionality allows you to send primary invitations and reminder invitations.



Feature notes:

  • Campaigns can only be modified by the Owner and System Admins.
  • Clicking on a campaign name opens a pop-up with all of the campaign's information.
  • Clicking on the pie chart under Stats opens the Data Transport Report for that specific campaign.
  • A single SMS holds up to 140 bytes. 1 character is usually 1 byte; complex characters and symbols may use more than 1 byte.
  • SMS templates that contain more than 140 bytes of data will send multiple SMS until the whole message is delivered, generating a charge for every set of 140 bytes.




Table of Contents






Managing SMS Campaigns



Creating a Campaign


  1. Navigate to Campaigns → Campaign Suite → Automated.

  2. Click on "+New Campaign" button and then select SMS delivery vector.

  3. In the Settings step all fields are required, fill them and then click Next.Campaign name: choose a name for your campaign.
    Survey: choose the survey template for the campaign.
    Filters: Select any survey filter as a condition for the campaign.


  4. In the Sending step, set up the Reminders and Sending Period
    Reminders: The reminders are sent based on the sent date of the invitation. You are able to enable up to two reminders, please make sure the second reminder is set to a value higher than the first reminder.

    Sending Period: You are able to set when the survey invitations will be sent, based on the system's timezone. The surveys will only be sent during the period between "Start at" and "Stop at".

    Duplication Prevention: You are able to prevent a contact from receiving the same survey invitation from the same campaign within a set number of days. Please make sure the number of days is higher than your Global Duplication Rule, otherwise it will have no effect.



  5. In the Languages step, choose all the languages for this campaign.

  6. In the Templates step, choose a Sender Phone Number for each language and write their templates. You are able to add merge tags by clicking on Merge Tags { } button.

  7. Save all your templates and double-check them, if everything is ok click on Next.

  8. Activate the campaign if you'd like to enable it right away and click on Save and Close.




Priority


When uploading a file for SMS campaigns it tries to find a matching campaign starting from the highest priority and going to the lowest.

The priorities can be checked by taking a look at the Priority column or the order in which the campaigns are shown. The campaign on the top has 1 as priority which is the highest.







Searching in automated campaigns is very straightforward, just type what you're looking for and any matches in Priority, Campaign Name, Type, Survey, Owner and Last Modified Date across all pages will be returned shortly.


The search will look for exact matches within the Campaign Name, see the example below:

Search input: Support

Returned results: Support Links 1; PL-Support 01; Supporting Campaign.






Unsubscribes


Surveys are not sent for contacts that have been previously unsubscribed. When importing a file the system will check the Unsubscribes list and will not send any survey for these specific contacts.

If you wish to manage contacts in the unsubscribes list you can do so from the Unsubscribes & Bounces feature.






Importing for SMS


Import Configuration


When creating your import configuration for SMS in addition to all the fields you want, you will need to add the Delivery Vector field to it. The Delivery Vector field must be present in the upload file and have sms (lowercase) as the value.


Alternatively, you may add a static Delivery Vector field to your SMS configuration with sms (lowercase) as the value. This will make all records being uploaded using that configuration to have the Delivery Vector field with your chosen value added.


Example of a Delivery Vector static field:




File Setup to Assign Template Language


Important: Make sure your file does not contain the Language field.
The Locale field will conflict with the Language field and cause the importing to fail.


In order to assign the correct language template to a record, the Locale field is required in your Import Configuration and import file. To avoid any conflict, make sure your import configuration does not have the Language field present.


When adding the Locales, make sure they match the following format: the two-letter language code underscore the two-letter country code. For example: en_US; pt_BR; en_GB.
The locale field is not case sensitive, you may populate your file with values like en_us, PT_BR, En_Gb and they will all be valid.


For the full list of our supported locales, please visit the Locale Codes support page.