Transparency alternatives to NextPhone
Other Conversational AI vendors we measure, sorted by how much we found at them and not at NextPhone. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from NextPhone on at least one criterion we measured for both. Public transparency score, not a product or security rating.
NextPhone has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at NextPhone” is the one that closes them.
| Vendor | Score | Found there, not found at NextPhone | Found at NextPhone, not found there | |
|---|---|---|---|---|
| MessageBirdbird.comSee also Transparency alternatives to MessageBird | 87/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | nothing | Compare |
| Forethoughtforethought.aiSee also Transparency alternatives to Forethought | 61/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Botpressbotpress.comSee also Transparency alternatives to Botpress | 57/100 | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Yellow.aiyellow.aiSee also Transparency alternatives to Yellow.ai | 55/100 | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | 1 Data location stated | Compare |
| Sinchsinch.comSee also Transparency alternatives to Sinch | 48/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| Sendbirdsendbird.comSee also Transparency alternatives to Sendbird | 65/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | nothing | Compare |
| Netominetomi.comSee also Transparency alternatives to Netomi | 48/100 | 3 Status page with history, No third-party tracking before consent, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Rasarasa.comSee also Transparency alternatives to Rasa | 48/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Tiledesktiledesk.comSee also Transparency alternatives to Tiledesk | 48/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Wotnotwotnot.ioSee also Transparency alternatives to Wotnot | 48/100 | 2 Notice before subprocessors change, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Infobipinfobip.comSee also Transparency alternatives to Infobip | 43/100 | 2 Data processing agreement, Status page with history | 2 Data location stated, Certifications named | Compare |
| Kore.aikore.aiSee also Transparency alternatives to Kore.ai | 30/100 | 2 Status page with history, Named privacy contact | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.