Transactional Dialog Requirements & Recommendations

The important thing in a proper flow of the T-Dialogs is a quick, reliable and scalable server on your end. Without it, the T-Dialogs fail since you are an integrated dependency of the whole flow. So do monitor your base statistics and ensure elastic scaling. 

Also, do note that while we provide you with access to our platform, given our joint client, you do have to adhere to the client’s security and data privacy policies, as we do. There’s no way you cannot have potentially sensitive data that are part of a T-Dialog, and then still make it work; which means you have to do your bit.

Server and Webhook Recommendations

The important thing for you is a quick, reliable and scaling server. We have no control over the amount of T-Dialog activations that happen from the end-user and thus really depends on your project. 

Also, keep in mind that we might hit your server quite often: of each non-filled slot, we have to assess whether the user input fills a slot or multiple at the same time. So each slot that doesn’t have a set value, and has one of your Webhooks registered to it, will be called each time. Therefore, we advise some form of elastic scaling. 

For security reasons, we only accept SSL connections; 'HTTP' calls are not allowed. Ensure you have valid certificates on your end.  

Lastly: we have many concurrent interactions on our platform and cannot lock up the conversation waiting for your Webhook to return. We have to set a time-out to ensure there is no blocking, which is set at 300 ms.