OptiText SMS

Introduction to OptiText SMS

OptiText SMS is a powerful communication channel that enables businesses to engage with their customers through SMS and MMS messages. It is widely used for transactional alerts, promotional campaigns, and personalized customer interactions. To ensure effective message delivery and compliance with regulations, certain customer profile attributes must be present when using SMS or MMS channels.

Required Customer Profile Attributes for SMS/MMS

For SMS or MMS messages to be successfully delivered, customer profiles must have the following attributes:

• MOBILE_NUMBER – The recipient’s valid mobile phone number.
• SMS_CONSENT – Indicates whether the customer has opted in to receive SMS communications.
• SMS_VALID – Confirms that the provided mobile number is valid for SMS delivery.

These attributes are typically updated as part of a batch process. This means they may not be immediately available at registration time—especially for real-time triggered campaigns.

Supporting Triggered Campaigns for “Converted Today” Users

Sometimes, businesses want to trigger real-time SMS campaigns for newly converted users—customers who have just signed up but may not yet have all their profile attributes updated. Since customer profiles are typically refreshed in batch processes, the required SMS attributes might not be available at registration time.

To support this use case, you can include mobile_number in the event data of a real-time (triggered) campaign, allowing immediate communication with new customers. For more information on real-time (triggered) campaigns, see Real Time (Triggered) Campaigns.

Event Data Handling in Real-Time Campaigns

Logic – MOBILE_NUMBER

If the event data that triggers a real-time campaign includes a MOBILE_NUMBER, it will be used instead of the customer profile’s MOBILE_NUMBER if the latter is missing.

Handling Conflicting MOBILE_NUMBER Values

When both the customer profile and event data contain different MOBILE_NUMBER values, the system determines which number to use based on predefined prioritization rules. Below is an example flowchart illustrating how the system behaves when competing values exist:

Behaviour when competing MOBILE_NUMBER values exist between customer profile and event data.

Logic – SMS_CONSENT / SMS_VALID (Optional)

Event data can also include SMS_CONSENT and SMS_VALID attributes, though this is optional. The safest approach is to exclude these fields unless the data is reliably captured at registration time.

Handling Conflicting or Missing Consent Values

When conflicting or missing SMS_CONSENT or SMS_VALID values exist, the system applies prioritization rules to ensure compliance and best practices. Below is a flowchart illustrating how the system behaves when consent or validity values are competing or absent:

Behaviour when competing/absent consent values exist. Applies to both SMS_CONSENT and SMS_VALID.

Conclusion

By leveraging event data for mobile numbers and consent attributes, businesses can execute real-time SMS campaigns effectively—even for newly converted users who have not yet been fully onboarded into the customer profile system. Ensuring the presence of MOBILE_NUMBER, SMS_CONSENT, and SMS_VALID (via profile data or event data) is crucial for delivering compliant, successful SMS and MMS messages.