Where the reviewed products stand
Compare documented control across the named products and routes. Open a review for its plan, region and agreement (this is a selected sample).
0–10 on both axes · Higher and further right means more documented control
Exact scores & review links (10)
| Vendor | Data access & portability | Build & act |
|---|---|---|
| Zendesk ↗ | 3.3* | 3.5* |
| Freshdesk ↗ | 7.6* | 6.0* |
| Help Scout ↗ | 8.2* | 6.7* |
| Intercom ↗ | 6.9* | 5.6* |
| ServiceNow ↗ | 4.7* | 4.7* |
| Gorgias ↗ | 6.2* | 4.1* |
| Front ↗ | 7.6* | 5.1* |
| Kustomer ↗ | 4.6* | 4.5* |
| Pylon ↗ | 5.3* | 6.3* |
| Permute ↗Publisher self-assessment | 8.0* | 7.1* |
Axes average three dimensions each: access, third-party access and exit horizontally; action, continuity and business logic vertically. Fixed 0–10 scale, midlines at 5 (overall grades use separate weights). * Some evidence is unresolved. Marker colors identify companies, not score bands. How to read the map ↗
Permute is included as a reference (it owns this site and is a publisher self-assessment). Its score is excluded from sample averages. Read the Permute review ↗
Support conversations and enterprise service tables have different schemas and permissions. Each review identifies the assessed records and documented write operations.
Compare the six dimensions
| Overall control | |
|---|---|
| Data access | |
| Third-party accessibility | |
| External action | |
| Continuity | |
| Data exit | |
| Business logic and customization | |
Product scopes, dates & reviews
Zendesk
Support and service management · Checked 2026-10-12
Zendesk Support / reviewed third-party application using standard ticketing APIs under the Developer Terms. Direct customer incremental exports are a separate route and are not credited to third-party apps.
Read findings and sources ↗Freshdesk
Support and service management · Checked 2026-10-16
Freshdesk / customer agent API key, REST v2 tickets and contacts, including ticket updated_since and deleted-ticket filters; public Marketplace distribution is outside this route.
Read findings and sources ↗| Customer control | Zendesk ↗ | Freshdesk ↗ | Help Scout ↗ | Intercom ↗ | ServiceNow ↗ | Gorgias ↗ | Front ↗ | Kustomer ↗ | Pylon ↗ | Permute ↗ |
|---|---|---|---|---|---|---|---|---|---|---|
| Category | Support and service management | Support and service management | Support and service management | Support and service management | Support and service management | Support and service management | Support and service management | Support and service management | Support and service management | Databases and data platforms |
| Overall control | ||||||||||
| Data access | ||||||||||
| Third-party accessibility | ||||||||||
| External action | ||||||||||
| Continuity | ||||||||||
| Data exit | ||||||||||
| Business logic and customization | ||||||||||
| Assessment scope | Zendesk Support / reviewed third-party application using standard ticketing APIs under the Developer Terms. Direct customer incremental exports are a separate route and are not credited to third-party apps. | Freshdesk / customer agent API key, REST v2 tickets and contacts, including ticket updated_since and deleted-ticket filters; public Marketplace distribution is outside this route. | Help Scout Inbox API 2.0 / core conversations and customers using customer-owned client credentials or user-authorized OAuth; reporting endpoints and Docs API are excluded. | Intercom / customer-owned private apps for their own workspace and approved third-party OAuth apps for contacts, conversations and webhooks. Listed and unlisted third-party apps both require provider review; private tokens must not be handed to third parties. | ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. | Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications. | Front Core API company/team contact collections and mutations; customer/single-customer API tokens and public OAuth distribution are distinct. | Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved. | Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score. | Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. |
| Assessment checked | 2026-10-12 | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-16 | 2026-10-23 | 2026-10-12 |
| Read the findings | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ |
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
Who can connect?
Yes No- Unknown
A check means the column applies to that route (customer credentials can still require provider approval). Report exports use the customer account without separate API credentials. Open a connection method for its authentication, requirements and last review date.
What each review covers
Zendesk ↗
Ticket reads and writes are available, but third-party access has specific limits on bulk export, persistent copies and background collection.
Zendesk Support / reviewed third-party application using standard ticketing APIs under the Developer Terms. Direct customer incremental exports are a separate route and are not credited to third-party apps.
Freshdesk ↗
Freshdesk provides an agent-authenticated ticket API with updated-time retrieval and deleted-ticket filtering. Its default date window and pagination ceiling need deliberate handling during migration.
Freshdesk / customer agent API key, REST v2 tickets and contacts, including ticket updated_since and deleted-ticket filters; public Marketplace distribution is outside this route.
Help Scout ↗
Help Scout provides customer-owned client credentials and OAuth for Inbox integrations. Core access is included on Standard, while reports have a separate higher-plan boundary.
Help Scout Inbox API 2.0 / core conversations and customers using customer-owned client credentials or user-authorized OAuth; reporting endpoints and Docs API are excluded.
Intercom ↗
Intercom exposes searchable contacts and conversations through private workspace apps and reviewed third-party OAuth apps. Both listed and unlisted third-party apps require approval, and webhook retry is bounded.
Intercom / customer-owned private apps for their own workspace and approved third-party OAuth apps for contacts, conversations and webhooks. Listed and unlisted third-party apps both require provider review; private tokens must not be handed to third parties.
ServiceNow ↗
ServiceNow exposes ACL-governed table APIs and customer-defined integration controls. Read/write capability depends on the selected table, field permissions and instance configuration, not merely on knowing its name.
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Gorgias ↗
Gorgias provides cursor-paginated ticket APIs and documented ticket mutations. Private integrations use account credentials; public apps must use OAuth and pass the partner app process.
Gorgias REST ticket collections and mutations; private account API credentials versus reviewed public OAuth applications.
Front ↗
Front explicitly supports customer and single-customer API tokens, with granular resource permissions. Contact collections support updated-time filters; public integrations normally require OAuth.
Front Core API company/team contact collections and mutations; customer/single-customer API tokens and public OAuth distribution are distinct.
Kustomer ↗
Kustomer documents private customer apps and a separate partner route for client/public apps. Search exports provide a concrete CSV exit path, with a 50,000-row limit and object-specific history constraints.
Kustomer Apps Platform user-context cards, app registration and customer-selected search/report CSV exports; generic backend customer API eligibility and full schema remain unresolved.
Pylon ↗
Pylon includes a read/write REST API in its lowest listed paid plan. Customer-controlled S3 exports offer a separate analytics route from Advanced. The API supports issue updates and operational actions, while hosted token custody, complete deletion recovery and native workflow portability remain unresolved.
Customer-run Pylon REST API for current issues, accounts, contacts and users, including issue/account create/update. Messages are an optional sensitive child stream. Advanced-plan warehouse delivery is a separate route and does not raise the API score.
Permute ↗
Scoped APIs expose SQL reads, managed records and customer-authored operation code. Customer-built apps are supported, while complete workspace recovery, outbound CDC and minimum-plan access terms remain unresolved.
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.