whats-best.ai
Search Sign in

Customer Service & Helpdesk

HubSpot Service Hub

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 4 dimensions proven

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

by HubSpot, Inc. · www.hubspot.de

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 Integrator

Weighted verdict

Has to wire the helpdesk into a CRM, a shop and an identity provider that all predate it. Wants a documented API with rate limits, webhooks that retry, SCIM, and a sandbox. Reads a partner-contact form on an integrations page as a missing API.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Integrator

Ticketing, queues & SLA

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.

Report an error

The Integrator

Ticket automation, skills-based routing and team-based organisation are stated, SLAs exist with conditional SLAs reserved for the Enterprise tier, and macros, helpdesk areas, custom reports and dashboards carry published per-tier limits. Enterprise additionally promises sophisticated routing and capacity planning, which reads as capacity-aware assignment. I found no public information on business-hours-aware SLA policies, escalation chains, ticket merge and split, or an audit of every status change. 2 2 6 2

Report an error

Channels in one queue

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.

Report an error

The Integrator

Email, live chat, phone and WhatsApp land in one helpdesk, and the vendor states that all conversation information is preserved so the team can switch channels within the same ticket. Built-in calling from tickets logs calls automatically, WhatsApp carries a stated monthly message limit, and a customer portal is named alongside private knowledge-base access groups. I found no public information on consent handling specific to the messenger channel — the consent tooling named covers forms, live chat and meetings. 2 2 6

Report an error

Knowledge base & deflection

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.

Report an error

The Integrator

A knowledge-base agent analyses tickets and customer interactions to detect knowledge gaps and generates draft articles the team reviews before publishing, and the AI customer agent resolves requests across chat, email, forms and calls, with claimed deflection figures published. Reply recommendations for agents and article limits per tier are also stated. I found no public information on multilingual articles, review dates that flag stale content, or in-product reporting on which articles deflect; the seventeen languages quoted are interface languages. 2 6 7 2

Report an error

Customer data protection

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.

Report an error

The Integrator

The GDPR playbook documents executable, irreversible deletion with a warning on re-import, machine-readable exports, consent evidence storage and lawful-basis tracking, and a data processing agreement with standard contractual clauses sits inside the customer terms. The retention statement names only processing until there is no ongoing legitimate business need, with no fixed period. I found no public information on automatic retention rules per queue, attachment handling, an audit log of who opened which ticket, or redaction of ticket content. 3 3 8 9

Report an error

Integrations & API

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.

Report an error

The Integrator

Almost my whole checklist is on the page: around 1,900 prebuilt marketplace integrations with Jira, Slack, Facebook Messenger, Aircall, Dialpad and JustCall named, bidirectional data sync with dozens of apps, webhooks, custom objects, custom code actions, a custom channel API for any messaging or voice platform, single sign-on and a sandbox for testing changes. What holds me back is the fine print: I found no public information on SCIM user provisioning, documented API rate limits, webhook retry behaviour, or a versioning and deprecation policy. The developer documentation referenced on the captured pages covers Content Hub rather than the service APIs. 2 4 6 2

Report an error

European sovereignty

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.

Report an error

The Integrator

The contracting entity in the page footers is HubSpot, Inc. of the United States, with HubSpot Ireland Limited named only as data controller for website visitors in the EEA and UK. EU data residency in a German data center comes solely as a paid upgrade to the Starter version, the default hosting region is not stated, the platform runs on AWS, and the subprocessor list sits in an annex of the data processing agreement rather than on a public page. The certifications named are the EU-U.S. Data Privacy Framework set, which rests on U.S. enforcement. 2 3 3 4

Report an error

Pricing transparency

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.

Report an error

The Integrator

Per-license prices are public for every tier with the billing options quoted exactly — from Ab 7 €/Monat/Lizenz through Ab 90 €/Monat/Lizenz and 100 €/Monat/Lizenz to Ab 150 €/Monat/Lizenz — alongside required one-time onboarding fees of 1.470 € for Professional and 3.420 € for Enterprise, credits at 9,00 € pro 1.000 Guthabeneinheiten, and per-tier limits for calling minutes, phone numbers and WhatsApp messages. I cannot compute the real annual invoice from the pages alone: I found no public information on VAT treatment, a minimum term, or overage pricing once the included minutes and messages run out. The captured pages also give different figures for the free Customer Agent access window, fourteen days against twenty-eight. 2 2 2

Report an error

European sovereignty — proven facts

3 of 4 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.

Ownership Not determined — uncited Report an error
Data residency EU optional ⚠ unverified 1/3 pts 4 Report an error
Subprocessors US CLOUD Act reach ⚠ unverified 0/2 pts 4 Report an error

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.

Do you know more about HubSpot Service Hub? Tell us Report an error on this page

Sources (9)

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

  1. 1 Product page www.hubspot.de Checked 5 Oct 2026 +2 earlier captures: 15 Sep 2026, 31 Aug 2026 Details →
  2. 2 Pricing www.hubspot.de Checked 5 Oct 2026 +3 earlier captures: 28 Sep 2026, 15 Sep 2026, 15 Sep 2026 Details →
  3. 3 Privacy policy legal.hubspot.com Checked 5 Oct 2026 +1 earlier capture: 15 Sep 2026 Details →
  4. 4 Security / trust page www.hubspot.de Checked 5 Oct 2026 Details →
  5. 5 Privacy policy www.hubspot.de Checked 5 Oct 2026 Details →
  6. 6 Channels in one queue — found from sitemap www.hubspot.de Checked 5 Oct 2026 Details →
  7. 7 Knowledge base & deflection — found from sitemap www.hubspot.de Checked 5 Oct 2026 Details →
  8. 8 Customer data protection — found from sitemap www.hubspot.de Checked 5 Oct 2026 Details →
  9. 9 Customer data protection — found from sitemap www.hubspot.de Checked 5 Oct 2026 Details →