(Means Interactive SMS. Represents an exchange of messages between the end-user and the application.)
Service Studio 5.1 Help
iSMS flow Initiated by the End User
The iSMS flow can be initiated by the end-user or by another flow. In the first situation, the iSMS flows starts when the end-user dials to application phone number.
In the flow canvas, you must use the following elements provided by Service Studio:
Application Phone: this is the entry point of the flow. How?
Represents a well-known telephone number that receives the commands from the end-user; and from which the messages originated in the application are sent. The application phone must be followed by a Wait Message element.
Wait for Message: supports the beginning of the dialog originated by the end-user. How?
This support is achieved by SMS commands. Service Studio provides a section in the Properties Pane where you can specify the accepted commands to start the dialogue.
If you want to access the properties of the message that was received, simply use a built-in action called InboundSmsGetDetails. How?
An iSMS flow initiated by the end-user looks like this:
Start an SMS Flow initiated by the end user
The Application Phone must always be connected to a Wait Message. If this destination has mandatory parameters that are not specified in the request, Agile Platform automatically uses the default values of the Service Studio data type. See Available Data Types.
iSMS Flow Initiated by Another Flow | Application Phone Properties | Wait for Message Properties