How Activities work, an introduction to Automation

Activity_overview_small.png

Frontline’s automated Activities work with two essential elements; something that triggers them, and some action that it executes.  Along with the basic naming extras, these are the two key things that an Activity needs to be run.  Everything else is optional.

More complicated Activities, in addition to their triggers and actions, have conditions/restrictions  and other options.  These conditions and options are sometimes very specific to the Activity, for example ‘Which Group to add the user to when they Subscribe’, or very general, for example ‘Send all SMS actions that this Activity executes through this Connection’.

Whenever an incoming event occurs in your Frontline workspace, it could trigger an Activity.  The basic set can be triggered by receiving an incoming Missed Call, or an incoming SMS.  Each Activity will assess this object and execute its actions based on its criteria.

For example, assume there exists an 'Autoreply to SMS’ Activity that has had the keyword restriction option 'SMS Messages that contain the specified keyword(s)’ selected, and a keyword entered of ‘Autumn’.  This means that the contents of the activity’s auto reply text will be sent in reply to any incoming SMS that contains ‘autumn’ or ‘Autumn’ or ‘AUTUMN’ anywhere in the SMS's text.

An Activity can be disabled at any time so that different activities can be kept and managed so that certain activities can be manually switched off and on depending on when they are needed.

Once the activity is enabled, configured and left the workspace can then be left to automatically execute actions whenever matching triggers are received.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk