Evaluate Turn - Githubissues

Things to Evaluate

A conversation builder or support on conversation building - is that node based UI we have previously worked with. With turn we have to see do they offer something better or atleast as good as what we had previously. One of the issues with prev journey builder had was that the process to import journeys from the staging account to production account was manual. Which defeats the whole purpose of creating a journey in staging. So we'll see how better turn is at this.
A unified view of all the messages being sent and received from the user, regardless of which API is used - What we want is a centralised view of every message sent by the user and tattle, and their delivery status. It should not matter whether i used API a or API b to send message. If a message is going in and out of our whatsapp account, we need to be able to audit it.
Customer Support Quality - response time, response quality
documentation quality and ease of navigation etc
Check the developer/user experience with Templates - prev BSP template API requires us to match the string exactly!!! as opposed to provide a template id and variables as payload. I would be surprised if turn also has the same string based requirement. but yeah lets evaluate how easy it is to whitelist a template and then incorporate it into our codebase.

We are working with Sandboxes, they are prototyping accounts that have most of the functionality of a live WhatsApp line so you can iterate and test seamlessly. To send a message to a sandbox whatsapp line, send join to +27600136875.

using templates is not allowed in a sandbox account
read the documentation, defining the templates with a variable is same as what it was in gupshup - {{1}}
a template can also have button when we send it (even from code)
TODO - check if a template message sent to a user can be seen in the chat part of the Turn dashboard.