mPulse SMS

Overview

The following channel-specific fields are shown for mPulse mobile channels.

General tab

Re-subscribe contacts: allows you to re-subscribe contacts who have at some point previously opted out from receiving communications via the channel. By doing so, you may once again begin sending them mobile communications.

Invocation of Re-subscribe contacts displays the Re-Subscribe Contacts dialog, which contains the following:

Label: “Specify the list of contacts to re-subscribe to this channel”.
Add new Phone Number: invocation adds a new, blank phone number to the list.
Copy list of Contacts to clipboard: this button is available when at least one row is present in the email address list. Invocation copies the list of email addresses to the clipboard. Blank values are ignored.
Paste list of Contacts from clipboard: selecting this button displays a submenu exposing the following options:
- Replace Existing Values: selecting this option replaces the list of displayed phone numbers with the contents of the clipboard. Duplicate values are not pasted.
- Add to Existing Values: selecting this option appends the contents of the clipboard to the list of phone numbers. Duplicate values are not appended.
Clear all Phone Numbers: invocation of this option removes all phone numbers from the list and closes the dialog. It is not protected by an “Are You Sure?” dialog.
Phone number list: you can specify one or more phone numbers that you wish to re-subscribe in the list. A button is shown to the right of a list entry:
- Remove: invocation of this option removes the current list entry. An “Are You Sure?” dialog is not shown.
Create job to re-subscribe these Phone Numbers: this button is shown at the bottom right of the dialog and is only displayed when one or more phone numbers are listed. If one or more list entries are blank at invocation, a warning message is displayed. Selecting the button creates a Re-subscribe contacts job and displays it in the My Jobs Dialog. Full details of the job and Dialog can be found in the My Jobs documentation.
Cancel: this button is shown at the bottom right of the dialog and is always available. Invocation closes the dialog without re-subscribing email addresses.

Channel Specific tab

Recipient phone: this attribute defines the field in which a contact’s cellphone number is stored. Provision of Recipient phone is mandatory, and the attribute’s data type must be string. You can browse for an attribute using the recent items chooser or File System Dialog. You can also drag an attribute from the toolbox and drop it directly onto the field. Once selected, you can clear the attribute, or view its details in the File Information dialog.

Service Credentials

The following properties are exposed within the Service Credentials section:

API Service URL: this mandatory text property defaults to the value https://ms-api.mpulsemobile.com/. It can be a maximum of 500 characters in length, and represents the API service URL used to connect to the mPulse service.
Username: this mandatory text property accepts a maximum of 100 characters. It allows you to specify a username to be used to connect to the mPulse service.
Password: this mandatory, password-masked text field accepts a maximum of 100 characters. It allows you specify a password to accompany the supplied username.
Account ID: this mandatory text property accepts a maximum of 100 characters. It represents the account ID that will be used to connect to the mPulse service.
Audience List ID: this combo box field is accompanied by an Add button, which allows you to specify one or more audience list IDs. Each can be a maximum of 100 characters in length, and represents an Audience list ID in the context of which all uploaded contacts will be grouped together. Specification of an audience list ID is mandatory.
Event name: this mandatory text property accepts a maximum of 100 characters. It represents the event name that will be used to send mPulse SMS messages.
Content attribute: this mandatory text property accepts a maximum of 50 characters. It represents the custom attribute name that will be used to render SMS content for each subscriber.
Mobile phone: the mobile phone number used to test connectivity to the mPulse service.
Max. list upload batch size: the maximum number of message recipients that can be uploaded to an mPulse audience list in a single batch For each, properties such as Phone Number, Customer Key, First Name and Last Name are uploaded. The property defaults to 50.
Max. event upload batch size: the maximum size of a batch of personalized subscriber content that can be uploaded to mPulse. The property defaults to 2000.
Enable asynchronous list upload: if this checkbox is checked, the action of uploading subscribers to an mPulse audience list will be carried out in asynchronous mode.
Enable asynchronous event upload: if this checkbox is checked, the action of uploading personalized subscriber content will be carried out in asynchronous mode.
Max send threshold: this numeric property defaults to 10, and accepts a range of values from 1 to 10. It represents the maximum number of concurrent send operations that can be executed for a batch of email campaigns.
Ignore HTTP 400 error: if this checkbox is checked, any HTTP 400 errors received from mPulse when uploading member lists will be ignored.
Request timeout: a time period, in seconds, for which RPI will wait to connect to the mPulse service before timing out. The property defaults to 120.
Event upload status timeout: this integer property defaults to 10, and accepts a range of values from 0 to 30. It represents the period (in minutes) for which RPI will wait for an event upload status call to complete.
Event upload confirmation timeout: this integer property defaults to 24, and accepts a range of values from 1 to 120. It represents the period (in hours) to retry checking for event upload status completion.
SMS send retention period: this mandatory numeric property defaults to 30, and accepts a range of values between 0 and 90. It represents the number of days for which channel fulfillment activities will be processed.

Suppressions

The following properties are exposed within the Suppressions section:

Auto-suppress: this checkbox, checked by default, controls whether the system should automatically suppress (i.e., not send mail to) any individual whose email address is registered in the email suppression table (as defined by system config setting EmailUnsubscribersTable).
Custom suppression table: checkbox, default unchecked. This field allows you to specify that the email channel is to use its own custom suppression table, rather than the default email suppression table (defined by system configuration setting EmailUnsubscribersTable). Checking the field toggles on Suppression table name.
Suppression table name: this text field is available and mandatory when Custom suppression table is checked and can be a maximum of 50 characters. Any characters entered must be database-valid. When a contact elects to unsubscribe from email communications received via a channel using a custom suppression table, his or her email address is stored in that table. Any other email channels remain unaffected, so emails could still be sent using those mechanisms.

Callback Service

This section contains the following:

Callback service URL: URL of service used to process incoming SMS events.
Event upload content queue path: path of the queue to which event upload content will be sent.
Member list import timeout: the period, in minutes, for which the member list import will wait to complete.

Web Adapters tab

All types of web adapters are supported.

Advanced tab

Enable trace: this checkbox is unchecked by default. When checked, API requests and corresponding replies from the SMS service provider are logged. At execution of an SMS offer in an interaction workflow, or a channel synchronization job, if checked, all requests made to mPulse are logged.

This feature should be used only when troubleshooting to avoid logging an excessive amount of data to the database. A message displays when Enable trace is selected, which states “Enabling this option can impact performance and potentially persist PII data within the trace data”.

No. of days fulfillment active: this numeric field overrides the default number of days a channel fulfillment activity remains active.

Persist import state data: this checkbox is unchecked by default. If checked, import state data will be persisted on a data table.
Import state data table name: this property specifies the name of the import state data table.