Recurring Campaigns
Recurring campaigns allow an organization to schedule a text campaign on a recurring basis.
From the Recurring tab, edit or delete all current and recurring jobs. Clicking View Runs will detail all of the runs for that job and current dashboard statistics/metrics.
Status Definitions
The statuses mean the following:
- Delivered - Twilio has received confirmation of message delivery from the carrier, (and, where available, the destination handset).
- Sent - Twilio has not received updated delivery information for your message. Typically, a sent status will be replaced by a delivered or undelivered status within seconds or minutes. Please note that US/Canada long code MMS often remain in sent status due to a lack of final delivery status updates from carriers. Once a message is older than 72 hours, receiving a further status is unlikely, although we will update the record if we receive one. Your messages will stay in sent status forever if you are sending messages using the deprecated /SMS/Message REST API Resource, which does not support delivery status updates.
- Error - TO number is not a valid phone number
- Undelivered - Twilio has received a delivery receipt indicating that the message was not delivered. This can happen for a number of reasons including carrier content filtering, availability of the destination handset, etc.
- Preparing - A iMIS Text Messenger status indicating that the message is being prepared to send.
- Failed - The message could not be sent. This can happen for various reasons including queue overflows, account suspensions and media errors (in the case of MMS). Twilio charges a Failed Message Processing Fee of $0.001 per message that fails.
Creating the required TEXTMSG activity type
(missing or bad snippet)Creating a recurring campaign
To create a Recurring Campaign, do the following:
- Click the Recurring tab.
- Click New Recurring Campaign.
- Enter a Campaign Name.
- Enter an email address in the Status Report E-mails(s) field. This email address will receive a full status report of the campaign results.
- From the Recipient Query Path field, click Browse. Retrieve the result set for the SMS Campaign.
- From the API Mode drop-down, choose one of the following:
- Live - Live mode will send SMS messages.
- Test - In test mode you will be allowed to conduct a campaign, but no SMS message will be sent.
- In the Message Template field, construct the text message to your members. The Merge Fields to the right are fields from the selected IQA. You can use these fields in your message. For example. addressing your members by name. "Hello ${FullName},"
- Enable Write to Activities to ensure the TEXTMSG activity is saved to the member's account upon successfully receiving the text message.
- Enable Write to Communication Log (Interactions) to have a communication log item saved to the member's account upon successfully receiving the text message. You will need to create the TEXTMSG activity type if it does not exist in iMIS.
- From Select Recurring Schedule, choose how often the recurring campaign will send (in UTC).
Example: Every month on the 2nd at 8:10 - The campaign will run on that time on the 2nd of every month.
- From the summary, review how many contacts were pulled back from the query and how many people you will be sending to:
- Estimate Segments show and estimation of how many text messages will be sent. A text message might be longer than 160 characters (standard max length for 1 text message) depending on your merge fields from your IQA.
- Max Segments / Day will show you current amount of segments(messages) you have left to send.
- Estimated Send Time allows you to know when it will be sent.
Click Save Recurring Campaign.
Important! The IQA must have at least two fields (iMIS ID and Mobile Phone number). All columns must have the Alias field populated within your IQA. This field is then selected for Phone Number Column Name. Other columns can be included in the IQA for use in the SMS Message which will be described further below.
Important! If you did not Alias all of your IQA columns as mentioned above, these Merge Fields will not work correctly.
