MO

Definition:
MO messages, short for "Mobile Originated" messages, refer to messages initiated by mobile phone users and sent to dedicated shortcodes or long code numbers using specific keywords. These messages are a way for customers or subscribers to interact with vendors or applications.

Process:
User Initiation:
A customer/subscriber sends a text message with a specific keyword to a dedicated shortcode or long code number.

Example:
Sending the text "Cars" to the shortcode 57547.
 
Message Routing:
The message is routed to the respective application or vendor associated with the shortcode or long code.

Key Points:
MO messages enable two-way communication between users and applications/vendors.

Specific keywords are used to trigger actions or responses.

Dedicated shortcodes or long code numbers are assigned for MO message reception.In summary, MO messages facilitate user interaction and engagement by allowing them to initiate communication with applications or vendors through simple text messages.

 HTTP MO Handlers Configuration Guide:
 Overview:

HTTP MO Handlers in iTextPro are essential for receiving incoming Mobile Originated (MO) messages from various vendors. The payload structure may vary between vendors. Follow these steps to configure the MO handler.

Step 1: Adding a New Handler:

Click on the "Add New Handler" option to initiate the configuration process. You will encounter the following options to map payload parameter names.
 

Prerequisites:
Basic knowledge of Restful API concepts is necessary for successful configuration.

Example Configuration:
Consider the scenario where you've acquired a long code (MO) from a vendor like Airtel. The payload received from Airtel looks like this:

Vendor Payload:

{

   "originatorAddress": "999563256",

   "destinationAddress": "8754321565",

   "messageContent": "BINGO 101",

   "CustomerId": "669912"

}

 iTextPro Configuration:
 Configure the local endpoint for your vendor with the following details:

Method: POST HTTP/1.1
 Content Type: JSON
 Payload Configuration on iTextPro Side:

Method: POST
 Content Type: application/json
 Originator Payload Key: originatorAddress
 Destination Payload Key: destinationAddress
 Message Payload Key: messageContent
 
 Explanation:
 The "Method" and "Content Type" on the vendor side and iTextPro side need to align.
 Specify the local endpoint for your vendor.
 Map the payload keys to iTextPro parameters:
 Originator Payload Key: Map to "originatorAddress"
 Destination Payload Key: Map to "destinationAddress"
 Message Payload Key: Map to "messageContent"

By configuring these parameters correctly, iTextPro can effectively handle incoming MO messages, allowing seamless integration with different vendors.

 Step 2: Configuring MO Services for User Account

 In this step, we guide you through the process of configuring MO services for a specific user account.
 
Navigate to the User Account:
To start, log in to the iTextPro platform and locate the specific user account to which you want to allocate the MO number.

Activate MO Services:
Within the user account, find the "Manage Services" section. Ensure that the MO services are activated to enable MO functionality for the user.

 Configure MO Number and Keyword:
 Access the MO option and click on "Add Keyword" to initiate the configuration process.

End Date: Specify the validity period for the assigned long code/short code number. This ensures control over the duration of use.

Select Channel: Choose the specific MO long code/short code number from the available options.

Keyword: The keyword is crucial for identifying user actions or services requested. Select the appropriate keyword from the list or use '*' to allow all keywords.

Status: Activate the configured number by setting the status to 'active.' This ensures that the MO number is ready for use.

Click "Add" to save the configuration for the user account.

Step 3: MO Routing Rule Configuration

This step is vital for efficiently managing incoming MO traffic through the creation of routing rules.
 
 

Access MO Routing Rule:
 Navigate to the MO Routing Rule option within iTextPro, where you'll find tools to manage the flow of MO traffic.

View/Edit Existing Rules or Create a New Rule:
 
 

Explore existing rules or create a new one with detailed parameters:

General Parameters:
Rule Name: Assign a descriptive name for easy identification.
 
Start Date & End Date: Set the validity period for the MO rule.

Gateway Interface:
Gateway Handler: Choose between HTTP or SMPP gateway handler based on specific requirements.
 
Condition:
Originator: Configure rules based on the source address.
Destination: Set up rules based on the destination address, such as MO channel number.
Message: Define rules based on the message or keyword.
Select User and Corresponding Endpoint:
 
 User: Choose the user account for routing.

User Interface Type: Select downstream HTTP webhook or ESME account based on your needs.

No Manual Restart Required:
 A notable advantage is that no manual restart or reload is required after creating or updating any routing rule. This ensures seamless integration and updates on the fly.
 

User Interface Interaction:
This section explains how users can interact with the iTextPro interface to monitor and manage incoming MO hits.

Impersonate or Login:
Users can either impersonate or directly log in to the user account where MO hits will be monitored.

Navigate to MO Module:
Access the MO module within the user interface to gain insights into incoming MO hits on the respective long code/shortcode number, conveniently displayed in the inbox.
 

Keyword Details:
 Here, users can obtain more detailed information about the allocated long code/shortcode number.
 
 

Clicking on the keyword option provides visibility into the specifics of the allocated long code/shortcode number, including information about its validity period.

Auto Reply:
Users can set up an automated response to be sent to the mobile number after receiving an incoming MO hit. This feature enhances user engagement and provides a quick acknowledgment to user actions.

Notification Settings:
 This section outlines the notification settings available for users:

Email Forwarding:
Users can receive email notifications for incoming MO hits, ensuring timely awareness and response.
 

 Mobile Forwarding:
 SMS notifications for incoming MO hits can be configured, providing an additional notification channel. Users should ensure that the mobile number is entered with the correct country code for accurate delivery.
 
 

Manage Sub-keyword:
In this detailed section, users can explore the intricacies of managing sub-keywords for enhanced user interaction:

Definition: Sub-keywords are secondary words following the main keyword, separated by a space.

Example:

Main Keyword: CAR
Auto-Response: "Thank you for joining! Was our service beneficial for you? Please reply YES or NO."

Sub-keyword 1: YES
Auto-Response: "Thanks for your feedback. We look forward to seeing you soon!"

Sub-keyword 2: NO

Auto-Response: "Thanks for your feedback. Please get in touch with our support team on 6584XXX…!!"

This comprehensive breakdown provides users with an in-depth understanding of the MO configuration process in iTextPro, empowering them to manage MO services, routing rules, and user interactions with precision and efficiency.

Reports: Export MO Reports in Excel Format

The Export Report feature in iTextPro empowers users with the ability to download MO (Mobile Originated) reports in Excel format. This feature provides flexibility by allowing users to customize reports based on keywords and sub-keywords.
 
 

Steps to Export MO Reports:
Access the Reports section in iTextPro.
Utilize the Export Report feature.
Download MO reports in Excel format.
Customize reports based on keywords and sub-keywords as needed.
 
This functionality enhances the user experience by providing detailed insights into MO activities in a format that suits individual requirements.

MO Webhooks: Real-time MO Notifications
 iTextPro offers the MO Webhooks feature, enabling real-time notifications for MO transactions through HTTP Web push. Users can configure a webhook URL to receive instant copies of MO transactions.
 

 Configuring MO Webhooks:
 Ensure that the parent account has enabled the HTTP Web push option.
 Access the MO Webhooks section.
 Configure a webhook URL for real-time MO notifications.
 
 

Important Information:
Webhook Availability:
If the remote web server is unavailable during the transaction, the MO will be discarded.
 
Timeout Period:
The default timeout for webhook requests is set at 10 seconds.
 
Adding a New Webhook:
Click on "Add New Webhook."
Configure the following details on the displayed page:
Name: Provide a friendly name for the HTTP Webhook URL.
 
Endpoint Base URL: Configure the base URL of the HTTP webhook, excluding other parameters.
Method: Specify the method of sending a request to the HTTP Webhook URL (GET or POST).
Handler: Choose the handler as MO based on your requirements.

Note: Parameters may vary depending on the selected handler.

This comprehensive documentation guides users through the seamless process of exporting MO reports and configuring MO Webhooks in iTextPro. Whether customizing reports or setting up real-time notifications, these features contribute to a more informed and efficient user exper