Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Freshworks Inc. · www.freshworks.com

Compare with Zammad → Compare with Zendesk → Report an error on this page Is this your product? →

Link to this page

Freshdesk: AI-assisted analysis on whats-best.ai Freshdesk: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Freshdesk at a glance

Vendor
Freshworks Inc.
Headquarters
Incorporated in the United States source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates Freshdesk 3/5, the mean of 6 judges. Freshdesk is Freshworks Inc.'s helpdesk. how scores are made
As of
Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

Freshdesk alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Freshdesk is Freshworks Inc.'s helpdesk. Pricing transparency and ticketing core drew the highest scores at 6-7; sovereignty the lowest at 3-4. Every tier is priced publicly — Growth €17, Pro €52, Enterprise €84 per agent per month, billed annually — add-ons carry unit prices, including AI Agent sessions at €45/100 sessions with the first 500 included; we found no public information on telephony or messenger costs, VAT treatment or minimum term. Ticketing core rests on documented mechanics: closed tickets archive automatically after 120 inactive days, routing tiers named per plan — but we found no public information on SLA breach warnings, business-hours policies or first-response reporting by agent and queue. Sovereignty sits low: a US parent, transfers resting on the EU-U.S. Data Privacy Framework, European entities in Germany, the Netherlands and France, a Europe data-centre endpoint for the bot product — and we found no public information on ticket-archive residency or sub-processor locations. WhatsApp and Facebook Messenger reach the helpdesk through a separate bot product rather than one native queue. Scores clustered narrowly; widest ranges sat at knowledge and self-service, 5-7, and integrations, 4-6.

Report an error

Speaks for it

  • Public per-agent prices on every tier — Growth €17, Pro €52, Enterprise €84 per agent per month, billed annually — with metered add-ons quoted at €45/100 AI Agent sessions, €80/5000 connector tasks and €13/1000 MCP actions
  • A documented ticket lifecycle in which closed tickets archive automatically after 120 inactive days as read-only records, with deletion of archived tickets documented as permanent and irreversible
  • Routing named per plan: intelligent routing and multiple SLA policies at Pro, skill-based routing and audit logs at Enterprise
  • Measurable bot deflection through per-intent statistics on times sent and helpfulness, with training tags flagging unmapped, unhelpful and thin-coverage questions
  • A documented API library in the bot builder with custom headers and authorization, test runs, a ten-second timeout, and multipart payloads that pass file attachments to third-party systems

Report an error

Held against it

  • Sovereignty scored 3-4, the lowest of the seven criteria: a US parent with transfers resting on the EU-U.S. Data Privacy Framework, and we found no public information on ticket-archive residency or sub-processor locations
  • WhatsApp and Facebook Messenger reach Freshdesk through a separate bot product — WhatsApp via a Freshchat integration — and we found no public information on telephony inside the Freshdesk queue
  • We found no public information on business-hours SLA policies, breach warnings, escalation paths, or first-response and resolution-time reporting by agent and queue
  • We found no public information on retention rules per queue or data category, redaction of ticket content, attachment handling, or documented support for access and erasure requests
  • We found no public information on named CRM or shop integrations, agent SSO and SCIM provisioning, published rate limits, or customer order context shown inside the ticket

Report an error

Best for

  • You run an email-first shared inbox with a customer portal and want predictable per-agent pricing you can budget from public pages
  • You want deflection you can measure: per-intent statistics on how often a question was sent and whether it helped, with training tags flagging unmapped questions
  • You need rule-based routing and multiple SLA policies over a documented ticket archive lifecycle
  • You prefer consumption add-ons quoted openly, from AI Agent sessions at €45/100 sessions to connector tasks at €80/5000 tasks

Report an error

Avoid if

  • You require EU-only data residency or an EU contracting chain — ask the vendor: the public pages we read do not show it
  • You need telephony and messengers inside one Freshdesk queue — WhatsApp and Facebook Messenger ride through a separate bot product and calling sits with a separate product
  • Your audit scope must cover vendor-side practices the privacy notice documents: sharing identifiers with Facebook and LinkedIn for custom-audience advertising, and using Freshcaller call recordings for product improvement
  • You must verify SLA mechanics — breach warnings, business-hours policies, first-response reporting by agent and queue — before committing, since the public pages document routing tiers but not these controls

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Ticketing, queues & SLA 3 of 5
Channels in one queue 3 of 5
Knowledge base & deflection 3 of 5
Customer data protection 3 of 5
Integrations & API 3 of 5
European sovereignty 1.5 of 5
Pricing transparency 3.5 of 5

Ticketing, queues & SLA

Show reasoning
How this is scored

The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.

0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.

3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.

5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.

8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.

10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.

Report an error

The Support Lead

Intelligent routing and multiple SLA policies are on the Pro plan, skill-based routing and audit logs on Enterprise, and the archiving and unresolved-tickets articles prove real status management, automation rules and global search behind the marketing. What I found no public information on is breach warnings and escalation timers, or first-response and resolution time reported by agent and queue — so I can't put it in the top band. 2 4 5

Report an error

The Agent Advocate

Intelligent routing and multiple SLA policies come with Pro, skill-based routing with Enterprise, and global search does span tickets — but it excludes archived threads unless you change the setting, which is precisely how the half-remembered case gets lost. The archiving engine is thought through: a customer reply to an archived thread opens a new ticket, linked tickets stay linked, and reports still count archived tickets as closed. We found no public information on macros, merge and split, or business-hours SLA policies with breach warnings, and those decide the hundredth reply. 2 4 5

Report an error

The Data Protection Officer

Tickets are routed by intelligent routing on Pro and skill-based routing on Enterprise, with multiple SLA policies, automation rules, global search and custom dashboards; closed tickets move automatically into a read-only archive after 120 days of inactivity and remain searchable behind an opt-in setting. We found no public information on business-hours-aware SLA policies with breach warnings and escalation, macros, merge and split, or first-response and resolution reporting broken down by agent and queue. 2 4 5

Report an error

The Shop Operator

The engine is real: plan pages name intelligent routing, skill-based routing and multiple SLA policies, and the support documentation shows automation rules, automatic archiving after 120 days of inactivity, global search across tickets, and an unresolved-tickets metric with reporting durations that differ by plan. But we found no public information on SLA breach warnings, business-hours policies, or first-response and resolution time reported per agent and queue, so it sits above solid basics and below the mature tier. 2 4 5

Report an error

The Integrator

The plan pages list a shared inbox, intelligent routing and multiple SLA policies on Pro plus skill-based routing, a sandbox and audit logs on Enterprise, and the help centre documents a managed ticket lifecycle — automatic archiving after 120 inactive days, read-only access, export, and permanent irreversible deletion — alongside an unresolved-tickets metric. We found no public information on business-hours-aware SLA policies, breach warnings, escalation paths, or merge and split, so the evidence reaches solid rule-based routing with skills-based assignment, short of contract-grade SLA management. 2 4 5

Report an error

The Skeptic

The priced tiers name real engine parts — intelligent routing and multiple SLA policies at Pro, skill-based routing and audit logs at Enterprise — and the help centre documents a genuine lifecycle: closed tickets auto-archived after 120 inactive days, read-only archives, global search with archived tickets excluded unless opted in, and automation rules that stop running on archives. We found no public information on business-hours-aware SLA policies, breach warnings or escalation paths, macros, merge and split, or first-response and resolution-time reporting by agent and queue, so the tier bullets never show the mechanics an SLA owner would need. 2 4 5

Report an error

Channels in one queue

Show reasoning
How this is scored

Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.

0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.

3 — Email turned into tickets, with a web form or one further channel.

5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.

8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.

10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.

Report an error

The Support Lead

Email lands in a shared inbox, customers see their own tickets in the portal, and WhatsApp and Facebook Messenger are documented — though WhatsApp rides through the Freshchat widget and Facebook through the bot product, and voice is a separate Freshcaller product with consent-based call recording. I found no public information showing all of these writing to one conversation with one history for the agent. 2 4 6 7 3

Report an error

The Agent Advocate

Email, a self-service customer portal and the messengers all reach Freshdesk, but Facebook Messenger and WhatsApp arrive through a separate bot product — and WhatsApp first needs a Freshchat account wired in, so I'd be working across consoles instead of one screen. The portal is properly two-way: customers log in and see their own tickets, archived ones included, though they cannot reply to those. We found no public information on telephony with call logging landing in the Freshdesk queue. 2 4 6 7 8

Report an error

The Data Protection Officer

Email lands in a ticketing shared inbox with a customer portal from the Growth tier, and the self-service bot reaches Facebook Messenger and WhatsApp, collecting context and handing over to Freshdesk agents as a ticket; the WhatsApp deployment runs through a separate Freshchat integration and accepts text input only, with numbered options instead of buttons. We found no public information on telephony integration into the Freshdesk queue or on consent handling for the messenger channels. 2 6 7 8 4

Report an error

The Shop Operator

WhatsApp and Facebook Messenger are both documented, but the route runs through a separate Freshchat widget and the Freddy Self-service bot, which hands over to Freshdesk "using APIs" and creates a ticket — messengers reach the helpdesk through bot handover rather than landing natively in the queue. The customer portal is evidenced (customers can even view archived tickets there), agents see a contact's ticket history, and email threads exist; we found no public information on telephony landing in the same queue — a call-recording consent note for the separate Freshcaller product is all the captured pages carry on phone, and no consent handling is stated for WhatsApp. 3 4 6 7 8

Report an error

The Integrator

Email arrives in a shared inbox, requesters can see their own tickets in a customer portal, and Facebook Messenger and WhatsApp conversations reach Freshdesk through the Freddy Self-service bot product, which hands the conversation to an agent and creates a ticket on the customer's behalf. The messenger channels run through a separate bot product wired in by APIs, and we found no public information on earlier cross-channel conversations being visible to the agent; a separate calling product records calls with both parties' consent, but we found no public information on calls writing into the ticket history. 3 2 4 6 7 8

Report an error

The Skeptic

Email ticketing with a shared inbox and a customer portal ship from the Growth tier, and the help centre confirms customers can log into the portal and see their own archived tickets. WhatsApp and Facebook Messenger are reached through a separate bot product that hands conversations over to Freshdesk agents and creates tickets on the customer's behalf, with webhooks pointed at a freshbots domain rather than the helpdesk — the captured pages never show these channels landing in one queue with one shared conversation history, and we found no public information on telephony or social channels inside the Freshdesk queue. 2 4 6 7 8

Report an error

Knowledge base & deflection

Show reasoning
How this is scored

Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.

0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.

3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.

5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.

8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.

10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.

Report an error

The Support Lead

The answer bot maps customer questions to answers before a ticket exists, tracks how often each was sent and how helpful it was, and a training view tags unmapped and unhelpful questions — that is genuine gap identification — with a multilingual helpdesk from Pro. I found no public information on versioning or review dates that flag stale articles, or on suggestions shown to agents while they answer. 2 8 9

Report an error

The Agent Advocate

Deflection is engineered rather than bolted on: the bot maps customer questions and their variants to answers or flows, counts how often each intent fired and whether it helped, and tags unmapped or unhelpful questions for training — that is gap-finding, not article storage. A knowledge base and customer portal ship in the base plan, and the bot hands over by creating a ticket on the customer's behalf when it cannot answer. We found no public information on article suggestions to the agent while answering, draft and publish states, or stale-content flags, so the help centre itself may be thinner than the bot in front of it. 2 8 9

Report an error

The Data Protection Officer

A knowledge base ships with the customer portal from the Growth tier, and the self-service layer maps customer questions and their variants to answers or chatbot flows, records helpful and not-helpful feedback with per-intent statistics, and tags unmapped or unhelpful questions for coverage training — deflection measured at the bot level. We found no public information on article workflow such as draft and publish states, multilingual articles, versioning, or article suggestions surfaced to the agent while answering. 2 8 9 1

Report an error

The Shop Operator

Deflection has machinery behind it: the self-service bot maps customer questions and their variants to answers or flows before any ticket exists, tracks how often each intent was sent and how helpful it was, and tags unmapped questions for coverage training — that is the December ticket-count test in embryonic form. But the article side is thin: a knowledge base is named in the plan features and we found no public information on draft and publish states, versioning, multilingual articles, or article suggestions to agents while they answer. 2 8 9

Report an error

The Integrator

A knowledge base ships with the customer portal from the entry plan, and the self-service bot maps customer questions and their variants to answers or flows, records how often each intent is sent and how helpful it was, and tags unmapped or unhelpful questions for training — real deflection machinery. We found no public information on the help centre's article workflow — draft and publish states, versioning, review dates — or on article suggestions shown to agents while they answer. 2 8 9

Report an error

The Skeptic

A knowledge base and customer portal ship from the Growth tier, and the bot layer does visible deflection work: customer questions and variants mapped to answers or flows, helpful/not-helpful statistics per intent, Yes/No feedback after each answer, and training tags flagging unmapped, unhelpful and thin-coverage questions. We found no public information on draft and publish states, a branded public help centre, article versioning or stale-content flags, so deflection runs through bot answers rather than a documented knowledge workflow. 2 8 9

Report an error

Customer data protection

Show reasoning
How this is scored

A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.

0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.

3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.

5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.

8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and redaction of ticket content.

10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.

Report an error

The Support Lead

A data processing agreement is stated to govern hosted data, the sub-processor list is published, agent roles and permissions ship from the base plan, audit logs from Enterprise, and permanent ticket deletion is documented in the help centre. Two facts hold me back: the privacy notice says call recordings are used to train the vendor's own applications, and identifiers are shared with Facebook and LinkedIn for custom-audience advertising — both consent-based, but I would want that scoped before an audit. 3 2 4

Report an error

The Agent Advocate

The paper trail is solid: a data processing agreement governs Hosted Data, a sub-processor list is published, roles and permissions are in the base plan, audit logs arrive at Enterprise, and deleting an archived ticket is documented as permanent and irreversible. Closed tickets archive automatically after 120 days, which behaves like retention, though we found no public information on deletion rules per queue or data category, redaction of ticket content, or documented handling of access and erasure requests. Two passages deserve a buyer's attention — the notice describes sharing identifiers with Facebook and LinkedIn for custom audiences, and Freshcaller call recordings used for product improvement — both sit in the vendor's own controller role rather than the hosted-data relationship. 3 2 4

Report an error

The Data Protection Officer

A data processing agreement governs Hosted Data with Freshworks acting as processor, agent roles and permissions are included from Growth, audit logs sit on Enterprise, and a sub-processor list is published with access limited to necessity and bound by confidentiality obligations. Retention executes — closed tickets archive automatically after 120 days of inactivity and deleting an archived ticket is permanent and irreversible — but we found no public information on redaction of ticket content, attachment handling, retention configured per queue or data category, or whether the vendor's own support can open a customer ticket. 3 2 4

Report an error

The Shop Operator

A data processing agreement is stated to govern Hosted Data, agent roles and permissions are listed in the plans, ticket deletion is documented as permanent and irreversible, a sub-processor list is published with access limited to what is necessary, and audit logs appear at the top tier. We found no public information on automatic retention rules per data category, attachment handling, redaction, or documented support for access and erasure requests; the privacy notice separately describes sharing website identifiers with social advertising platforms while stating Freshworks is not the controller of customer Hosted Data. 3 2 4

Report an error

The Integrator

The privacy notice states that Hosted Data is governed by the customer's own notice and a data processing agreement, a sub-processor list is published with access-limited commitments, permanent ticket deletion is documented in the help centre, roles and permissions ship from the entry plan and audit logs from the top tier. We found no public information on retention or deletion rules per queue or data category, attachment handling, documented support for access and erasure requests, or redaction of ticket content. 3 2 4

Report an error

The Skeptic

The privacy notice confirms customer hosted data is governed by a data processing agreement with the customer's notice applying, a sub-processor list is published with access limited to what is necessary, and the help centre documents permanent, irreversible deletion of tickets and full-list exports. Roles and permissions appear from Growth while audit logs sit only in Enterprise, and we found no public information on automatic retention rules per queue or data category, redaction of ticket content, attachment handling, or documented support for access and erasure requests. 3 2 4

Report an error

Integrations & API

Show reasoning
How this is scored

The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.

0 — A closed tool with no API and no integrations; context is copied in by hand.

3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.

5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.

8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and SCIM provisioning, documented rate limits and a sandbox.

10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.

Report an error

The Support Lead

There is a marketplace for first- and third-party apps, pre-built connectors for data sync priced by the task, and a documented REST-and-JSON API library with authorisation headers, test runs and a ten-second timeout, plus a sandbox on Enterprise. I found no public information on documented rate limits, SSO or SCIM provisioning for agents, or customer context from another system shown inside the ticket. 3 2 10 11

Report an error

The Agent Advocate

There is a marketplace for first- and third-party apps, pre-built connectors for data sync metered by the task, and a genuinely documented API library in the bot builder — REST and JSON only, with custom headers and authorisation, test runs, and a ten-second timeout on every call. Failed calls leave status and logs you can debug, and multipart support carries file attachments out to third-party systems. We found no public information on rate limits, SCIM provisioning, or CRM context shown inside the ticket, so the marketplace reads as a listing platform more than a maintained integration set. 3 2 10 11

Report an error

The Data Protection Officer

A marketplace carries applications from Freshworks and third parties, pre-built connector apps are sold by the task, and the API library documents REST calls with GET, PUT, POST and DELETE plus a JS function, custom headers and authorisation, test runs, and multipart payloads that pass file attachments to third-party systems; a sandbox and IP whitelisting sit on Enterprise. We found no public information on documented rate limits beyond the ten-second API timeout, on SSO or SCIM provisioning, or on customer context from other systems shown inside the ticket. 3 2 10 11

Report an error

The Shop Operator

There is a marketplace for first- and third-party apps, pre-built connectors metered by tasks, and a genuinely documented bot-side API library — REST with JSON, the usual methods, headers and authorization, test runs, and multipart form data that can carry file attachments to third-party systems. But we found no public information on named CRM or shop integrations, on customer order context shown inside the ticket, or on SSO and SCIM for the product — and order-in-the-ticket is the whole point for me: my agent needs the parcel data without a second login. 3 2 8 10 11

Report an error

The Integrator

There is a marketplace for first- and third-party apps, pre-built connectors metered by task at published prices, a sandbox on the Enterprise plan, and a documented API library in the bot builder covering methods, authorisation headers, sample test runs, a ten-second timeout and status logs for failed calls, with webhook endpoints published per data centre. What I need to wire in a CRM, a shop and an identity provider is not on these pages: we found no public information on rate limits, SCIM provisioning, single sign-on for agents, webhook retry behaviour or API versioning — the only sign-in evidence is social login on the vendor's website. 3 2 6 10 11

Report an error

The Skeptic

A marketplace for first- and third-party applications exists, pre-built connectors are sold as metered tasks, and the bot builder's API library is documented in real depth — GET/PUT/POST/DELETE methods, custom headers and authorization, test runs, a 10-second timeout, and multipart payloads that carry file attachments to third-party systems. That is outbound API calling from a bot rather than the product's own documented REST API, and we found no public information on named CRM or shop integrations, agent SSO and SCIM provisioning, or published rate limits — the social sign-in in the privacy notice is website login, not agent identity. 3 2 10 11

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.

0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.

3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.

5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.

Report an error

The Support Lead

The contracting parent is a Delaware company, but the privacy notice names entities established in Germany, France and the Netherlands, a DPA governs hosted data, the sub-processor list is published, and the bot infrastructure has a Europe data-centre endpoint. Where the ticket archive itself is hosted is not confirmed in what I read, and processing regions are named as the United States, United Kingdom and EEA plus third-party countries under the Data Privacy Framework rather than EU-only processing. 3 6

Report an error

The Agent Advocate

The contracting picture is US-first: Freshworks Inc. of Delaware, with regional entities in Germany, the Netherlands and France named in the privacy notice, and processing stated across the United States, the United Kingdom and the EEA. A European data-centre endpoint exists for the bot service, while reliance on the EU-U.S. Data Privacy Framework tells me transatlantic transfers are by design. For the Freshdesk archive itself we found no public information on selectable data residency, self-hosting, or where the sub-processors sit. 3 6

Report an error

The Data Protection Officer

The vendor is US-based Freshworks Inc. of Delaware and transfers rest on the EU-U.S. Data Privacy Framework, while the privacy notice names German, Dutch and French entities as controllers under the GDPR, processing includes the EEA alongside the United States and UK, and the bot service offers a Europe data-centre endpoint. We found no public information establishing an EU hosting option as standard or selectable, an EU contracting entity for the service, or sub-processor locations, so the European elements stand in an otherwise unstated chain. 3 6

Report an error

The Shop Operator

The vendor is Freshworks Inc. of Delaware, transfers lean on the EU-U.S. Data Privacy Framework, and we found no public information on an EU hosting option for the ticket archive. The European elements that are proven — group companies in Germany, the Netherlands and France, EEA named among processing regions, and a Europe data-centre endpoint for the bot platform's Messenger webhook — give one European link with the rest of the chain unstated, which is exactly the low rung. 3 6

Report an error

The Integrator

The contracting parent is a US company relying on the EU-U.S. Data Privacy Framework, but the captured pages prove European elements: processing in the European Economic Area is stated, German, French and Dutch group entities are named, a sub-processor list is published, and the bot platform operates a Europe data centre. Where the ticket archive itself is hosted and what the data processing agreement commits to are unknown from these pages, so I cannot score this above one proven European element with the rest of the chain unstated. 3 6

Report an error

The Skeptic

The captured pages give a US picture: an inferred Delaware parent, processing stated across the United States, the UK and the EEA, and transfers resting on the EU-US Data Privacy Framework rather than an EU-only chain. European elements are proven — Freshworks entities registered in Germany, the Netherlands and France, EEA processing, and a Europe data-centre endpoint for the bot product — but the residency of the Freshdesk ticket archive, the contracting entity for Freshdesk itself, and sub-processor locations are unstated on the pages read. 3 6

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price or one priced tier, per agent or flat.

5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.

8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.

10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.

Report an error

The Support Lead

Three tiers are priced per agent per month with the billing period stated and features listed per tier, and the metered add-ons carry unit prices — "€45/100 sessions" and "€80/5000 tasks" — plus day passes per tier. I found no public information on telephony or messenger costs, minimum term or VAT treatment, so I cannot compute the real annual invoice for my agent count from public pages alone. 2

Report an error

The Agent Advocate

Three tiers priced per agent with the billing period stated — Growth at €17/agent/month, Pro at €52/agent/month, Enterprise at €84/agent/month, billed annually — plus day passes at €2/€7/€12 per pass and add-ons quoted exactly: AI Agent sessions at €45/100 sessions, connector app tasks at €80/5000 tasks, MCP actions at €13/1000 actions. With the feature list per tier I can get most of the way to a real invoice for my agent count. What stops exact maths is that we found no public information on telephony or messenger channel costs, VAT treatment, or minimum term on the captured pages. 2 1

Report an error

The Data Protection Officer

Every agent tier is priced publicly with the annual billing period stated — Growth at €17 per agent per month, Pro at €52, Enterprise at €84 — plus day passes at €2, €7 and €12 per pass and metered add-ons at €45 per 100 AI Agent sessions, €80 per 5000 connector tasks and €13 per 1000 MCP actions. We found no public information on telephony or messenger channel costs, light-agent or contact limits, minimum term or VAT treatment, so the real annual invoice is not computable from the published pages alone. 2 1

Report an error

The Shop Operator

A support lead can compute the core annual invoice from public pages: Growth at €17 /agent/month, Pro at €52 and Enterprise at €84, each "billed annually" with features listed per tier, plus priced add-ons — AI Agent sessions at €45/100 sessions, connector tasks at €80/5000 tasks, MCP actions at €13/1000 actions — day passes per plan, and a free start. What is missing for a complete figure: we found no public information on telephony or WhatsApp channel costs, light-agent or contact limits, minimum term, or VAT treatment. 2 1

Report an error

The Integrator

Every plan is priced publicly per agent in euros — Growth at €17 /agent/month, Pro at €52 /agent/month, Enterprise at €84 /agent/month, billed annually — with main features listed per tier, day passes priced per plan, consumption add-ons priced by AI session, connector task and MCP action, and a free start offered. A support lead can compute most of the annual invoice from these pages; we found no public information on VAT treatment, minimum term, or telephony and messenger channel costs. 2 1

Report an error

The Skeptic

Every tier carries a public per-agent price — €17, €52 and €84 per agent per month, billed annually — with features listed per tier and even the metered add-ons priced: AI Agent sessions at €45/100 sessions with the first 500 included, connector tasks at €80/5000 tasks, MCP actions at €13/1000 actions, and day passes of €2, €7 and €12 by tier. So the AI agent is demonstrably metered, not quietly included; still, the captured pricing pages give no telephony or messenger costs, no VAT treatment or minimum term, and state only the annual rate, leaving a support lead unable to compute the full invoice. 2 1

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Freshdesk

Is Freshdesk European?

No. whats-best.ai classifies Freshdesk as Rest of world. Its vendor, Freshworks Inc., is incorporated in the United States, per the vendor’s page captured 16 Nov 2026.

Where does Freshdesk store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does Freshdesk have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to Freshdesk?

As of 18 Nov 2026, the panel rates Zendesk (3.5/5), LiveAgent (3.5/5) and Intercom (3.5/5) highest among the other 35 Customer Service & Helpdesk products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Zammad (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Freshdesk alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Product page www.freshworks.com Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
  2. 2 Pricing www.freshworks.com Checked 16 Nov 2026 +2 earlier captures: 11 Sep 2026, 31 Aug 2026 Details →
  3. 3 Privacy policy www.freshworks.com Checked 16 Nov 2026 Details →
  4. 4 Ticketing, queues & SLA — found from sitemap support.freshworks.com Checked 16 Nov 2026 Details →
  5. 5 Ticketing, queues & SLA — found from sitemap support.freshworks.com Checked 16 Nov 2026 Details →
  6. 6 Channels in one queue — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
  7. 7 Channels in one queue — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
  8. 8 Knowledge base & deflection — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
  9. 9 Knowledge base & deflection — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
  10. 10 Integrations & API — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
  11. 11 Integrations & API — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →