Mobile settings allow you to control both outbound and inbound SMS communication. You can find the mobile settings under the 'System Settings' section in the Settings Module.
In this article, you will find information about:
Outbound SMS
In the Outbound SMS section, you can set the sender name recipients will see when they receive an SMS from you. You can set a sender name for both Staging and Production.
It's important to remember that if you allow you recipients to answer your SMS directly using inbound SMS, the sender name must be the SMS shortcode for your given country. You can always contact the Product Specialists in Agillic Support to find out the shortcode for your country.
Inbound SMS
Syntax for Keywords
The syntax of an SMS determines how inbound messages are interpreted. This might mean triggering Events or causing Person Data fields to update with some received content.
If you want to use this feature, you need to index the person data field that holds values for mobile numbers. It's important as this ensures that messages have a high enough performance to make sure all messages actually reach Agillic. Read more about how to apply an index to a person data field here
The Syntax: <keyword> <PERSON DATA> registers an Event (the keyword) and one or several Person Data fields. For example, we could register the keyword 'AGCANDY' at 1980 and configure the following syntax in 'Inbound SMS' settings:
AGCANDY PERMISSION
‘PERMISSION’ here is the name of a Person Data field. This would allow a recipient to send in the following message: ‘AGCANDY yes’, which would result in the value ‘yes’ being saved to the person data field ‘PERMISSION’.
The syntax for updating Person Data is, therefore:
In the example below, please replace the placeholder text with the relevant values.
Syntax - {KEYWORD} {NAME OF PERSON DATA}
Example - AGCANDY yes
You have to register an additional keyword for each syntax you wish to support.
Examples of Inbound SMS:
Person Data
| Syntax | Example of SMS | Change in Agillic |
| AGCANDY SATISFACTION | AGCANDY 5 | The Person data SATISFACTION is set to ‘5’ |
| AGCANDY EMAIL PERMISSION | AGCANDY me@agilliccandy.com yes | The Person data EMAIL is set to ‘me@agilliccandy.com’ and PERMISSION is set to ‘yes’ |
| AGCANDY FULL_NAME | AGCANDY Hans Christian Andersen | The Person data FULL_NAME is set to “Hans Christian Andersen” |
| AGCANDY FULL_NAME SATISFACTION | AGCANDY Hans Christian Andersen 5 | The Person data FULL_NAME is set to “Hans” and SATISFACTION is set to “Christian Andersen 5” |
| AGCANDY SATISFACTION FULL_NAME | AGCANDY 5 Hans Christian Andersen | The Person data SATISFACTION is set to “5” and FULL_NAME is set to " Hans Christian Andersen" |
Events
| Syntax | Example of SMS | Change in Agillic |
| To support events with no spaces | ||
| {blank} | AGCANDY update | If an event exists with the name 'agcandy', it is triggered, follow by the event ‘update’ being triggered for the recipient. |
| To support events with spaces | ||
| AGCANDY "email signup" | AGCANDY email signup | If an event exists with the name 'agcandy', it is triggered, followed by the event ‘email signup’ being triggered for the recipient, |
Using double quotes allows you to quote an Event which has spaces within the name such as "Hans Christian Andersen".
Events and Person Data
The Syntax: <keyword> * or <keyword> registers an event (the keyword) followed by another event or updates the Person Data pointing to the email address if the inbound SMS text can be recognized by a "@".
| Syntax | Example of SMS | Change in Agillic |
| Candy * PERMISSION | AGCANDY {name of event} yes | The event ‘{name}’ is triggered, and the value ‘yes’ is saved to the person data field ‘PERMISSION’ |
Agillic will recognise any value with an '@' as an email address and save it as the email address of the user. This can be more secure than using 'EMAIL' in a Syntax, as it would not allow invalid email addresses to save.
Update all matched recipients
When the same phone number links to two or more recipients, you can put a system in place to update all recipients with the same number simultaneously. If not checked, only one of the recipients will be updated.
Disable recipient creation
If you want to stop the system from creating new recipients when a mobile number doesn't exist, you need to check this setting.
Prioritise recipients without county code
By default, the system searches for recipients with country codes first when an Inbound SMS is received. If you check this setting, the system will prioritise recipients who do not have an international area code in their phone number.
Mobile Settings in Agillic
Comments
Can this article be improved? Please let us know, and we will update the article
0 comments
Please sign in to leave a comment.