Transparency alternatives to Call Handling VCC
Other Contact centre vendors we measure, sorted by how much we found at them and not at Call Handling VCC. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 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 6 gaps in what we could measure: Data processing agreement, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Call Handling VCC” is the one that closes them.
| Vendor | Score | Found there, not found at Call Handling VCC | Found at Call Handling VCC, not found there | |
|---|---|---|---|---|
| Aircallaircall.ioSee also Transparency alternatives to Aircall | 70/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| CallHippocallhippo.comSee also Transparency alternatives to CallHippo | 59/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 3 Subprocessor list, Status page with history, Named privacy contact | Compare |
| RingCentralringcentral.comSee also Transparency alternatives to RingCentral | 43/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 4 Subprocessor list, Data location stated, Status page with history, +1 | Compare |
| Enreachenreach.comSee also Transparency alternatives to Enreach | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Subprocessor list, Status page with history, Public pricing, +1 | Compare |
| CloudTalkcloudtalk.ioSee also Transparency alternatives to CloudTalk | 61/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Talkdesktalkdesk.comSee also Transparency alternatives to Talkdesk | 48/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Subprocessor list, Notice before subprocessors change | Compare |
| JustCalljustcall.ioSee also Transparency alternatives to JustCall | 43/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| NICEnice.comSee also Transparency alternatives to NICE | 39/100 | 2 Data processing agreement, Certifications named | 3 Subprocessor list, Data location stated, Status page with history | Compare |
| Babelforcebabelforce.comSee also Transparency alternatives to Babelforce | 30/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 5 Subprocessor list, Status page with history, Public pricing, +2 | Compare |
| CallMinercallminer.comSee also Transparency alternatives to CallMiner | 30/100 | 2 Certifications named, HTTPS enforced with HSTS | 4 Subprocessor list, Status page with history, Public pricing, +1 | Compare |
| United World Telecomunitedworldtelecom.comSee also Transparency alternatives to United World Telecom | 30/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 5 Subprocessor list, Data location stated, Status page with history, +2 | Compare |
| Genesysgenesys.comSee also Transparency alternatives to Genesys | 26/100 | 2 Certifications named, HTTPS enforced with HSTS | 4 Subprocessor list, Data location stated, Status page with history, +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.