HubSpot Service Hub

Rest of world Report an error

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 HubSpot, Inc. · www.hubspot.de

Report an error on this page Is this your product? →

Link to this page

HubSpot Service Hub: AI-assisted analysis on whats-best.ai HubSpot Service Hub: 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.

HubSpot Service Hub at a glance

Vendor
HubSpot, Inc.
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 15 Sep 2026
Starting price
“Ab 7 €/Monat/Lizenz 20 €/Monat/Lizenz” (vendor’s words) source, captured 15 Sep 2026
Panel verdict
The AI panel rates HubSpot Service Hub 2.5/5, the mean of 6 judges. Two judges recorded 0 on every criterion, unexplained by their reasoning; the four others scored 3-9, never more than two points apart. how scores are made
As of
Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

HubSpot Service Hub alternatives, European ones first →

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

The Support Lead

Weighted verdict

Runs a team of twelve against an SLA the sales team promised. Wants routing that reflects skill, timers that warn before they breach, and reporting she can take to a quarterly review. Reads "AI-powered" as a claim to be checked against the queue on a Monday morning.

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

Scored by The Support Lead

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

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 — 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

Skills-based routing, incoming tickets automatically assigned to the right team, SLAs with conditional SLAs at the Enterprise tier, macros by tier, and helpdesk areas for queue organisation give me most of the routing spine my team needs. I found no public information on SLA breach warnings, ticket merge and split, or first-response and resolution reporting broken out by agent and queue, and the documented routing and capacity planning at Enterprise is as close as the pages get to capacity-aware assignment. 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 — 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, live chat, built-in calling from within tickets with automatic call logging, WhatsApp with a monthly message allowance, Facebook Messenger, and a customer portal at the Professional tier are all documented, and the pages state the team can switch channels within the same ticket with all conversation information preserved. AI reply recommendations are stated to work across all channels. I found no public information on consent handling for WhatsApp, so I stop one band short of the top. 6 2 2

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 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

A knowledge base with per-tier article limits, an AI agent that reads tickets to find knowledge gaps and produces drafts the team reviews before publishing, and auto-resolve figures the captured pages give as both 65 and 70 percent of conversations — that is deflection expressed as a number. I found no public information on multilingual articles, stale-content flags or versioning, or reporting on which specific articles deflect. 2 2 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 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 included in the customer terms, and the GDPR toolset is concrete: irreversible GDPR-compliant deletion with a warning if a deleted contact returns, machine-readable exports for access and portability requests, permission control with advanced permissions at Enterprise, and consent plus lawful-basis tracking. I found no public information on per-queue retention rules, attachment handling, an audit log of agent access, or redaction of ticket content. One item I would put in front of legal: the privacy policy states personal data may be processed to develop and train HubSpot's own AI models. 3 9 3 2 8

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 — 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

The pages document an app marketplace they count between roughly 1,800 and over 2,000 apps, bidirectional data sync with dozens of apps, webhooks plus custom objects and custom code actions, single sign-on, a sandbox account, and CRM context inside the ticket, with a channel API for building our own connectors. I found no public information on SCIM provisioning, documented API rate limits, or a versioning and deprecation policy for the API. 6 2 2 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. 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

European elements are proven — a German data centre offered as a benefit of the paid Starter tier, an Irish entity named as controller for EEA and UK website visitors, and a data processing agreement included in the terms — but the vendor publishes as a United States company and leans on the EU-U.S. Data Privacy Framework. Where our ticket archive sits by default and the contracting entity for the service itself are not established by the captured pages, which is not enough for my DACH risk review. 4 3 3

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 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

Per-license prices are public for all tiers, with required one-time onboarding fees of 1.470 € and 3.420 € stated exactly, monthly credit allowances per tier, 9,00 € per 1.000 credit units with annual payment, and usage costs such as 50 credits per resolved AI conversation. Three gaps block a fully computable invoice: the Starter price appears only as a time-limited 65 percent discount at 7 € per month per license, VAT treatment and minimum term are not stated, and the captured pages give different figures for the Enterprise license at 150 € and 175 € per month. Calling minutes and WhatsApp message allowances per tier are published, though I found no per-unit overage price. 2 2 2 2

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?

The EU data center is presented only as a benefit of upgrading to the paid Starter tier, and no excerpt states where data is hosted by default (free hosting runs on AWS infrastructure with no region given).

— uncited Report an error
Hosting options Not determined unverified
Why unverified?

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

— uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The privacy policy only references the agreement; the agreement text itself is not reproduced in these excerpts.

1/1 pts 3 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about HubSpot Service Hub

Is HubSpot Service Hub European?

No. whats-best.ai classifies HubSpot Service Hub as Rest of world.

Where does HubSpot Service Hub store data?

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

Does HubSpot Service Hub have a free plan?

Yes. HubSpot Service Hub has a free plan, per the vendor’s page captured 15 Sep 2026.

What are the best alternatives to HubSpot Service Hub?

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: HubSpot Service Hub 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 (10)

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 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 15 Sep 2026, 31 Aug 2026 Details →
  2. 2 Pricing www.hubspot.de Checked 16 Nov 2026 +4 earlier captures: 5 Oct 2026, 28 Sep 2026, 15 Sep 2026, 15 Sep 2026 Details →
  3. 3 Privacy policy legal.hubspot.com Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
  4. 4 Security / trust page www.hubspot.de Checked 16 Nov 2026 Details →
  5. 5 Privacy policy www.hubspot.de Checked 16 Nov 2026 Details →
  6. 6 Channels in one queue — found from sitemap www.hubspot.de Checked 16 Nov 2026 Details →
  7. 7 Knowledge base & deflection — found from sitemap www.hubspot.de Checked 16 Nov 2026 Details →
  8. 8 Customer data protection — found from sitemap www.hubspot.de Checked 16 Nov 2026 Details →
  9. 9 Customer data protection — found from sitemap www.hubspot.de Checked 16 Nov 2026 Details →
  10. 10 Structured-data backfill: markup only, no text or screenshot www.hubspot.de Checked 8 Nov 2026 Details →