SMS - Same Day Registration Events

Using the SMS or MMS channels requires that targeted customers' profiles have the following attributes:

• MOBILE_NUMBER
• SMS_CONSENT
• SMS_VALID

The customer profile is typically updated as part of a batch process. This means that the attributes may not be available at registration time for realtime triggered campaigns.

In order to support this use case, you can add mobile_number to the event data (see Real Time (triggered) Campaigns). If the customer profile is not yet available, you must also add sms_consent and sms_valid to the event data. Otherwise the customer will not receive the SMS.

Logic - MOBILE_NUMBER

If the customer profile has a MOBILE_NUMBER, that number is used. If it doesn't, the MOBILE_NUMBER from the event data that triggered the campaign is used. If neither has one, the SMS is not sent.

Send a single MOBILE_NUMBER in the event data. If the event data contains more than one different number, which one is used is not guaranteed.

Logic - SMS_CONSENT / SMS_VALID

Consent and validity attributes are also supported in event data. The same logic applies to both SMS_CONSENT and SMS_VALID:

1. If the customer profile has the attribute, the profile value is used and the event data is ignored.
2. If it doesn't, the value from the event data is used.
3. If neither has the attribute, the customer is not sent to. Consent is never assumed.

A customer receives the SMS only when both SMS_CONSENT and SMS_VALID are true.

For same-day registrations the customer profile is usually not available yet, so include sms_consent and sms_valid in the event data whenever you capture them at registration. Without them, newly registered customers will not receive triggered SMS campaigns until their profile has been updated.

Accepted values: true / false or 1 / 0. Any other value is treated as not consented.