HubSpot Service Hub
Rest of world Report an errorPanel 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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Two judges recorded 0 on every criterion, unexplained by their reasoning; the four others scored 3-9, never more than two points apart. Among those four, HubSpot Service Hub is strongest on omnichannel and knowledge and self-service — email, live chat, phone, WhatsApp and Facebook Messenger in one queue, channel switching within the same ticket with conversation information preserved, a knowledge-base agent drafting articles from ticket gaps. Weakest is sovereignty: the vendor is HubSpot, Inc. of Cambridge, Massachusetts, the German data centre appears only as a Starter-upgrade benefit, and the default hosting region and contracting entity are unstated on the captured pages. Customer data protection sits at 6 (no public information on per-queue retention or agent-access audit logs; a privacy policy stating personal data may be processed to train the vendor's own AI models) and pricing transparency at 7, despite two Enterprise prices (150 €/Monat/Lizenz and 175 €/Monat/Lizenz). The agent advocate scored highest on ticketing core, omnichannel and knowledge for agent-workflow reasons; the support lead gave sovereignty 3, short of a DACH risk review.
Speaks for it
- Email, live chat, phone with automatic call logging, WhatsApp and Facebook Messenger land in one helpdesk queue, with channel switching inside the same ticket
- A knowledge-base agent detects gaps from tickets and drafts articles for team review before publishing
- The GDPR toolset includes a data processing agreement in the customer terms with standard contractual clauses for EU/EEA customers, irreversible deletion with a re-add warning, machine-readable exports and stored consent evidence
- CRM core is included in every version, so the customer record sits with the ticket
- Per-license prices are public for every tier, with required one-time onboarding fees of 1.470 € (Professional) and 3.420 € (Enterprise) printed
Held against it
- Sovereignty is the weakest criterion: the vendor is HubSpot, Inc. of Cambridge, Massachusetts, the German data centre appears only as a Starter-upgrade benefit, and the default hosting region and contracting entity are unstated on the captured pages
- The privacy policy states that personal data from use of the products may be processed to develop, support and improve HubSpot AI features and to train its AI models
- We found no public information on per-queue retention rules, an audit log of agent access, redaction of ticket content or attachment handling
- The captured pages give different figures for the Enterprise license (150 €/Monat/Lizenz and 175 €/Monat/Lizenz) and for free customer-agent access (14 and 28 days), and Starter appears only at a time-limited 65 % discount (7 €/Monat/Lizenz)
- WhatsApp sits behind the Professional tier with a stated cap of 1,000 messages per month, and phone numbers are stated as not supported in all countries
Best for
- You need one queue across email, live chat, phone, WhatsApp and Facebook Messenger, with the team able to switch channels inside the same ticket while conversation information is preserved
- You want metered, published AI deflection: the customer agent costs 50 credit units per resolved conversation from the Professional tier, and the captured pages give auto-resolve figures of both 65 %+ and 70 %+
- Your team works CRM-first and wants the customer record inside every ticket rather than in a separate system
- You want to pilot before committing: the free version is 0 €/Monat for up to 2 users, with no credit card required
Avoid if
- Your procurement requires EU hosting as standard and an EU contracting entity for the service itself — the captured pages present the German data centre only as a Starter-upgrade benefit and name HubSpot Ireland Limited only as controller for EEA and UK website visitors
- Your data-protection review cannot accept a privacy policy stating personal data may be processed to train the vendor's own AI models, or retention defined only as deletion or anonymisation once no ongoing legitimate business need remains, with no fixed period
- You need high-volume WhatsApp support — the integration sits behind the Professional tier with a stated cap of 1,000 messages per month
- You must compute a complete annual invoice from public pages before contacting the vendor — the captured pages give two Enterprise prices, Starter appears only at a time-limited 65 % discount (7 €/Monat/Lizenz), and required onboarding fees of 1.470 € and 3.420 € come on top
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 3.5 of 5 |
| Channels in one queue | 4 of 5 |
| Knowledge base & deflection | 4 of 5 |
| Customer data protection | 3 of 5 |
| Integrations & API | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3.5 of 5 |
Ticketing, queues & SLA
panel disagrees
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 — 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.
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
The Agent Advocate
Routing is documented and real: incoming tickets assigned to the right team, skills-based forwarding, SLAs with conditional SLAs at the top tier, and macros with published per-tier limits; Enterprise adds routing and capacity planning, which is managing workload rather than tracking it. I found no public information on search that finds an old ticket from a half-remembered phrase, business-hours SLA policies, or merge and split, which is what keeps it off the top band. 2 2 6 2 2
The Data Protection Officer
The captured pages document a genuine helpdesk engine: incoming tickets assigned to the right team, routing based on agent skills, SLAs with conditional SLAs at the Enterprise tier, macros, and routing plus capacity planning for complex omnichannel setups. We found no public information on business-hours-aware SLA policies with breach warnings and escalation, ticket merge and split, or first-response and resolution reporting broken down by agent and queue, so we stop one level below the top. 2 6 2
The Shop Operator
Ticket routing to teams, skills-based routing, SLAs with conditional SLAs at the top tier, and macros at 500 and 1,500 are all documented, and the Enterprise tier advertises sophisticated routing and capacity planning. We found no public information on search across tickets, merge and split, or business-hours SLA policies with breach warnings and escalation, so I cannot place the engine higher. 2 6 2 2
The Integrator
Skills-based routing, assignment of incoming tickets to the right team, macros with published limits per tier, SLAs including conditional SLAs at the top tier, and at Enterprise sophisticated routing and capacity planning for complex omnichannel deployments are all documented. That reads as a real workload engine rather than a tracked inbox. We found no public information on business-hours SLA policies with breach warnings and escalation, on merging and splitting tickets, or on first-response and resolution-time reporting by agent and queue. 2 6 2
The Skeptic
Incoming tickets are assigned to teams by automation and routed by agent skills, SLAs exist with conditional SLAs reserved for Enterprise, macros carry 500 and 1,500 limits by tier, and Enterprise adds routing and capacity planning with custom reports — this is well past a shared inbox. But we found no public information on business-hours-aware SLA policies, breach warnings or escalation, merge and split, or first-response and resolution-time reporting by agent and queue, so I stop below the top band. 2 2 2 6 2 2
Channels in one queue
panel disagrees
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 — 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.
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
The Agent Advocate
Email, live chat, phone with a built-in calling tool that auto-logs calls, WhatsApp and Facebook Messenger all land in the helpdesk, with a customer portal at Professional and channel APIs for anything else the customer uses. The part I care about is stated outright: agents can switch channels within the same ticket with conversation history preserved, so the customer doesn't restart. Consent tooling is documented generically for forms, live chat and meetings rather than for a specific messenger, which costs it a point. 2 6 2
The Data Protection Officer
Email, live chat, built-in calling with automatic call logging, WhatsApp, Facebook Messenger and a customer portal are all documented as landing in the helpdesk, with all conversation information preserved and switching between channels inside the same ticket. Consent handling for the messenger channels is not stated on the captured pages, which is what keeps this below the top level. 2 6 2
The Shop Operator
Email, live chat, built-in calling with automatic call logging, WhatsApp and Facebook Messenger are documented as landing in one queue with all conversation information preserved, and the team can switch channels within the same ticket — that is WhatsApp and my shop in one queue, my basic test. We found no public information on consent handling specific to WhatsApp, which keeps this a step short of the top. 2 2 6 2
The Integrator
Email, live chat, phone with a built-in calling tool whose call activities are automatically logged, WhatsApp with stated monthly message limits, Facebook Messenger and forms all land as tickets, and the captured pages state that all conversation information is preserved so the team can switch channels within the same ticket. A customer portal where requesters see their own tickets is documented at the Professional tier, and a consent notice is documented for live chat. We found no statement of consent handling specific to WhatsApp and no public information on the customer moving between channels mid-issue; the channel switching documented is the team's. 2 6 9
The Skeptic
Email, live chat, phone with automatic call logging, WhatsApp, forms and a customer portal from the Professional tier all land in the helpdesk, and the vendor states agents can switch channels within the same ticket with all conversation information preserved — one queue and one history, not just a row of logos. Points off because WhatsApp and the portal sit behind the Professional tier, WhatsApp is capped at 1,000 messages per month, phone numbers are stated as not supported in all countries, and we found no public information on the messenger's consent handling. 2 2 6 2 2
Knowledge base & deflection
panel disagrees
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 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.
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
The Agent Advocate
This thinks about the hundredth reply: a knowledge base agent analyses tickets to detect gaps, drafts articles the team reviews before publishing, and the deflection number is published — 65 %+ of conversations auto-resolved, metered at 50 credit units per resolved conversation. Multiple knowledge bases with article limits per tier and private access groups shared with the customer portal are documented. I found no public information on per-article deflection reporting or multilingual articles, so I stop short of the top. 2 2 7 2
The Data Protection Officer
A knowledge base agent analyses tickets and detected knowledge gaps to draft articles the team reviews before publishing, successful interactions are turned into help articles automatically, and AI reply recommendations assist agents while they answer. We found no public information on versioning or review dates that flag stale articles, or on reporting that shows which articles deflect; the published resolution figure is a vendor claim about its AI agent rather than a deflection number the team can act on. 2 2 7 2
The Shop Operator
The knowledge base runs to 2,000 articles on Professional and 10,000 on Enterprise, and a Knowledge Base Agent analyses tickets to detect gaps and drafts articles for team review before publishing. Deflection comes from the AI Customer Agent, claimed at 65 to 70 percent of conversations resolved automatically; we found no public information on per-article deflection reporting, multilingual articles, or review dates flagging stale content. 2 7 2
The Integrator
The Knowledge Base Agent analyses tickets and customer interactions to detect knowledge gaps and generates draft articles the team reviews before publishing, and an AI customer agent resolves conversations automatically, with resolution rates published on the pricing pages. Article limits per tier, private knowledge bases with access groups, automatic language detection and seventeen interface languages are documented. We found no public information on article versioning or review dates, or on reporting that measures article performance against ticket volume by topic. 2 2 7 2
The Skeptic
A knowledge base with tiered article limits (2,000 articles on Professional, 10,000 on Enterprise) plus a knowledge-base agent that mines tickets and customer interactions for gaps and drafts articles the team reviews before publishing — gap-to-draft is managed-asset territory. Deflection is real but metered: the customer agent that auto-resolves conversations costs 50 credit units per resolved conversation and only from Professional, and we found no public information on article-level deflection reporting or multilingual articles. 2 2 2 7 2
Customer data protection
panel disagrees
Show reasoningHide 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.
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
The Agent Advocate
A data processing agreement sits in the customer terms with standard contractual clauses for EU customers, agent permissions are documented, and the GDPR playbook covers irreversible deletion, machine-readable export, contact correction, and stored consent evidence with a copy of the notice, the consent type and a timestamp. I found no public information on automatic retention rules per queue or data category, an audit log of agent access, redaction of ticket content, or attachment handling — those are what a data-protection audit would ask for first. 3 3 8 9 2
The Data Protection Officer
A data processing agreement included in the customer terms of service, GDPR-compliant irreversible deletion of contact records with a warning if a deleted contact is re-added, machine-readable export for access and portability requests, contact correction, and stored consent evidence (copy of the notice, type and timestamp) are all documented. We found no public information on retention rules that execute per queue or data category, on attachment handling, on redaction of ticket content, or on an audit log of who accessed what — the privacy policy states retention only as deletion once there is no ongoing legitimate business need, with no fixed period. A buyer must also weigh the vendor's statement that it may process personal data from use of its services to train its own AI models. 3 8 9 2
The Shop Operator
The GDPR tooling is documented in depth: a data processing agreement included in the customer terms with standard contractual clauses for EU customers, irreversible GDPR-compliant deletion with a warning if a deleted contact is re-added, machine-readable exports for access and portability requests, and consent records storing the notice shown, the consent type and a timestamp. We found no public information on automatic retention rules per queue, attachment handling, an audit log of agent access, or redaction of ticket content. The privacy policy also states that personal data may be processed to develop and train the vendor's own AI models, which a buyer under German data protection law will want in the risk assessment. 3 8 9 2
The Integrator
Subject rights are properly documented: a data processing agreement included in the customer terms with standard contractual clauses for EU and EEA customers, irreversible GDPR-compliant deletion of contact data with a warning if a deleted contact is re-added, machine-readable export for access and portability requests, and consent records storing the notice shown, the consent type and the timestamp. Access control appears as permissions to control data access and editing, with advanced permissions at Enterprise. We found no public information on automatic retention or deletion rules per queue or data category — the vendor's own policy states deletion or anonymisation when there is no ongoing legitimate business need, with no fixed period — nor on an audit log of agent access, attachment handling, or redaction of ticket content. 3 3 8 9 2
The Skeptic
A data processing agreement sits inside the customer terms with standard contractual clauses for EU/EEA customers, affiliate subprocessors are listed with locations in its annex, and the playbook documents irreversible GDPR-compliant deletion with a re-add warning, machine-readable export for access requests, correction, and stored consent evidence. We found no public information on automatic retention rules per queue, attachment handling, an audit log of agent access, or redaction of ticket content — and the privacy policy states HubSpot may process personal data from use of its products to improve and train its own AI models, a scope a buyer should nail down before signing. 3 3 8 9 2
Integrations & API
panel disagrees
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 — 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.
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
The Agent Advocate
Over 1,900 marketplace integrations with named tools like Jira and Slack, bidirectional data sync, webhooks, custom objects, custom code actions, a sandbox and single sign-on are all documented, and CRM context sits inside every ticket by design. The pages show single sign-on but we found no public information on SCIM provisioning or documented rate limits, and nothing on API versioning or a deprecation policy, so it stays just under the top band. 2 6 2 2
The Data Protection Officer
A large app marketplace (the captured pages give different figures, between roughly 1.800 and over 2.000 apps) with named connectors such as Jira, Slack and calling providers, bidirectional data synchronisation with dozens of apps, webhooks, custom objects and custom code actions, plus single sign-on and a sandbox account. We found no public information on SCIM provisioning or documented rate limits, which the next level expects. 2 6 2 2
The Shop Operator
The captured pages give different figures for the marketplace size — 1,800, 1,900 and 2,000-plus apps — and with it come bidirectional data sync with dozens of apps, webhooks, custom code actions and channel APIs for anything custom, plus single sign-on and a sandbox account. CRM core sits in every version, so the customer record is next to the ticket without a second login, which is my order-in-front-of-the-agent test. We found no public information on SCIM provisioning or documented rate limits. 6 2 2
The Integrator
This is the criterion I buy on, and the marketplace is substantial: bidirectional data synchronisation with dozens of apps, webhooks, custom objects, custom code actions, a custom channel API, single sign-on, a sandbox account for testing changes, and named connectors for Jira, Slack, Gmail, Outlook and Microsoft Exchange plus calling partners such as Aircall and Dialpad — though the captured pages give different figures for the app count (over 1,800, over 1,900 and over 2,000). Developer documentation is referenced. What holds me back: we found no public information on documented API rate limits, SCIM user provisioning, or an API versioning and deprecation policy — the API is described as developer-friendly, but I cannot see the documentation depth I would need to wire in a shop and an identity provider without opening a conversation. 4 6 2 2
The Skeptic
An app marketplace the captured pages size differently — 1,800, 1,900 and over 2,000 apps — with bidirectional data sync for dozens of them, webhooks, custom objects and custom-code actions, named links to Jira, Slack and Facebook Messenger, plus SSO and a sandbox account. CRM context is native to every version, so the customer record is inside the ticket rather than a copy-paste away. We found no public information on SCIM provisioning or documented rate limits, which keeps this below the top band. 2 2 6 2 2
European sovereignty
panel opinion
panel disagrees
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. 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.
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
The Agent Advocate
European elements are proven: a German data centre tied to the paid Starter tier, standard contractual clauses in the data processing agreement for EU customers, and HubSpot Ireland Limited named as controller for EEA and UK website visitors. The contracting entity for the service itself, the default hosting region, and the subprocessor locations are not stated on these pages — the annex listing affiliates and their locations is referenced but not reproduced. A US vendor under the Data Privacy Framework with the rest of the chain unstated is exactly the position I can only score in the middle band. 3 3 4 8
The Data Protection Officer
European elements are proven — a data centre in Germany offered as a benefit of upgrading to the paid Starter tier, a self-serve data processing agreement containing standard contractual clauses for EU and EEA customers, and HubSpot Ireland Limited named as controller for website visitors — but the contracting entity's seat is not stated and we found no public information on where data is hosted by default. The vendor sits under the EU-U.S. Data Privacy Framework with the U.S. Federal Trade Commission as enforcer, its own pages state that GDPR does not require storage within the EU, and affiliates act as subprocessors with their locations listed in an annex of the data processing agreement rather than on the public pages captured. 2 3 3 4 8
The Shop Operator
HubSpot, Inc. of Cambridge, Massachusetts is the name on every page, certified under the EU-U.S. Data Privacy Framework, and the Germany data centre appears in the captures only as a benefit of upgrading to the paid Starter tier; we found no public information on where data is hosted by default. A self-serve data processing agreement with standard contractual clauses and an affiliate subprocessor list with locations in its annex exist, and HubSpot Ireland Limited appears as controller for the vendor's own website visitors, but the contracting entity and hosting chain for a customer's ticket archive are otherwise unstated. 2 3 3 4
The Integrator
The contracting vendor is proven United States-based (HubSpot, Inc.), and the captured pages name HubSpot Ireland Limited only as controller of the vendor's own website data for EEA and UK visitors, not as the contracting entity for the service. European elements are proven — a data centre in Germany, presented as a benefit of upgrading to the paid Starter tier, and a data processing agreement with standard contractual clauses for EU and EEA customers — while the default hosting region, the service contracting entity and the locations of the affiliate subprocessors referenced in Annex 3 remain unstated on the captured pages. I credit what is proven and treat the rest as unknown rather than European. 2 3 3 4 8
The Skeptic
The vendor is HubSpot, Inc. of Cambridge, Massachusetts; the captured pages name HubSpot Ireland Limited only as controller for EEA and UK website visitors, and the one EU data centre named — Germany — is presented as a benefit of upgrading to the paid Starter version, with the default hosting region unstated on AWS infrastructure. A published data processing agreement with standard contractual clauses and a subprocessor annex exists, and US oversight under the Data Privacy Framework with FTC enforcement is stated. That is more than a single European element, yet neither EU hosting as standard nor an EU contracting entity for the service itself is established on these pages. 2 3 3 4
Pricing transparency
panel disagrees
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 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.
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
The Agent Advocate
Almost everything carries a number: per-license monthly prices for every tier, extra license prices, required one-time onboarding fees of 1.470 € for Professional and 3.420 € for Enterprise, credit units at 9,00 € per 1.000, plus calling minutes and WhatsApp allowances per tier. The annual invoice still isn't computable from the pages alone: the Starter figure carries a time-limited 65 % discount, the captured pages give different figures for Enterprise (ab 150 €/Monat/Lizenz and 175 €/Monat/Lizenz), AI usage is metered in credits that reset monthly, and we found no public information on VAT treatment, minimum terms, or per-minute telephony overage. 2 2 2 2
The Data Protection Officer
Every tier carries a public per-license price — free at 0 €/Monat for up to 2 users, Starter at 7 €/Monat/Lizenz under a time-limited 65 % discount, Professional at 90 €/Monat/Lizenz with annual billing and 100 €/Monat/Lizenz with monthly billing — and the pages state required one-time onboarding fees of 1.470 € (Professional) and 3.420 € (Enterprise), additional licenses at 90 € and 175 € per month, included monthly credit allowances of 5.000, 10.000 and 15.000, 9,00 € pro 1.000 Guthabeneinheiten, and limits for calling minutes, phone numbers and WhatsApp messages. The captured pages give different figures for the Enterprise license price, the Starter price appears only at the discounted rate, and we found no public information on VAT treatment or minimum term, so the annual invoice is close to computable but not fully. 2 2 2 2
The Shop Operator
Every tier carries a public per-license price — the captured pages give different figures for Enterprise, at 150 and at 175 euros a month per license — plus one-time onboarding fees of 1,470 and 3,420 euros for Professional and Enterprise, credit allowances of 5,000 to 15,000 per month priced at 9.00 euros per 1,000 credits with pay-as-you-go overage, and calling minutes, phone numbers and WhatsApp message limits by tier. The Starter price appears only as a time-limited 65 percent discount, and we found no public information on VAT treatment or minimum term, so the steady-state annual invoice for my agent count is not fully computable. 2 2 2 2
The Integrator
Per-licence prices are public for every tier with the billing period stated — Professional at 90 €/Monat/Lizenz with annual billing and 100 €/Monat with monthly billing — along with additional licences at 90 €/Monat/Lizenz and 175 €/Monat/Lizenz, mandatory one-time onboarding fees of 1.470 € for Professional and 3.420 € for Enterprise, and a metered credit system at 9,00 € pro 1.000 Guthabeneinheiten with per-tier monthly allowances and a per-resolved-conversation cost for the AI agent. The captured pages give different figures for the Enterprise licence (150 €/Monat/Lizenz and 175 €/Monat/Lizenz), and Starter appears only as a time-limited 7 €/Monat/Lizenz at 65 % Rabatt. We found no public information on VAT treatment or a minimum term, so the annual invoice for my agent count is close to computable from public pages but not fully. 2 2 2 2
The Skeptic
Per-license prices are public for every tier with the billing period shown for Professional (90 € per month per license on annual billing, 100 € on monthly), the required one-time onboarding fees of 1.470 € and 3.420 € are printed, extra seats carry per-license prices, and the metered AI is priced at 9,00 € per 1,000 credit units with monthly allowances of 5,000 to 15,000 that reset without rollover. But the captured pages give different figures for the Enterprise license (150 € 'from' versus 175 € per month per license) and for the free customer-agent trial (14 versus 28 days), the Starter figure of 7 € is a time-limited 65 % discount, and we found no public information on VAT treatment or a minimum term. 2 2 2 2 2
European sovereignty — proven facts
1 of 6 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
Why unverified?The vendor's pages name a local subsidiary and do not state the parent's seat. |
— | uncited Report an error |
|---|---|---|---|
| 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
- 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 — Data processing agreement. The privacy policy only references the agreement; the agreement text itself is not reproduced in these excerpts.
- Weak sourcing — Legal entity. The vendor's pages name a local subsidiary and do not state the parent's seat.
- Weak sourcing — Hosting location. 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).
- Weak sourcing — Hosting options. 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.
- 101 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
- 34 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
- 3 compliance 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
- 3 support 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 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Product page www.hubspot.de Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 15 Sep 2026, 31 Aug 2026 Details →
- 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 Privacy policy legal.hubspot.com Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 4 Security / trust page www.hubspot.de Checked 16 Nov 2026 Details →
- 5 Privacy policy www.hubspot.de Checked 16 Nov 2026 Details →
- 6 Channels in one queue — found from sitemap www.hubspot.de Checked 16 Nov 2026 Details →
- 7 Knowledge base & deflection — found from sitemap www.hubspot.de Checked 16 Nov 2026 Details →
- 8 Customer data protection — found from sitemap www.hubspot.de Checked 16 Nov 2026 Details →
- 9 Customer data protection — found from sitemap www.hubspot.de Checked 16 Nov 2026 Details →
- 10 Structured-data backfill: markup only, no text or screenshot www.hubspot.de Checked 8 Nov 2026 Details →