HelpSpace
EU-Made 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 HelpSpace GmbH · helpspace.com
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.
HelpSpace at a glance
- Vendor
- HelpSpace GmbH
- Headquarters
- Incorporated in Germany source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Starting price
- “Starter $12 /user/month Starts with 2 Users Up to 5 Users 2 Email Channels 1 Docs Sites 2 Task Boards” (vendor’s words) source, captured 19 Oct 2026
- Panel verdict
- The AI panel rates HelpSpace 3/5, the mean of 6 judges. HelpSpace, a helpdesk from HelpSpace GmbH in Germany for small and medium-sized teams, is priced publicly at Starter $12 /user/month, Team $20 /user/month and Business $40 /user/month. how scores are made
- As of
- Vendor pages captured 19 Oct 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
HelpSpace, a helpdesk from HelpSpace GmbH in Germany for small and medium-sized teams, is priced publicly at Starter $12 /user/month, Team $20 /user/month and Business $40 /user/month. The highest scores land on integrations and ticketing core, both at 6-7: rules with team and round-robin assignment, merge and split, internal notes and per-ticket SLA deadlines and reminders, plus an open API with technical documentation, webhooks verified by a shared secret, and native Shopify and Xentral context showing orders and ERP data beside the ticket. The low mark is customer data protection at 4, with no public information on agent roles, queue-level visibility, audit logs, retention rules or redaction. Omnichannel scores 4-5: email, forms and an Instagram channel in beta share one inbox, with no public information on live chat, telephony, messengers or a customer portal. The ticketing split is narrow — judges at 7 call it a real engine, judges at 6 hold back because business-hours-aware SLA policies, breach warnings and escalation are undocumented. Knowledge self-service and pricing transparency sit at 6; sovereignty at 5.
Speaks for it
- Rules, automations and team routing with round-robin assignment, merge and split, internal notes, and settable deadlines, reminders or SLAs on tickets
- Native Shopify and Xentral integrations show customer data, orders, shipping status and ERP data beside the ticket
- Open API with technical documentation and webhooks verifiable with a secret, plus single sign-on via OpenID Connect or SAML 2.0
- Docs help centre on your own domain in three styles with multilingual articles, versioning, translation and article ratings, usable directly from the ticket interface
- All three tiers priced publicly per user per month with per-tier limits listed, and a 15-day trial with no payment details and no automatic renewal
Held against it
- No public information on agent roles or queue-level visibility limits, per-queue retention rules, audit logs of agent access, or redaction of ticket content
- Documented channels are email, forms and an Instagram channel in beta, with no public information on live chat, telephony, messengers or a customer portal
- SLA documentation goes as far as deadlines, reminders or SLAs per ticket, with no public information on business-hours-aware policies, breach warnings or escalation
- Only the payment subprocessor Paddle.com Market Limited is named, with no public information on a published subprocessor list with locations or a named data-centre provider
- No public information on VAT treatment, minimum term or annual billing, so the annual invoice is only partly computable from the published prices
Best for
- Your small team works email and forms in one shared inbox and wants rule-based routing with round-robin assignment
- You run a shop on Shopify or an ERP on Xentral and want orders, shipping status and customer data beside each ticket
- You want a branded public help centre on your own domain with multilingual articles agents can pull into replies
- You need a German contracting entity, hosting stated in a high-security data center located in the European Union, and a signable DPA
Avoid if
- Your queue needs live chat, telephony or WhatsApp-style messengers — the documented channels are email, forms and an Instagram channel in beta
- Your data-protection review requires documented agent roles, audit logs or redaction — customer data protection is the lowest score in the table at 4
- You must compute the full annual invoice from published pages — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 3.5 of 5 |
| Channels in one queue | 2.5 of 5 |
| Knowledge base & deflection | 3 of 5 |
| Customer data protection | 2 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3 of 5 |
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 — 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
Rules and automations with team routing, round-robin and agent assignment, global search, split and merge, and deadlines, reminders or SLAs are all documented, alongside an agent performance report and customer satisfaction ratings in reports. What I could not find is anything on business-hours-aware SLA policies, breach warnings or escalation, or first-response and resolution-time reporting by queue — the Monday-morning essentials I judge an engine on. 2 5 2 5
The Agent Advocate
Rules and automations route to teams, round-robin spreads the load, and Global Search, merge/split and the customer's previous tickets are the day-one basics done right. What I don't see is the hard edge: the captured pages describe deadlines, reminders or SLAs for tickets without business-hours policies, breach warnings or escalation, and agent performance reporting appears as a named line without first-response and resolution time broken out by queue. 2 5 2
The Data Protection Officer
Rules and automations route incoming tickets to teams, round-robin spreads assignment, and split, merge, global search, internal notes and an agent performance report are documented, with SLA deadlines, reminders and automatic status changes settable per ticket. What keeps me below calling this managed workload is the absence of any documented business-hours-aware SLA policy per queue with breach warnings and escalation, and of any audit of every status change. 2 5 2 5
The Shop Operator
Rules and automations route incoming mail to teams with round-robin assignment, SLA deadlines and reminders, split and merge, internal notes, global search and an agent performance report — a real engine, not just a shared inbox. What I would want before trusting a queue through a December peak is business-hours-aware SLA policies with breach warnings and escalation, and we found no public information on those. 2 5
The Integrator
Rules route incoming tickets to teams, with agent and round-robin assignment, global search, merge and split, canned replies, internal notes, wait-until status changes and an agent performance report, plus deadlines, reminders and SLAs on tickets. That is solid rule-based routing with useful mechanics, but we found no public information on business-hours-aware SLA policies per queue or customer, breach warnings, or escalation paths. 2 5 2 5
The Skeptic
The pricing page lists Ticket Management, Rules & Automation, Agent/Team Assignment and Round Robin, and the ticketing pages document teams that route incoming tickets, merge and split, global search, an agent performance report, and the ability to "set deadlines, reminders, or SLAs for tickets". That SLA sentence is as far as the documentation goes — I found no public information on business-hours-aware policies, breach warnings or escalation — which leaves this clearly above simple routed ticketing but short of managed workload. 2 2 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 — 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 and forms, plus Instagram in beta, land as tickets in one shared inbox, and the agent can see the customer's previous tickets and link duplicates. I found no public information on telephony, WhatsApp or comparable messengers, or a customer portal where requesters see their own tickets, so the basics are covered but the harder channels are not evidenced. 5 5
The Agent Advocate
Email, forms and an Instagram channel in beta land in one shared inbox, and the agent sees the requester's earlier tickets — honest small-team omnichannel, not a wall of logos. We found no public information on live chat, WhatsApp, telephony or a customer portal where requesters can see their own tickets, so the channel count stops there. 5 5 1
The Data Protection Officer
Email, forms and an Instagram channel — the Instagram one explicitly in beta — land in one shared inbox, and the agent sees the customer's previous tickets and can link duplicates. We found no public information on live chat, telephony, messengers such as WhatsApp, or a portal where a requester can see their own tickets. 1 5 5
The Shop Operator
Email, forms and an Instagram channel still in beta land in one central inbox with the customer's previous tickets visible, and Shopify orders show in a sidebar next to the conversation — that half of my test passes. The other half does not: we found no public information on a WhatsApp channel, live chat, telephony or a customer portal where a requester sees their own tickets. 5 6 5
The Integrator
Email, forms and an Instagram channel (in beta) land as tickets in one shared inbox, and the agent sees the customer's previous tickets and history while answering, with duplicates linkable. We found no public information on telephony with call logging, WhatsApp or similar messengers, or a customer portal where a requester can see their own tickets. 1 5 2 5
The Skeptic
Three channels are documented actually landing in one inbox with one history — "email, forms, and Instagram into one central inbox", with the customer's previous tickets visible and linkable to spot duplicates — though Instagram is explicitly in beta. I found no public information on live chat, telephony call logging, WhatsApp-style messengers with consent handling, or a portal where a requester sees their own tickets. 1 5 5
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 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
Docs run as a public help centre with its own domain, custom styling, multilingual articles, translation and versioning, and agents can use the knowledge base and canned responses directly from the ticket interface. I found no public information on article suggestions before a customer submits or while an agent answers, or reporting on which articles deflect — the GenAI chatbot that answers before support is a third-party integration, not a documented in-product deflection loop. 1 2 6 2 5
The Agent Advocate
Docs ships as a branded help centre on your own domain in three styles, with multilingual articles, versioning, ratings and canned replies straight from the ticket screen; a branchly chatbot integration can answer customers before support gets involved. We found no public information on suggesting articles to customers before they submit or on reporting which articles actually deflect, which is where deflection becomes a number. 2 2 5 6 1
The Data Protection Officer
Docs ship as a public help centre on the customer's own domain with article ratings, multilingual articles, article translation and article versioning, and agents can pull the knowledge base and canned responses directly into the reply interface. Deflection is addressed only through the third-party branchly chatbot integration; we found no public information on article suggestions to a customer before they submit or reporting on which articles deflect tickets. 1 6 2 5
The Shop Operator
A branded public help centre in three styles with its own domain, multi-language articles, translation and versioning, and agents pull knowledge base content and canned responses straight into the reply; a GenAI chatbot integration answers from the same Docs before support gets involved. Whether it actually cuts the ticket count is the part I cannot verify: we found no public information on article suggestions before submission or reporting that shows which articles deflect tickets. 1 6 2 5
The Integrator
Docs ships as a branded public help centre on your own domain in three styles, with multilingual articles, article versioning and ratings, usable from the ticket interface alongside canned responses, and a GenAI chatbot integration answers customers before they open a ticket. We found no public information on draft and publish states, review dates, or reporting that ties articles to deflected ticket volume. 1 2 6 2 5
The Skeptic
Docs is genuine self-service: own domain, custom CSS, multi-language, article versioning and translation, article ratings, three site styles, and agents using the knowledge base and canned responses directly from the ticket interface. I found no public information on article suggestions to customers before they submit or reporting on which articles deflect, so the reduction-in-tickets side of the ledger rests unproven on the public pages. 1 2 5
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 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 DPA is signable online, GDPR compliance is claimed, deletion after contract end and data portability are documented, and 2FA, penetration tests and ISO-certified data centres are stated. I found no public information on agent roles limiting what an agent can see or do, retention rules per queue or data category, an audit log of agent access, or redaction of ticket content — a DPO walk-through would stop at those gaps. 3 4
The Agent Advocate
A signable data processing agreement, GDPR claims with a named legal basis, deletion after contract end, portability and a named payment subprocessor give a decent floor. But the captured pages say nothing about agent roles or queue-level visibility, audit logs or redaction of ticket content — exactly what a data-protection audit of a ticket archive asks for. 4 3 2
The Data Protection Officer
A Data Processing Agreement can be signed, the privacy policy names the responsible German entity, states deletion after termination of the business relationship and addresses portability, and trial accounts are deleted automatically. For an archive of self-typed personal data I still need what the pages do not show: agent roles and queue-level visibility, automatic retention or deletion rules per queue, redaction of ticket content, an audit log of who opened which ticket, and a documented answer on whether vendor support can read customer tickets. 2 3 4 2
The Shop Operator
A privacy policy and a signable data processing agreement are published, GDPR compliance is asserted, customer data is stated to be deleted after termination of the business relationship, and portability plus two-factor authentication are documented. For a ticket archive, though, we found no public information on agent roles limiting ticket visibility, per-queue retention rules, audit logs or redaction of ticket content. 3 4
The Integrator
A privacy policy with a stated GDPR legal basis and a signable DPA are published, customer data is deleted after the business relationship ends, two-factor authentication exists, and a payment subprocessor is named. We found no public information on agent roles or queue-level visibility, deletion of individual tickets or a requester's data within the product, audit logs, attachment handling, or redaction. 3 4 2
The Skeptic
A DPA is offered — "Easily sign a Data Processing Agreement (DPA) with HelpSpace" — and the privacy policy documents deletion of customer data after termination, a right to data portability, and SSL/TLS, while 2FA and SSO cover login. I found no public information on agent roles or queue-level visibility limits, per-queue retention rules, attachment handling, an audit log of agent access, or redaction of ticket content. 3 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 — 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
A documented open API with webhooks carrying verification secrets, Zapier access to 7,000+ apps, Slack, and Shopify and Xentral showing customer orders and data beside the ticket, plus a custom sidebar framework and a widget JavaScript API. I found no public information on a maintained app marketplace, SCIM provisioning, documented rate limits or a sandbox, which keeps this short of the top band. 2 6 5
The Agent Advocate
An open API with technical documentation, verifiable webhooks, and a Custom Sidebar that shows Shopify orders or ERP data next to the ticket is precisely the one-screen context I want after six years of tab-hopping. We found no public information on an app marketplace of maintained integrations, SCIM provisioning, documented rate limits or a sandbox, so it sits a tier below the big ecosystems. 6 5 2 4 2
The Data Protection Officer
An open API with technical documentation, webhooks verifiable by a shared secret, and native Shopify and Xentral connections that surface order and ERP data next to the ticket, plus a Custom Sidebar for any app and single sign-on via OpenID Connect or SAML 2.0, give real in-ticket context. We found no public information on an app marketplace, SCIM provisioning, documented rate limits or a sandbox. 2 4 6 5
The Shop Operator
This is the part I care about most: Shopify is built in natively so customer data, orders and shipping status sit next to the ticket, Xentral ERP shows in the same sidebar, and behind it sit a public API, webhooks with verification secrets, technical documentation, a JavaScript widget API and a custom sidebar framework, plus single sign-on via OpenID Connect or SAML 2.0. We found no public information on an app marketplace, SCIM provisioning, rate limits or a sandbox. 2 4 6 5
The Integrator
The integrations page links to technical documentation for an open API and webhooks — with a secret to verify webhook payloads — plus native Shopify and Xentral connectors surfacing orders, shipping status and ERP data next to the ticket, a Custom Sidebar for external apps, custom-field mapping across CRM, project and shop tools, and single sign-on over OpenID Connect and SAML 2.0. What I would need before wiring this into a pre-existing CRM, shop and identity provider is not on the pages: we found no public information on documented rate limits, webhook retry behaviour, SCIM provisioning, or a sandbox environment. 2 4 6 5
The Skeptic
The integrations page shows an open API with technical documentation, webhooks carrying a verification secret, native Shopify and Xentral showing orders and ERP data beside the ticket, Slack, CentralStationCRM, Zapier with over 7,000 apps, and a Custom Sidebar for external apps, with SSO via OpenID Connect or SAML 2.0. I found no public information on an app marketplace, SCIM provisioning, documented rate limits, or a sandbox. 4 6 2
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. 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
HelpSpace GmbH with an address in Bad Vilbel is the responsible entity, hosting is stated as a high-security data centre in the European Union, a DPA is offered, and the German state data protection officer is named as the complaint authority. The subprocessor chain is barely visible — only the payment processor is named — and I found no named data-centre provider or published subprocessor list with locations, so the chain is proven only at the top. 1 3 4
The Agent Advocate
EU hosting in ISO-certified data centres is stated outright, the contracting entity is HelpSpace GmbH in Germany, and a DPA is offered — the European chain is proven at its three key links. The subprocessor picture stops at a payment processor named in the privacy policy; we found no published subprocessor list with locations and no named data-centre provider. 4 3 1
The Data Protection Officer
Hosting is stated as a high-security data center located in the European Union, the responsible and contracting entity is HelpSpace GmbH in Bad Vilbel, Germany, and a DPA is offered — that is EU hosting, EU entity and a DPA together. The subprocessor chain is not published as a list with locations; the privacy policy names only the payment processor Paddle, and we found no public information on a named data-centre provider or on how vendor support access to customer instances is governed. 1 3 4
The Shop Operator
The contracting entity is HelpSpace GmbH in Bad Vilbel, Germany, hosting is stated as a high-security data centre in the European Union with ISO 27001 and 9001 certified data centres, a DPA is signable, and the pitch is a solution Made in Germany. One payment subprocessor is named, but we found no public information on a published subprocessor list with locations or a named data-centre provider. 1 3 4
The Integrator
HelpSpace GmbH in Bad Vilbel is the contracting and responsible entity, hosting is stated to be in a high-security data centre in the European Union with ISO 27001 and ISO 9001 certified data centres, and a DPA is offered; a payment subprocessor, Paddle.com Market Limited, is named in the privacy policy. We found no public information on the named data-centre provider, a published subprocessor list with locations, or vendor support access to customer instances. 1 3 4
The Skeptic
HelpSpace GmbH at Backsteinweg 3, Bad Vilbel is the responsible and contracting entity, the security page states hosting "in a high-security data center located in the European Union" with ISO 27001 certified data centers, and a DPA is offered. The privacy policy names one subprocessor — Paddle.com Market Limited for payments — alongside unspecified "other third party service providers", and I found no public information on a named data-centre provider, a published subprocessor list with locations, or the vendor's own support access to customer instances. 1 3 4
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 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
All three tiers are public per user per month — Starter $12 /user/month, Team $20 /user/month, Business $40 /user/month — with user, email channel, docs site and task board limits per tier, and a 15-day trial with no payment details and no automatic renewal. I found no public information on VAT treatment, minimum term or annual billing, so the true annual invoice still needs one question to sales. 1 2 2
The Agent Advocate
Three tiers priced per user per month with user minimums and per-tier email channels, docs sites and task boards — a support lead can read the invoice shape off one page, and the 15-day trial is clean with no card required and no automatic renewal. VAT treatment, minimum term and any add-on prices are not stated on the captured pages, which keeps it short of full computability. 2 2 1
The Data Protection Officer
All three tiers carry public per-user monthly prices with user minimums and maximums and the email-channel, docs-site and task-board limits listed per tier, alongside a 15-day trial with no payment details and no automatic renewal. A support lead can compute the per-agent bill from these pages; we found no public information on annual billing terms, minimum contract term or VAT treatment. 1 2 2
The Shop Operator
All three tiers are priced publicly per user — Starter at $12 /user/month, Team at $20 /user/month, Business at $40 /user/month — with user counts, email channels, docs sites and task boards enumerated per tier, and a 15-day trial with no payment details and no automatic renewal. We found no public information on VAT treatment, minimum terms or annual billing, so I still cannot compute the full annual invoice from public pages alone. 1 2 2
The Integrator
All three tiers are public — Starter $12, Team $20, Business $40 per user per month — with user minimums and caps plus per-tier limits on email channels, docs sites and task boards, unlimited articles, customers, organizations and widgets, and a 15-day trial needing no payment details with no automatic renewal. We found no public information on VAT treatment, annual billing options, minimum terms, or any add-on or channel costs, which keeps the annual invoice only partly computable from public pages. 1 2 2
The Skeptic
All three tiers are public per user per month — Starter $12 /user/month, Team $20 /user/month, Business $40 /user/month — with user ranges, per-tier limits for email channels, docs sites and task boards, AI features flagged on Business, and a 15-day trial without payment details or automatic renewal. A support lead still cannot compute the real annual invoice from these figures alone: I found no public information on VAT treatment, minimum term, annual-versus-monthly rates, or add-on and channel usage costs. 1 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 |
Incorporated in DE
unverified
Why unverified?The address appears in the privacy policy as the responsible party rather than on a dedicated imprint page, though the GmbH form and German address are consistent. |
2/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
Questions about HelpSpace
Is HelpSpace European?
Yes. whats-best.ai classifies HelpSpace as EU-Made. Its vendor, HelpSpace GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does HelpSpace store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does HelpSpace have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to HelpSpace?
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: HelpSpace alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 19 Oct 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, Transfer impact assessment, Hosting location. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The address appears in the privacy policy as the responsible party rather than on a dedicated imprint page, though the GmbH form and German address are consistent.
- 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.
- 13 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
- 9 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
- 2 legal 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 subprocessors 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are 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 (6)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage helpspace.com Checked 16 Nov 2026 Details →
- 2 Pricing helpspace.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 3 Privacy policy helpspace.com Checked 16 Nov 2026 Details →
- 4 Security / trust page helpspace.com Checked 16 Nov 2026 Details →
- 5 Ticketing, queues & SLA — found from sitemap helpspace.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 6 Integrations & API — found from sitemap helpspace.com Checked 16 Nov 2026 Details →