In your iSMS flow you can define commands to interact with the end-user and these commands must follow the SMS command pattern language. In the SMS Command section of SMS elements Properties Pane, you can type commands directly in the Pattern property, or use the drop-down list that contains some possible patterns. Together with the command you type you must define the Destination where that command is going to go.

The SMS elements that allow having commands are the ones that interact with the user. See more about Interact with the User.

The SMS command pattern language is made up of symbols and a command is a sequence of symbols.

Available symbols

When the command has a symbol of this type, a local text variable is created.

The Word symbol must be written as <word>.

Example: If you are expecting the name of a product that the end-user wants to order, you should use this command:

<word>

When the command has a symbol of this type, a local text variable is created.

The Number symbol must be written as <number>.

Example: If you are expecting a film number that the end-user wants to book, you should use this command:

<number>

This symbol must be placed at the end of the command list, otherwise an error is generated and the eSpace is not valid.

When the command has a symbol of this type, a local text variable is created.

The Sentence symbol must be written as <sentence>.

Example: If you are expecting a sentence from the end-user, you should use this command:

<sentence>

The keyword symbol in a command does not create a local variable.

Example: If you are expecting the end-user to indicate whether he/she wants to see the a news film you should use this command:

NEWS

You can have a multiple choice with a list of keywords separated by the vertical bar "|".

Example: You might want to support several keywords to get news about a video club, you should use multiple choice keywords:

news | new | n

When the command has a symbol of this type, a local text variable is created.

The Regular expression symbol must be written between parenthesis. The characters <>\() and must be escaped using the black slash \. For example if you want to match the string <CODE>in your regular expression, you have to escape the < and >:

(\<CODE\>).

Note: Regular expressions match is case insensitive.

Example:

(news|new|n)

([0-9A-F]+): matches a sequence of one or more numbers or letters.

([0|1]+): matches a sequence of 0 or 1.

When the command has a symbol of this type, a local text variable is created.

The site properties must be written as <site_property>

Example: In your multi-tenant eSpace there is a site property called TenantCode that for tenant 1 has the value Lisboa and for tenant 2 has the value Porto. If you want to use this site property in your command, you have to type:

<TenantCode>

This site property is instantiated in a back-office, in Service Center or elsewhere in your eSpace. When tenants are deployed, the value of TenantCode is (Lisboa) for tenant 1 and (Porto) for tenant 2.

The value of a site property can be a regular expression, allowing several tenants to share the same phone number.

Managing command local variables

The values matched with words, numbers, and sentences are stored in local variables, which are automatically created in the scope of the screen. These variables are named p1, p2, …, pn, according to the symbols in the command.

If the destination of the pattern command has input parameters, you may use these variables to pass information into the destination of the command.

Examples

See Also