What are the 'Classic' FrontlineSMS Activities?

The 9 FrontlineSMS Activities below have for 10 years provided our messaging community with the powerful tools to save money, reach more people and scale their projects.  They are introduced below each with a link to more detailed descriptions.  All Frontline subscriptions include use so check them out with a free trial if you haven't already!

New_Actvities.png

The Classic Activities selection grid in a workspace at https://cloud.frontlinesms.com

1. Autoreply to SMS

The simplest and often most powerful activity.  This activity allows you to reply to all received SMS with a pre-compiled reply.  You can use the contact’s name in the reply, and importantly you can restrict the SMS to only be sent in reply to incoming SMS that start with or contain certain keyword(s). Example: HELP, CHECKIN.   

2. Autoreply to Missed Call (requires FrontlineSync connection)

 

 New as of December 2014, this works in the same way as above but without the option of keyword.  Hugely powerful when thinking about getting new users engaging with the system for the first time. Example: HELLO, INTRO

3. Autoforward SMS

Another simple activity, when an SMS arrives, optionally check its content for keywords and based on that forward the content of the SMS to a list of predetermined recipients.  This can be useful for managing certain messages without needing to check in to the Frontline workspace. Example: More powerful auto reply, URGENT, EMERGENCY 


4. Autoforward Missed Call (requires FrontlineSync connection):

As with the autoforwarding of SMS this activity sends out a message to a set of recipients when a Missed Call is received.  Of course there is no message to forward so the contents of the message would refer to the fact that a Missed Call has been received, and can include the name of the caller if that is known. Example: Voting 


5. Subscribe to group via SMS

 Managing subscriptions to groups is something that benefits from being automated.  If users are adding and removing themselves from groups as they need then all you need to worry about is using those groups in whatever processes you are running.  Simply use the group members as they are when you need them and trust everything is up to date!Incoming SMS can be checked for keywords set by you that perform the particular join or leave group action.  Add top-level keywords to allow the management of more than one set of groups/subscriptions. Example: newsletter, working this week


6. Subscribe to group via Missed Call (requires FrontlineSync connection)

Set up a group management subscription service based purely on free flash calls!  Simply decide whether a registered Missed Call subscribes (adds) a user to a group, unsubscribes (removes) them or simply toggles their membership.  This can be used in combination with an SMS subscription make the process easier for participants. Example: Flash to Join 


7. Poll; run a simple survey

Our most complex Activity allows you to run simple survey type ‘poll’ questions.  Find out which one of a set of options your participants vote for!  Run a multiple choice survey with any number of options and aliases for each option.  Set top level keyword to enable the running of multiple surveys.  Use in combination with Autoreply Activities to thank participants and/or link them to another question. Example: Multiple choice question.


8. Forward to URL

This Activity enables you to set up an outbound API integration from your Frontline workspace  to an external web application. This type of set up pushes your incoming SMS data to the integrated web application.  A common web service used with this type of Activity is Ushahidi's Crowd map service. 


9. Send SMS from a Web Service

This Activity enables you to set up an inbound API integration from an external web service to your Frontline workspace. This set up pulls SMSs from the integrated web application to your Frontline workspace and queues then to be sent out to the designated Contacts or groups. 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk