Customer Service & Helpdesk
Freshdesk
Rest of world Report an error0–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? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Freshdesk is Freshworks' customer service and helpdesk product. Scores peak on knowledge and self-service at 5-6 and pricing transparency at 5-7, bottoming out on sovereignty at 2-3. Self-service earns it: intents map to answers or flows, yes/no feedback follows every answer, and training tags flag unmapped questions. Pricing transparency splits 5-7: tiers are public — €17, €52 and €84 per agent per month, billed annually — but judges differ on whether the real invoice is computable, with chat and telephony separately priced and VAT treatment and minimum term unstated. Ticketing core splits 4-6: credit for the documented archiving lifecycle and tiered routing against missing detail on SLA timers, breach warnings, macros and per-agent reporting. Customer data protection is a flat 4 — irreversible archived-ticket deletion and a published sub-processor list, and judges found no public information on a signable data processing agreement or retention period. Sovereignty scores lowest: a Delaware contracting parent, processing stated for the United States, the United Kingdom, the EEA and countries where its third parties are based, and the captured pages do not confirm where the hosted archive resides.
Speaks for it
- Self-service deflection is measured, with intent statistics tracking how often each answer was sent and how helpful it was, and training tags flagging unmapped and unhelpful questions
- Closed tickets archive automatically after 120 inactive days, remain read-only, and deleting an archived ticket is documented as permanent and irreversible
- All three tiers carry public prices — Growth €17, Pro €52 and Enterprise €84 per agent per month, billed annually — plus day passes at €2, €7 and €12 per pass and metered add-ons such as additional AI Agent sessions at €45/100 sessions
- Intelligent routing and multiple SLA policies arrive at Pro, with skill-based routing, sandbox and audit logs held for Enterprise
- A sub-processor list is published with access limited to what is reasonably necessary, and Freshworks entities in Germany, the Netherlands and France are named as EU contracting entities
Held against it
- Sovereignty scores lowest on the table at 2-3 — the contracting parent is Freshworks Inc. of Delaware, and the captured pages do not confirm where the hosted ticket archive resides
- The privacy notice describes sharing email addresses and identifiers such as phone numbers, usually in hashed form, with Facebook and LinkedIn for custom-audience advertising
- We found no public information on a signable data processing agreement, a stated retention period for ticket data, or documented support for access and erasure requests
- We found no public information showing email, messengers and calls landing in one queue with one shared history — WhatsApp runs through a Freshchat integration, Facebook Messenger through the bot platform's own webhook data centres, and phone is a separate product
- The documented API library is the bot builder calling outward — REST with JSON responses only and a 10-second timeout — and we found no public information on a helpdesk-side API, named CRM or shop integrations, or webhooks for core ticket events
Best for
- You run email-first support with a customer portal — both are documented in one ticketing product, and requesters can see their own tickets, archived ones included, by logging into the portal
- You want deflection you can audit — intent statistics and yes/no feedback show which answers help, and training tags expose which questions have no coverage
- You need public per-agent euro pricing with elastic elements — day passes and additional AI Agent sessions at €45/100 sessions beyond the 500 included in every tier
- You want a self-running archive policy — closed tickets auto-archive after 120 inactive days, count as closed in reports, and archived deletion is permanent and irreversible
Avoid if
- You must confirm EU residency for your ticket archive before signing — the captured pages do not confirm where hosted data resides, and the contracting parent is Freshworks Inc. of Delaware relying on the EU-U.S. Data Privacy Framework
- You need WhatsApp, Facebook Messenger and phone in the same queue and shared history as email — the documented routes run messengers through a separate bot platform over APIs and phone through a separate product
- You cannot accept hashed email addresses and phone numbers being shared with Facebook and LinkedIn for custom-audience advertising
- You need audit logs, a sandbox or skill-based routing on a lower plan — all three are Enterprise-only, at €84 per agent per month billed annually
The scores
Ticketing, queues & SLA
Show reasoningHide 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 — A shared mailbox with labels; no ownership, no status model, no history beyond the thread.
3 — Tickets with assignment and open/closed status, but routing is manual, there are no SLA timers and search covers subject lines only.
5 — Queues with rules-based routing, priorities, a working status model, SLA timers with breach warnings, and full-text search across ticket bodies.
8 — Business-hours-aware SLA policies per queue or customer, escalation chains, macros and triggers, merge and split, 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.
The Support Lead
Intelligent routing, multiple SLA policies and custom dashboards arrive on Pro, with skill-based routing and audit logs held back for Enterprise, and the archiving lifecycle is properly documented — closed tickets auto-archive after 120 inactive days and still count as closed in reporting. We found no public information on SLA timers with breach warnings, escalation chains, or first-response and resolution time reported by agent and queue, which is exactly the reporting I take to a quarterly review. 2 4 5
The Agent Advocate
Multiple SLA policies and intelligent routing sit in Pro, skill-based routing and audit logs arrive with Enterprise, and the archiving lifecycle is documented down to the 120-day rule for closed tickets, which is a real status model rather than a labelled mailbox. What I can't find is the hundredth-reply machinery: no public information on breach warnings, escalation chains, macros, business-hours SLAs, or how deep ticket search actually goes. 2 4 5
The Data Protection Officer
Routing and SLA are real and visibly tiered — intelligent routing and multiple SLA policies on Pro, skill-based routing and audit logs on Enterprise — and the archive runs itself: closed, inactive tickets become read-only after 120 days, count as closed in reports, and stay out of global search unless an admin opts them in. We found no public information on priorities, escalation chains, macros, merge and split, business-hours SLA policies, or what the audit log actually records. 2 4 5
The Shop Operator
The plans name intelligent routing, multiple SLA policies and skill-based routing, and the support docs show a genuine lifecycle — closed tickets archive automatically after 120 inactive days, automation rules stop on archived tickets, and unresolved-ticket reporting is documented. But we found no public information on SLA breach warnings, priority handling, macros, or merge and split, and nothing showing whether search reaches ticket bodies, which is what finding one parcel query among ten thousand depends on. 2 4 5
The Integrator
Intelligent routing and multiple SLA policies arrive at Pro, skill-based routing and audit logs at Enterprise, and the ticket-archiving lifecycle is documented down to its effect on reports, search and customer replies. I found no public information on escalation chains, macros, merge and split, or first-response and resolution-time reporting by agent, so I stop short of the higher band. 2 4 5
The Skeptic
The tier pages are the clearest evidence: multiple SLA policies and intelligent routing begin at Pro, while skill-based routing, the sandbox and audit logs are Enterprise-only, and we found no public information on what an SLA policy actually enforces — timers, breach warnings, business-hours coverage. The ticket lifecycle itself is well documented (closed status, automatic archiving after 120 inactive days, permanent irreversible deletion, automation rules), but we found no public information on escalation chains, macros and triggers, or first-response and resolution reporting by agent and queue. 2 4 5
Channels in one queue
Show reasoningHide 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 — Email only.
3 — Email plus one more channel, but the second lives in its own inbox: no shared history, and a customer who switches channel starts again.
5 — Email, a web form or portal and live chat all landing as tickets in one queue, with the customer's history visible whichever channel they used.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp, Signal or similar) with its consent handling stated, and a customer portal where a requester can see their own tickets.
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.
The Support Lead
Email agents, a customer portal, Facebook Messenger and WhatsApp bots are all evidenced, and phone exists as the Freshcaller product with call-recording consent stated. But the WhatsApp deployment runs through a Freshchat integration and bot-to-agent handover happens over APIs, and we found no public information showing these channels land in one queue with one shared history a customer can move between mid-issue. 1 3 2 6 7 8
The Agent Advocate
Email and the customer portal live in one product with one history, and WhatsApp and Facebook Messenger are both documented, but as bot channels on a separate self-service platform that hands conversations over to Freshdesk through APIs, with phone calls in yet another product. I found no public information showing those channels landing in one queue with one history, so mid-issue channel switching still costs the customer a repeat. 2 4 6 7
The Data Protection Officer
Email threads, a customer portal where requesters can see their own tickets, and WhatsApp and Facebook Messenger deployment are all evidenced, with Messenger conversations handed over to a Freshdesk agent and Freshcaller call recording stated as subject to both parties' consent. The messengers arrive through a separate bot product connected over APIs, and we found no public information showing all channels landing in one queue with one shared history when a customer switches. 3 4 6 7 8
The Shop Operator
Email and the customer portal clearly land in one ticketing product with a shared inbox, and the portal lets a requester see their own archived tickets. WhatsApp only reaches an agent through a chain — a Freddy Self-service bot deployed on a Freshchat widget, handed over to Freshdesk via APIs — and Facebook Messenger runs through the same bot platform, so we found no public information showing these channels land in one queue with one shared history. Telephony appears only as a sibling product in the privacy notice, with no evidence of calls logging into the Freshdesk queue. 2 4 6 7 8
The Integrator
Email AI agents, a customer portal where requesters see their own tickets, and WhatsApp and Facebook Messenger deployment through the Freshchat and Freddy products are all evidenced, with consent-based call recording stated for the separate Freshcaller product. What the captured pages do not show is these channels meeting in one queue with one history: messenger conversations reach agents as a bot handover that creates a ticket, and no telephony call logging into the helpdesk is evidenced. 1 3 2 4 6 7
The Skeptic
Beyond email, the customer portal and per-contact ticket history are real — customers log in and see their own tickets, archived ones included — but every further channel arrives through glue: Facebook Messenger runs through the bot platform's own webhook data centres, WhatsApp only by wiring a separate Freshchat account into that bot product, and phone is a separate product whose consent-based call recording the privacy notice describes. We found no public information showing chat, messengers and calls landing in one queue with one shared history beside email. 3 2 4 6 7 8
Knowledge base & deflection
Show reasoningHide 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; answers live in agents' heads and old tickets.
3 — A basic article list, public or internal, with no editorial workflow, no versioning and no link between articles and tickets.
5 — A searchable public help centre with categories, draft and publish states, and agents able to insert an article into a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates 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.
The Support Lead
Freddy answers track intent statistics with helpful/not-helpful feedback and training tags that flag unmapped and unhelpful questions — a genuine gap-finding loop rather than a link library. We found no public information on editorial workflow, versioning, review dates or deflection reported as a number, and the claimed "up to 80% resolution rates" is a figure I would want checked against my own queue. 1 2 9
The Agent Advocate
The deflection half is genuinely evidenced: intents with variants map to answers or flows, yes/no feedback is captured, the questions view counts how often each intent fired and how helpful it was, and unmapped questions get tagged for coverage work. The article half is a single bundled knowledge-base mention — I found no public information on editorial workflow, versioning, review dates, or suggestions to agents mid-reply. 2 8 9
The Data Protection Officer
Self-service is managed where it is measured: intents with variants, fallbacks, yes/no feedback after each answer, helpfulness statistics, and a training view that tags unmapped and thin questions so coverage gaps get found. The knowledge base itself appears only as a plan feature line, and we found no public information on editorial workflow, versioning, review dates, article suggestions to agents while they answer, or deflection reported as a number against ticket volume. 1 2 8 9
The Shop Operator
The deflection machinery is documented and it is what I judge on: the bot answers customers before any ticket exists, tracks how often each intent was sent and whether it helped, flags unmapped and unhelpful questions for training, and creates a ticket only on handover, with the product pages claiming resolution rates up to 80%. We found no public information on the knowledge base as a managed asset — editorial workflow, versioning, review dates, or reporting tying specific articles to deflected volume; it appears only as a named plan feature. 1 2 8 9
The Integrator
A knowledge base and customer portal ship from the Growth plan, and the Freddy bot answers customer questions with intent statistics showing how often each answer was sent and how helpful it was, plus a training view flagging unmapped and unhelpful questions — deflection treated as measurable. I found no public information on editorial workflow, versioning, review dates, or article suggestions shown to agents while they answer. 2 8 9
The Skeptic
Deflection is documented and measured: intents and their variants map to answers or flows, yes/no helpfulness feedback is collected after every answer, each intent tracks how often it was sent and how helpful, unmapped or low-coverage questions are tagged for training, and the bot hands over to a Freshdesk agent when it cannot answer. The knowledge base itself appears as a tier feature with "multilingual helpdesk" at Pro, but we found no public information on article workflow, versioning, review dates, or agents inserting articles into replies; the "Up to 80% resolution rates" figure sits on the product page with no indication of how it is measured. 1 2 8 9
Customer data protection
Show reasoningHide reasoning
How this is scored
A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights, and what the vendor does with attachments — judged on what executes rather than what is promised.
0 — No retention policy stated, no deletion path, agents all see everything, and no DPA is published.
3 — A DPA on request and coarse roles; deletion is described as something the customer arranges, and there is no stated retention period.
5 — A signable DPA published, configurable agent roles and queue-level visibility, a stated retention period, and deletion of a requester's data that can actually be executed.
8 — Automatic retention rules per queue or data category, attachment handling stated, an audit log of who opened which ticket, documented support for access and erasure requests, and pseudonymisation or 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.
The Support Lead
The sub-processor list is published, Freshworks states it is generally the processor rather than controller of hosted data, and audit logs come with the Enterprise plan. We found no public information on a published signable data processing agreement, a stated retention period, or documented support for access and erasure requests; the only deletion path evidenced is the permanent, irreversible deletion of archived tickets. 3 2 4
The Agent Advocate
Roles and permissions ship from the bottom tier up, archived tickets can be permanently and irreversibly deleted, a sub-processor list is published, and Enterprise adds audit logs. But I found no public information on a signable DPA, a stated retention period for a requester's data, attachment handling, or a documented access or erasure path — and the privacy notice's description of sharing email addresses and identifiers with social advertising platforms is an uneasy read next to a ticket archive. 3 2 4
The Data Protection Officer
The one lifecycle that demonstrably executes is archiving — closed, inactive tickets are archived after 120 days and deleting an archived ticket is permanent and irreversible — alongside roles and permissions on the base plan, audit logs on Enterprise, a published subprocessor list, and the customer named as controller of hosted data. We found no public information on a signable data processing agreement, queue-level visibility, redaction, attachment handling, what happens to the data after archiving, or whether the vendor's own support can open a customer's ticket. 3 2 4
The Shop Operator
The engine can actually execute deletion — deleting an archived ticket is documented as permanent and irreversible — and the plans name roles and permissions plus audit logs. The privacy notice publishes a subprocessor list with confidentiality obligations, but we found no public information on a signable DPA, on a stated retention period for ticket data (the 120-day archive rule is workflow, not retention), or on documented support for access and erasure requests. 3 2 4
The Integrator
Roles and permissions ship from Growth, audit logs sit at Enterprise, a sub-processor list is published, and deleting an archived ticket is documented as permanent and irreversible. We found no public information on a signable data processing agreement, a stated retention period, requester-level erasure or access requests, or attachment handling, and the privacy notice describes sharing hashed email addresses and phone numbers with Facebook and LinkedIn for custom-audience advertising. 3 2 4
The Skeptic
Two things execute rather than promise: deleting an archived ticket is documented as permanent and irreversible, and a sub-processor list is published with access limited to "only as reasonably necessary", with roles and permissions named from the Growth tier. Against that, audit logs sit behind the Enterprise tier, we found no public information on a signable data processing agreement, per-queue retention rules, or an audit trail of who opened which ticket, and the privacy notice itself describes sharing hashed visitor identifiers with Facebook and LinkedIn for custom-audience advertising. 3 2 4
Integrations & API
Show reasoningHide 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 — No API and no named integrations; context is copied in by hand.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common CRM and shop systems, a documented REST API with keys, webhooks for the core ticket events, and SSO.
8 — Maintained bidirectional integrations, customer context from other systems shown inside the ticket, 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.
The Support Lead
The API library supports GET, PUT, POST, DELETE and JS functions with test runs, custom authorisation headers and reusable configurations, connectors are sold as metered add-ons at €80/5000 tasks, and there is a marketplace plus a sandbox on Enterprise. We found no public information on named CRM or shop integrations, documented rate limits, or SCIM provisioning, and the only webhooks evidenced are messenger event subscriptions. 3 2 6 10 11
The Agent Advocate
There is a marketplace for first- and third-party apps, pre-built connectors metered by the task, and a properly documented outbound API library with methods, authorisation headers, sample test runs and multipart file payloads. That library only speaks JSON and times out after 10 seconds, and I found no public information on named CRM or shop integrations, an inbound helpdesk API with documented rate limits, webhooks for core ticket events, or SCIM provisioning. 3 2 10 11
The Data Protection Officer
The bot platform's API library is documented in working detail — methods, authorisation headers, test runs, a ten-second timeout and multipart file payloads — and pre-built connectors, MCP actions and a marketplace of first- and third-party applications are all named, with a sandbox on the top plan. We found no public information on integrations named for CRM or shop systems, webhooks for core ticket events, single sign-on for agents, SCIM provisioning or documented rate limits. 3 2 10 11
The Shop Operator
There is a real integration surface: pre-built connectors for data sync priced per five thousand tasks, MCP actions priced per thousand, a marketplace of first- and third-party apps, and a documented API library inside the bot builder covering GET, PUT, POST and DELETE, authorisation headers, test runs and file payloads. But for a shop like mine the order context is the point, and we found no public information naming any CRM or shop integration, showing order data inside the ticket, or covering product single sign-on, webhooks or documented rate limits. 3 2 8 10 11
The Integrator
An application marketplace for first- and third-party apps, metered pre-built connectors, MCP actions priced per thousand, and a documented bot-side API library with custom headers, test runs, file attachments and debug logs are all evidenced, and a sandbox ships at Enterprise. But what is documented is the product calling out — I found no public information on a documented REST API for building against the helpdesk itself, rate limits, webhooks for ticket events, or SCIM provisioning, and no CRM, shop or identity system is named. 3 2 8 10 11
The Skeptic
The documented API here is the bot builder calling outward — GET, PUT, POST and DELETE with headers and authorisation, test runs, a 10-second timeout, and multipart form data for file uploads — alongside a marketplace platform and metered "pre-built connectors" at €80/5000 tasks. We found no public information on a documented REST API over the helpdesk itself with keys, named CRM or shop integrations, webhooks for core ticket events, or documented rate limits, and the sign-in services described are Google, Facebook Connect and LinkedIn for the vendor's websites rather than enterprise single sign-on for agents. 3 2 10 11
European sovereignty
panel opinion
Show reasoningHide 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.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — support tooling, analytics, AI features — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, 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.
The Support Lead
The contracting parent is a Delaware company and processing is named in the United States, the UK and the EEA, with the EU-U.S. Data Privacy Framework offered as the safeguard. EU entities such as Freshworks GmbH and Freshworks Technologies B.V. exist and the sub-processor list is published, but the captured pages do not confirm where the hosted ticket archive itself is stored. 3 6
The Agent Advocate
The contracting default is a Delaware company, the notice leans on the EU-US Data Privacy Framework, and processing is stated for the United States, the UK and the EEA wherever its third parties sit; I found no public information confirming where the hosted ticket archive itself lives, and the bot service's data centres named in the docs include the US, India and Australia. EU entities in Germany, France and the Netherlands and a published sub-processor list keep this off the floor, but we found no public information showing EU hosting as standard. 3 6
The Data Protection Officer
The contracting parent is Freshworks Inc. of Delaware and the notice relies on the EU-US Data Privacy Framework while processing personal data in the United States, the UK, the EEA and wherever its third parties are based; the vendor's own captured pages do not confirm where hosted customer data resides, and hashed identifiers are shared with social platforms for advertising. A published subprocessor list, EU group entities and a Europe data centre for the bot webhooks — alongside US, India and Australia — keep this a step above nothing. 3 6
The Shop Operator
This is an American vendor — Freshworks Inc. of Delaware — processing personal data in the United States, the United Kingdom and the EEA and relying on the EU-U.S. Data Privacy Framework, though EU contracting entities in Germany, the Netherlands and France exist depending on the customer. A subprocessor list is published and the bot platform exposes a Europe data-centre endpoint, but data residency for the ticket archive itself is not confirmed on the vendor's own captured pages, and for a European buyer that unknown is the whole question. 3 6
The Integrator
The parent is Freshworks Inc. of Delaware, processing is described across the United States, the United Kingdom, the EEA and countries where third parties are based, and transfers rest on the Data Privacy Framework; German, Dutch and French entities are also named as controllers. Data residency is not confirmed on the vendor's captured pages, though a sub-processor list is published and a Data Hosting page is referenced. 3
The Skeptic
The contracting parent is a Delaware company relying on the EU-US, UK and Swiss Data Privacy Frameworks, and processing is stated for the United States, the United Kingdom and the EEA "and in other countries where third parties that we may use are based"; where the hosted archive resides is not confirmed on the captured pages, which only point to a Data Hosting page. A sub-processor list is published, Freshworks entities exist in Germany, the Netherlands and France, and the bot webhooks offer separate US, Europe, India and Australia data centres — but we found no public information showing EU hosting as the standard for a customer's ticket archive. 3 6
Pricing transparency
Show reasoningHide 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 per-agent headline exists, but the tier where the needed channel or SLA feature begins is unstated, or light-agent and contact limits are not mentioned.
5 — Per-agent prices public for the main tiers with billing period stated, but at least one commonly needed capability (telephony, messengers, SLA policies) sits in an unpriced bundle.
8 — Every tier and add-on priced publicly with per-agent maths, 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.
The Support Lead
All three tiers are public per-agent with the billing period stated — €17, €52 and €84 /agent/month billed annually — alongside day passes and metered add-ons such as €45/100 AI Agent sessions and €13/1000 MCP actions, so most of my annual agent invoice is computable from the pricing page. VAT treatment and minimum term are not stated, however, and we found no public information on telephony pricing. 2
The Agent Advocate
One pricing page gives me €17, €52 and €84 /agent/month billed annually, day passes at €2/€7/€12, and metered add-ons priced by the hundred sessions, thousand actions or five thousand tasks, so the agent count plus AI usage is computable from public pages. The chat product the WhatsApp deployment depends on and the telephony product are separately priced with no figures captured here, and I found no public information on VAT treatment or minimum term. 2 7
The Data Protection Officer
All three plans carry public per-agent prices with the billing period stated — Growth at €17, Pro at €52 and Enterprise at €84 per agent per month billed annually — plus per-tier day passes and metered prices for AI sessions, connector tasks and MCP actions, and the feature lists show which tier SLA policies and audit logs belong to. Computing the real invoice still trips on unstated VAT treatment and minimum term, and we found no public price for the chat product the WhatsApp deployment depends on. 2 7
The Shop Operator
The per-agent maths is public and unusually granular: "€17 /agent/month, billed annually" at Growth, €52 at Pro, €84 at Enterprise, with day passes at €2, €7 and €12 per pass and metered add-ons priced by the unit — €45/100 sessions, €80/5000 tasks, €13/1000 actions. What I cannot compute from these pages is my real invoice: the WhatsApp route runs through Freshchat and calls through Freshcaller, and we found no public prices for either, nor VAT treatment or minimum terms. 2
The Integrator
All three tiers are priced per agent with the billing period stated — €17, €52 and €84 per agent per month, billed annually — alongside day passes at €2, €7 and €12 and metered prices for extra AI sessions, connector tasks and MCP actions, with plan lists showing where SLA policies and the sandbox begin. We found no public information on VAT treatment, minimum term, or the cost of the separate chat and telephony products, so the full annual invoice is still not computable from public pages. 3 2
The Skeptic
All three tiers carry public euro prices with the billing period stated — Growth €17, Pro €52 and Enterprise €84 per agent per month, billed annually — and the metered pieces are unusually explicit: day passes at €2, €7 and €12 per pass, additional AI Agent sessions at €45/100 sessions beyond the 500 included in every tier, plus priced connector tasks and MCP actions. A support lead still cannot compute the real annual invoice, because telephony and live chat sit in separate Freshworks products with no prices on these pages, and VAT treatment and minimum term are unstated. 2
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 31 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Data residency. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 24 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 16 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Product page www.freshworks.com Checked 15 Sep 2026 Details →
- 2 Pricing www.freshworks.com Checked 15 Sep 2026 +2 earlier captures: 11 Sep 2026, 31 Aug 2026 Details →
- 3 Privacy policy www.freshworks.com Checked 15 Sep 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
- 5 Ticketing, queues & SLA — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
- 6 Channels in one queue — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
- 7 Channels in one queue — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
- 8 Knowledge base & deflection — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
- 9 Knowledge base & deflection — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
- 10 Integrations & API — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →
- 11 Integrations & API — found from sitemap support.freshworks.com Checked 5 Oct 2026 Details →