Cht-core: Scoping: Investigate IVR options

[ranjuts]

Potentially required for Remote CHW onboarding. Immediately relevant in Kenya (C-EBS national scale with MOH) and MOH Zambia.

Africa's Talking is a potential in Kenya esp given we support an integration with them already. Viamo needs to be explored in Zambia as Africa's talking does not provide IVR there. We have had initial partnership conversations with Viamo

Would be able to leverage the same providers in other countries (e.g. Viamo in Nepal, Uganda etc)

@shreyakb please add any further context that's helpful.

[MaxDiz]

Based on this cut-sheet, Viamo offers service in each of the locations mentioned: https://viamo.io/wp-content/uploads/2020/03/Viamo-Capabilities-Statement-Epidemic-Response.pdf

Twilio also offers service in some, but not all, locations: https://support.twilio.com/hc/en-us/articles/223183068-Twilio-international-phone-number-availability-and-their-capabilities

Any additional info you can provide on project deployment requirements and constraints would be helpful.

[abbyad]

Assigning myself as I have been having conversations with providers. It is possible that we won't have an IVR system that is compatible across all our deployment countries, so please add countries and deployment timelines to this issue.

[ranjuts]

I started this spreadsheet to keep track of requests but there are many unknowns. https://docs.google.com/spreadsheets/d/1AXvteiBp--OpuUdz4PuuKPyaKMY-yKvHgvcgHUOx8uE/edit#gid=0

[benkags]

Just had a chat with an Africas Talking Developer on an unrelated issue to do with CIHA and I brought up IVR. He recommends https://mteja.io/. It's a sister company to AT and they have been using it for their IVR needs internally instead of their own voice product.

I have not had a look into it yet but wanted to leave it here an an option we may want to explore.

[abbyad]

Thanks @benkags, will keep this in mind too!

Current countries of operation for Mteja: Kenya, Uganda, Nigeria, South Africa, Philippines, USA

[garethbowen]

@abbyad Can we remove this from 3.10.0, and either put it in 3.11.0 or track it separately from product releases?

[abbyad]

We are tracking it with releases for scheduling purposes. We are aiming to wrap up the investigation by the end of next week, so it should be fine to leave in 3.10 and will close ahead of the release.

[abbyad]

Some thoughts from the investigation are in this internal doc. I think this gives us enough to move forward and to close this issue.

@ranjuts please comment in the doc where additional info is needed, and any questions you may still have. We can create a new issue for any more IVR-related work.