There are times that a critical message must be quickly delivered to inform a person about an important event. For example, a shipment of important medical supplies may have been delayed due to flight cancellations, and the person receiving the shipment must quickly decide if she can wait a couple days or would prefer to drive to a nearby city to pick it up sooner. She may have provided an email address as the primary means of receiving important notifications in addition to a mobile phone number as a secondary contact information. By law, the shipping company also may be obligated to ensure she does receive the message about her delivery.
Every month, the Oracle Responsys marketing platform delivers billions of personalized messages via email, SMS, and mobile push channels to millions of people worldwide. A large percentage of these messages are important transactional messages, e.g., purchase confirmations, shipment notifications, flight delays, password changes, and notifications about medical supply delivery, such as in our example.
These transactional messages are triggered using highly available Oracle Responsys Web Service APIs that help process and send such messages out quickly even if the customer’s primary Responsys account is out of service—for planned maintenance or accidentally due to system issues. This means the person from the example above would have received a notification via Oracle Responsys about the flight cancellation immediately, even if the shipping company’s account was down. It would comply with the law about her receiving the notification and given her more time to decide if she should wait or drive to pick up the shipment.
A failover Oracle Responsys account that is continuously synchronized with the primary account and is automatically activated when the primary account goes out of service helps to ensure that this message gets delivered. The incoming API requests to trigger messages (email, SMS, or mobile push) are immediately redirected to the failover account through an automatic service without any action required from the Oracle Responsys customer. Once the primary account is back in service, the API requests are automatically directed back to the primary account and all of the data collected in the failover account, such as updated customer records or interactions with messages, are replicated back into the primary account.
But what would happen if the person from the example above had an email inbox that was full or an email address that was no longer valid? Oracle Responsys continuously monitors the email messages that fail to reach their intended recipients and automatically and promptly notifies the sender through an API call-back with details about those failed email messages. For example, if the shipment change date notification bounces from its intended recipient’s inbox, the shipping company receives an API call-back about that specific email so that the recipient can be contacted by the shipping company via an alternate method like SMS, mobile push, or a phone call. She can then make plans regarding what she must do next to see that the delivery reaches its destination.
To find out more about Oracle Response, please visit us here.