To ensure seamless integration with WordFly's SMS functionality, Tessitura customers need to configure their system to process SMS-specific responses: hard bounces, soft bounces, and unsubscribe (STOP) messages. This involves setting up new response types and updating processing workflows to handle SMS data appropriately.
Step 1: Create SMS-specific response types in Tessitura
Define new response types in Tessitura to distinguish SMS responses from email responses.
-
SMS Hard Bounce
-
Purpose: Identify invalid or unreachable mobile numbers.
-
Suggested Code:
SMS_HARD_BOUNCE
-
-
SMS Soft Bounce
-
Purpose: Flag temporary delivery issues (e.g., carrier errors, message queue timeouts).
-
Suggested Code:
SMS_SOFT_BOUNCE
-
-
SMS Unsubscribe (STOP)
-
Purpose: Record when a subscriber texts "STOP" to opt out of SMS communications.
-
Suggested Code:
SMS_UNSUBSCRIBE
-
Ensure these response types are added to the TR_RESPONSE table and appropriately mapped in TR_EMAIL_RESPONSE_CODE
Step 2: Map WordFly SMS responses to Tessitura response types
Coordinate with the WordFly team to map incoming SMS response codes to the newly created Tessitura response types. This ensures that SMS responses are accurately recorded and processed within your Tessitura system.
Step 3: Update processing workflows
Modify your existing processing workflows to handle SMS responses distinctly from email responses. This may involve updating stored procedures or automation scripts to process SMS-specific response codes and update subscriber records accordingly.
-
Unsubscribe Handling
Ensure that SMS unsubscribe responses update the subscriber's SMS preferences without affecting their email preferences. -
Bounce Handling
Configure the system to manage SMS hard and soft bounces appropriately, such as flagging invalid numbers or scheduling retries for temporary issues.
Step 4: Test the configuration
Before deploying SMS campaigns, conduct thorough testing to verify that SMS responses are correctly received, mapped, and processed within Tessitura. This includes sending test messages and confirming that the corresponding responses update subscriber records as intended.