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