SMS-enable your business. Using iSMS, integrate with an SMS gateway of your choice and let your employees and customers interact with your systems via SMS.
Create your own Keywords
Create a custom menu/command structure that suits your needs.
Allows you to setup user-friendly, business-related commands and keywords.
For each command/keyword, define (optional) parameters.
Connect the command to one of the supported integration actions.
Test the command structure through a Web UI first, once the commands work as expected, activate them for SMS.
Commands can execute one or more steps/tasks.
Database integration
Interact with databases using SMS.
Use the database connector to connect to any SQL-Compliant data source.
Run commands, scripts, stored procedures to insert, update or retrieve data.
Return the data to the mobile phone via SMS.
REST API Integration
Interact with applications using REST API.
Integrate with any internal/external web service that uses REST API.
Supports single call or, dependent, sequential calls (using the Workflow option).
Allow users to interact with existing (REST) web apps/services.
Workflow-based Integration
Execute simple or complex sequence of actions triggered by an incoming SMS
Uses Microsoft Windows Workflow foundation.
Comes with a pre-defined set of Actions, new Actions can be added as needed.
Allows simple workflows that start and stop for each SMS request.
Create complex workflows that maintain state and are able to interact with users and take them through a series of steps.
Embed actions like email, SMS, REST API call, database call, authentication call, validation call, XSL transformations, string parsing etc. within a workflow.
Open or Authenticated Interaction
Not all commands are available to everyone – some are open, and some are not.
Commands can be categorized according to the sensitivity of the information they access.
Create “Open” commands – commands that are available to all users/SMS senders, no validation required. For e.g., Hours of operation – anyone can send a request and get an answer.
Create “Closed” commands – commands that require a user to be validated but not necessarily authenticated to retrieve information. For e.g., Product Availability – only valid users can send a request and get an answer.
Create “Secure” commands – Commands that require a user to be valid AND authorized to send the command. For e.g., Place an Order – only valid users that have the right to create an order can send a request and get an answer.
Custom Application integration
Have developers, will code.
Our engineers will provide specifications on how to create custom actions.
Using the specs, create custom actions that interact with your applications, databases etc.
