SMS: Doing a test run

This task pertains to using HCL Campaign to send SMS text messages from HCL Engage. It is important to do a test run before committing to a production run.

About this task

A test run is extremely important because it is your opportunity to confirm that the text message is properly configured before you deliver it to customers. Never do a production run without first doing a test run.

Typically, you do a test run after you finish configuring the SMS process in an HCL Campaign flowchart.

The purpose of the test run is to confirm connectivity between Campaign and Engage and to spot-check several text messages in HCL Engage. For example, if you used HCL Campaign to override the Subject line in the SMS template, you must confirm that the correct substitution was made.

A test run in Campaign never sends production SMS text messages to customers, even if Send SMS to all contacts immediately (in the SMS configuration dialog) is checked.

Important: See the HCL Marketing Cloud documentation for complete information about doing SMS test runs. This topic covers only a small portion of the process (testing from HCL Campaign to HCL Engage).

Procedure

Use HCL Campaign to open the flowchart (in Edit mode) that contains the configured SMS process.
Limit the test run to just a few records. You will remove this restriction later, after the test run is complete.

Note: This step is recommended but not required.

If you do not limit the test run, the entire contact list is sent to HCL Engage during the test run, which is unneccessary and time consuming.
1. Double-click the process box that provides input to the SMS process. For example, if a Select process is connected to the SMS process, open the Select process configuration dialog.
2. Select the Cell size limit tab.
3. Use the Limit output cell size option under Test run output cell size limitations to restrict the number of records. Typically, 5 or 10 records are sufficient for a test run.
Save the flowchart.
Open the Run menu and use one of the Test run options to do a test run of the flowchart, branch, or process.

The contact list is sent to Engage but no texts are sent (regardless of whether Send SMS to all contacts immediately is selected).
In HCL Engage, use the Test Mailing feature to send a test SMS and confirm that the text content and contact list are correct. A test mailing is typically sent to a "black hole" address or an internal marketing address.
Confirm that all of the selections that were made in HCL Campaign are accurately reflected in the test text message. For example:
- Confirm that the Engage contact list includes all of the expected fields from HCL Campaign.
- Confirm that the contact list was either created or updated, depending on which selection was made in Campaign.
- Confirm that the test send was saved in the correct folder on the Sent tab in Engage.
Follow all of the instructions in the HCL Marketing Cloud documentation to confirm that the SMS text message is properly prepared.

For more information, read about SMS text messaging in the HCL Marketing Cloud documentation: http://www.ibm.com/support/knowledgecenter/SSTSRG/SMS_-_Silverpop_Mobile_Messaging.html?lang=en.

What to do next

If you encounter any errors, resolve them and then do another test run. When you are satisfied with the test run results, you are ready to do a production run. See SMS: Doing a production run.