Deliver Response Processing

From version 12.1.5, Deliver adopts a push model from On-Demand side so that reply messages arriving from WhatsApp and SMS from On-Demand server are pushed by Deliver to RCT as and when they appear. This significantly reduces data transfer between On-Demand and On-Premises because the responses will be pushed only when they arrive.

In the earlier versions, RCT was downloading responses of messages, sent via Unica Deliver and user interactions, to those messages, periodically, by polling OD dataapp server. This was not an effective model as response availability depended on the download frequency. Additionally, if there were no pending responses, RCT kept polling for responses resulting in bandwidth consumption and increase in load on OD dataapp server, which was responsible for serving responses to RCT.

Instead of the earlier mechanism, Deliver pushes these responses as and when possible. To effectively utilize resources like bandwidth and processing capabilities of downstream systems, the download frequency for different type of responses are as mentioned in the following points:

  • Message send events for all channels and responses for email channel uses the current configuration of 1000 responses or 10 minutes whichever is earliest to send them together to OP.
  • All type of delivery receipts for other channels, for example, SMS, WhatsApp, and Push are sent more often, like at an interval of 5 minutes, as these channels are more interactive.
  • Reply messages for SMS and WhatsApp are pushed to OP as soon as they enter the OD server. This ensures that conversations can happen without a signifcant delay.