Alternatives to LiveAgent
Other Helpdesk vendors we measure, sorted by how much they publish that LiveAgent does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from LiveAgent on at least one criterion we measured for both. Public transparency score, not a product or security rating.
LiveAgent has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and LiveAgent does not” is the one that closes them.
| Vendor | Score | Publishes, and LiveAgent does not | LiveAgent publishes, and they do not | |
|---|---|---|---|---|
| Intercomintercom.com | 70/100 | 6 Data processing agreement, Data location stated, Certifications named, +3 | 1 Status page with history | Compare |
| Deskprodeskpro.com | 83/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | nothing | Compare |
| Dixadixa.com | 61/100 | 4 Data processing agreement, Data location stated, Uptime SLA with a figure, +1 | 1 Status page with history | Compare |
| Frontfront.com | 60/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | 1 Status page with history | Compare |
| Gorgiasgorgias.com | 50/100 | 4 Data processing agreement, Certifications named, security.txt (RFC 9116), +1 | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Crispcrisp.chat | 57/100 | 3 Subprocessor list, Data location stated, No third-party tracking before consent | 1 Status page with history | Compare |
| Zendeskzendesk.com | 35/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| Freshdeskfreshdesk.com | 48/100 | 2 Data location stated, Uptime SLA with a figure | nothing | Compare |
| Hiverhiverhq.com | 48/100 | 2 Data location stated, Certifications named | nothing | Compare |
| Re:amazereamaze.com | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Status page with history | Compare |
| Tidiotidio.com | 42/100 | 2 Data location stated, Certifications named | 1 HTTPS enforced with HSTS | Compare |
| Kayakokayako.com | 40/100 | 2 Data location stated, Certifications named | 1 HTTPS enforced with HSTS | 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.