Transparency alternatives to CallN
Other Contact centre vendors we measure, sorted by how much they publish that CallN does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from CallN on at least one criterion we measured for both. Public transparency score, not a product or security rating.
CallN has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and CallN does not” is the one that closes them.
| Vendor | Score | Publishes, and CallN does not | CallN publishes, and they do not | |
|---|---|---|---|---|
| Aircallaircall.io | 61/100 | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | 1 Uptime SLA with a figure | Compare |
| CloudTalkcloudtalk.io | 61/100 | 5 Subprocessor list, Public pricing, HTTPS enforced with HSTS, +2 | 1 Uptime SLA with a figure | Compare |
| Call Handling VCCcallhandling.co.uk | 43/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | 3 Data location stated, Certifications named, Uptime SLA with a figure | Compare |
| CallHippocallhippo.com | 59/100 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | 1 Uptime SLA with a figure | Compare |
| Puzzelpuzzel.com | 47/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 2 Certifications named, Uptime SLA with a figure | Compare |
| 2Chat2chat.co | 43/100 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 3 Data location stated, Certifications named, Uptime SLA with a figure | Compare |
| Nextivanextiva.com | 43/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 2 Certifications named, Uptime SLA with a figure | Compare |
| RingCentralringcentral.com | 43/100 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | 2 Data location stated, Uptime SLA with a figure | Compare |
| NICEnice.com | 39/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | 2 Data location stated, Uptime SLA with a figure | Compare |
| FreeClimbfreeclimb.com | 35/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 2 Data location stated, Certifications named | Compare |
| Diabolocomdiabolocom.com | 30/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 3 Data location stated, Certifications named, Uptime SLA with a figure | Compare |
| Talkdesktalkdesk.com | 26/100 | 4 Status page with history, Public pricing, security.txt (RFC 9116), +1 | 3 Data location stated, Certifications named, Uptime SLA with a figure | 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.