Design SMS Flows

An SMS flow represents a sequence of messages sent to the user through a mobile device. The user can interact, replying to these messages. In Service Studio, SMS flows are, in fact, interactive SMS (iSMS) flows.

In an iSMS flow you have a collection of the following elements:

Send Messages: dialogs used to interact with the end-user. How?
Entry points: start the iSMS flow with the end-user. How?
SMS screen references: link to SMS messages created in a different flow. How?
Connectors: link the elements in the iSMS flow. How?

There are also other elements that you can use in your iSMS flows. See the complete list of elements in a SMS flow.

In Service Studio, an SMS dialog is a sequence of messages:

Screens: are messages displayed to the end-user.
Commands: are the messages submitted by the end-user.

In iSMS flows, transitions can have commands associated. For example, the user receives a message with a question. Depending on the command given by the user, the eSpace flows to a different message. The transition between these screens has a command associated.

Each SMS Screen can be connected to more than one SMS Screen, Go To Screen or Wait For Message. An Application Phone must always be connected with to Wait For Message.

Remarks

SMS Flows are available in the following situations:

in .NET environments, specified by the Application Server eSpace property. If this property has the value J2EE or (both) a warning message is presented, notifying you that this type of flows is not implemented in a J2EE environment and will not be available at application runtime.
Message Queues Component is installed in your server. If this component is not installed, a warning message is presented and you should contact your Service Center administrator.