Streams

Streams can be used to send template SMS Messages triggered by events.

Overview

Implementing the sending of SMS messages with a stream is very similar to web push notifications. There are two new additions to streams related to SMS: the "Has SMS Subscription" condition and the "Send SMS Message" action.

Has SMS Subscription Condition

This stream condition is very similar to "Has notification subscription" and "Has email subscription". If the user is currently actively subscribed to SMS, the "Has SMS subscription" will be true. An active subscription requires the user to have responded affirmatively to the initial opt-in message.

Send SMS Message Action

This stream action will start the send process of the selected template SMS message. This action will always check the subscription status of the user to make sure he or she is subscribed (see note below). Under normal conditions — as in no heavy message load on the system — the SMS message should be sent within a few seconds of the trigger firing.

Only template SMS messages that are active can be sent by a stream, though streams can be created with either active or paused messages. An error will show in the action if the currently selected message is paused or inactive (deleted).

Important: Fanplayr recommends that the "Send SMS Message" always be paired with the "Has SMS Subscription" condition. This is not strictly required because the send process will always check that the user is subscribed, but adding the condition will provide clearer stream data to insights, as all of the stream nodes are logged in insights.

Example Stream Flows

Abandoned Cart

• Event: Session Expiry

• Condition: Has SMS Subscription

• Condition: Abandoned Cart Value > 0

• Action: Send SMS Message (template)