SMS Actions

From Triangle Wiki

Jump to: navigation, search

Contents

Introduction

The SMS Module processes incoming messages via a set of user defined service actions. These actions are put in place within the SMS Admin. Clicking on the Cog to the right of the service name will bring up a list of existing actions (which can be edited / deleted) and an element to create new actions.

There is no limit to the amount of Actions a service can have. For instance stacking multiple Send Message actions can allow the client to bill a far greater amount, or send more more information.

It is important to understand that most of the actions are only initiated when the customer sends a message into the service. This is the trigger for the actions.

Actions List

  • [AS] Already Subscribed
  • [DR] Delivery Report Forwarding
  • [FE] Forward To Email Addresses
  • [FS] Forward To Mobile Numbers
  • [MC] Mobile Content
  • [MX] MX Telecom Forward
  • [SC] Static Content
  • [SM] Send Message
  • [SR] Spend Reminder
  • [ST] Service Stop Message
  • [WA] Watershed Messages
  • [WP] WAP Push

[AS] Already Subscribed

If a user tried to sign up to a service that they are already a member of, you can set this action to send the customer a message back informing them of this fact. The system already has a safe guard for this in the form of the Multiple Sign ups check box in the service configuration, but this will only silently fail the sign up request of the user.

[DR] Forward Delivery Report

When a delivery report comes into the system and is matched against a service that has the [DR] action it will forward this delivery report to the URL specified when the action is created.

[FE] Forward To Email Addresses

Great for debugging the system, or checking on throughput, set any number of email addresses to push the incoming message to.

[FS] Forward To Mobile Numbers

Process the message and forward the message onto any number of mobile handsets. This can be used to broadcast a simple message such as an alert to company staff. Or can be used to broadacast a message to your member pool.

For example if you are a tipster and are on the move, simply SMS in and we will forward this message to your members.

[FU] Forward To URL

If you would like the entire incoming message and contents forwarded onto a specific URL then this action will accommodate that. It will forward the SMS Message; User CLI and Network.

Within the actions menu

[MC] Mobile Content

Activate this action to automatically send the Triangle mobile content. The user message is automatically processed to find the correct handset and reference number for the content.

[MX] MX Telecom Forward

To forward the messages back into some of the MX Telecom applications.

[SC] Static Content

Static content basically allows a keyword to be extended by utilising a unique 4 digit reference. Content is uploaded through the administration actions interface.

The user would send in a message such as [PROPERTY 1234]; the system would find the keyword PROPERTY and then process the allocated actions. When the system processes the Static Content action it will look within the Static content table for the matching reference number, when matched it will send the user the message stored against this reference.

To add static content please follow these guidelines.

  • Firstly create a Static content action by clicking on the 'Cog' to the left hand side of the service name.
  • Select Static content from the service actions menu.
  • Complete the form to allocate a static content action to this service.
  • When this has been completed a new action should appear within 'Existing Service Actions'
  • To the right hand side of the static content action is a View icon (Picture). Click this to view the list of reference numbers and messages allocated. At this the list should be empty.
  • Within this screen you may add / edit or delete the static content. To Add simply click the 'Plus' icon to the right hand side of the 'View Static Content For Service ID' title.
  • Add in a unique reference number and messages each time.

[SM] Send Message

Select this action to instruct the system to send a reply message back to the customer. This is usually employed to send a greeting for the service, but can be utilised to send competition questions and notices; passwords / pins for access to sites. Messages of this type are logged [KEYWORD]HI.

[SR] Spend Reminder

ICSTIS require that any premium service sends out spend reminders to their customers. The interval of these are every £20. The message should include instructions on how to stop the service. The system does this automatically and sends out a stock spend reminder message, to override this message please add this action to the service. You may add more than one of this action, the system will then send a randomly selected message from the spend reminder actions you add.

[ST] Service Stop Message

ICSTIS require all services to have an automatic STOP mechanism, the Triangle admin processes STOP keywords, and ceases any services the user may be signed up for. If the incoming message consists of STOP and a KEYWORD i.e. STOPPROPERTY or STOP PROPERTY then the system will only stop the PROPERTY service and leave any of the other users services intact.

[WA] Watershed Messages

The watershed action is unique to the Triangle system, it involves the process of sending out messages that have already been sent out by the client, that have not expired past a pre-defined time. These are commonly Tipping advice messages, with the expiry date being the time of the race, event or match.

A user would text in HORSERACE thus sigining them up to the horse race service. If the client has already sent the tipping advice for that day, but the race has not been completed yet then the system will send the user this advice plus the standard welcome message.

[WP] WAP Push

Send a WAP push to your customers.

External Links

Retrieved from "http://wiki.triangle-solutions.com/index.php/SMS_Actions"
Personal tools