overall, I wonder how compliance to this SSO would look like—is there room to comply with SMS and payments, but not with Voice and USSD? Is it about a provider reaching a level overall and communicating that to potential partners? For NGO’s I’d probably go by use-cases: A provider certifies/complies that their API support a bunch of use-cases as defined by the SSO. That may make it easier for NGOs to decide on a partner. “High-level aggregators” like us (engageSPARK) would probably be more interested in just seeing which Core SMS services are being complied with, etc.
Re payments: Agreed, was also not sure why it’s missing, especially since airtime topup and reverse billing were mentioned. I’d probably move “airtime distribution” to the payments column for a start. And if it’s part of “payments” then it would be basic, right? (Is it core in terms of that category, or core in terms of NGO’s capabilities to run programs?)
USSD: I’m curious to hear from others how relevant that is going forward for the programs that NGOs launch.
Admin/Utility: I understand that “Message cost calculator” is something important to have, but does it need to be an API? If someone wants to launch a program, isn’t that a one-time UI tool? Similarly with “Message page count calculator”—why as an API?
Speech-to-text: What would compliance mean here? I’m wondering about the language diversity, and the capabilities to recognize something other than the most common languages in NLP toolkits (English, Spanish, Chinese, …) Looks like a can of worms. Omit?
Hosted flow/tree logic: From the subtext “(single asyncronous delivery on session close/timeout)” I read this as receiving after-the-fact notifications about what happened, in the SMS/Voice/USSD campaign, maybe via Webhook. Is this correct? If yes, where would one find behavior that allows to disburse airtime in response to completion of a survey? Is that logic part of “Reverse-billing” ?
“Specify # rings before pickup”: More minimal would be config to simply not pick up.
“automatic charset handling” is part of Core’s “String-based Two-way SMS”, but it’s also sort of a Recommended feature in “Automatic character substitution”? Maybe I’m misunderstanding?