SMS MO Forwarding Feature Setup
With SMS MO Forwarding, customer requests and queries that are received as MOs are forwarded to respective businesses so they can respond to their customers with the latest information. It enables customer service scenarios that involve dynamically changing and sending sensitive information. Some examples would include dynamically changing information, such as a customer's flight status, and confidential information, such as a customer's bank account balance or bank account statement.
Setup
Raise a support ticket with My Oracle Support and include the following details:
- Your System’s endpoint URL for processing MO’s
- Oracle will make a HTTP GET call to this URL with following parameters, all of them strings:
- Mobile_code
- Keyword
- Mobile_number
- Message
- Oracle will make a HTTP GET call to this URL with following parameters, all of them strings:
- User Credentials: Username and password required to access the customer end point
- We use basic authentication for these calls
- Oracle Cloud recommendation is that you use CA authorized certification which can be recognized by any client (please confirm this on the ticket)
- Maximum traffic in terms of messages per second that the end point can accept and process
Failure Cases
If, given a valid campaign/program and active keyword, the customer system does not receive a MO from Oracle, these are some possible reasons:
- Keyword is not enabled for MO forwarding
- Program is in unpublished state, there by making keyword inactive
- Authentication issue: Please check if the username and password provided to Oracle are being honored
- Oracle’s outgoing IPs are not whitelisted
The Oracle system should give a XML response for each call containing 2 nodes, code and description. If the code value is 200, then it means it was successfully sent.
Limitations
Each account can have only 1 MO Forwarding URL. MO Forwarding is possible for dedicated short/long codes only – do not set up MO Forwarding on shared codes.