Customer Service & Helpdesk
HelpCrunch
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by HelpCrunch · helpcrunch.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
HelpCrunch is a chat-centred customer-service and helpdesk offering whose record splits sharply. Its highest scores come in omnichannel at 4-5, integrations at 4 and knowledge self-service at 3-4: live chat, email and the WhatsApp and Instagram messengers are stated to land in one dashboard; REST and JavaScript APIs, webhooks, mobile SDKs and Zapier are named; and a public help centre with WYSIWYG editing, SEO optimisation and an AI editor is evidenced. Weaknesses cluster in governance and workload: sovereignty scores sit at 0, with no sovereignty attributes on record and a contracting entity of HelpCrunch Corporation, Wilmington, Delaware; customer data protection spans 1-2, where judges split over how far a GDPR page carries with no public information on a signable data-processing agreement, retention or audit logs; and ticketing core scores 1-2, the pages evidencing an inbox with automation rather than an SLA engine. The 4-5 omnichannel split itself turns on whether one history follows the customer across channels, which the captured pages do not show.
Speaks for it
- Live chat, email and the WhatsApp and Instagram messengers are stated to unite in one dashboard, drawing omnichannel scores of 4-5.
- A named API surface — REST API, JavaScript API, webhooks, iOS, Android and React Native SDKs, plus Zapier — holds integrations at 4.
- A public help centre with a WYSIWYG editor, SEO optimisation, a stand-alone site or widget and an AI editor draws knowledge self-service scores of 3-4.
- Free data migration and a free trial with no credit card required are offered.
Held against it
- Ticketing core scores 1-2, the captured pages showing channel unification and marketing automation with no public information on assignment, routing, SLA timers or a status model.
- Sovereignty scores sit at 0, the contracting entity being HelpCrunch Corporation of Wilmington, Delaware, USA, with no sovereignty attributes on record.
- Customer data protection scores 1-2 on a GDPR page alone, with no public information on a signable data-processing agreement, retention periods or audit logs.
- Pricing transparency scores sit at 1, with no public per-agent prices, tiers or billing periods on the captured pages.
Best for
- You run support over live chat, email and the WhatsApp and Instagram messengers and want them handled in a single dashboard.
- You plan to build your own connectors against the named REST API, webhooks and mobile SDKs and reach other tools through Zapier.
- You want a public, SEO-optimised help centre that works as a stand-alone site or an in-product widget.
- You are moving from another solution and value free data migration alongside a free trial with no credit card required.
Avoid if
- You must run SLAs on a high-volume ticket queue — ticketing core scores 1-2, evidencing an inbox with automation rather than queues, routing or SLA timers.
- Your compliance review requires a signable data-processing agreement, stated retention periods or audit logs — customer data protection scores 1-2 on a GDPR page alone.
- You need a European chain of custody for your conversation archive — ask the vendor: the public pages we read do not show it
The scores
Ticketing, queues & SLA
Show reasoningHide reasoning
How this is scored
The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.
0 — A shared mailbox with labels; no ownership, no status model, no history beyond the thread.
3 — Tickets with assignment and open/closed status, but routing is manual, there are no SLA timers and search covers subject lines only.
5 — Queues with rules-based routing, priorities, a working status model, SLA timers with breach warnings, and full-text search across ticket bodies.
8 — Business-hours-aware SLA policies per queue or customer, escalation chains, macros and triggers, merge and split, and reporting on first-response and resolution time by agent and queue.
10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.
The Support Lead
The captured pages show one dashboard uniting live chat, email and the WhatsApp and Instagram messengers, with auto messages and chatbots pre-qualifying leads — that is inbox and channel plumbing, not an SLA engine. We found no public information on assignment and status models, rule-based routing, SLA timers with breach warnings, escalation chains, full-text search, or reporting on first-response and resolution time. That sits just above a shared mailbox and far from a queue my twelve agents could run an SLA on. 1
The Agent Advocate
The captured page sells a chat-and-messenger dashboard, not a ticketing engine: I found no public information on ticket assignment, queues, routing, SLA timers, macros, or search across ticket history. Multiple channels in one dashboard is a step above a shared mailbox, but nothing here shows the status model or ownership a team needs on a thousand-open-ticket day. 1
The Data Protection Officer
The captured pages speak of chats in one dashboard with auto messages and lead-qualifying chatbots, but I found no public information on ticket ownership, a status model, SLA timers, routing rules, escalation, or search across ticket bodies. What is evidenced is channel unification and marketing automation, not a workload engine. 1
The Shop Operator
Conversations from chat, email and messengers are stated to unite in one dashboard, but we found no public information on assignment and ownership, routing rules, SLA timers, a status model or search across tickets. For a thousand-parcel queue I see automation of incoming chat, not management of the work. 1
The Integrator
The captured pages describe a chat-centred product — auto messages, chatbots, lead pre-qualification and a shared dashboard — and we found no public information on ticket assignment, a status model, queues, SLA timers or full-text search. What is evidenced is a conversation inbox with marketing automation, not a ticketing engine an operator could run SLAs on. 1
The Skeptic
The captured page sells chat, messengers and marketing, and I found no public information on queues, routing rules, ticket ownership, a status model, SLA timers or search across ticket bodies. A shared dashboard with no evidenced ownership or SLA machinery is the honest reading. 1
Channels in one queue
Show reasoningHide reasoning
How this is scored
Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.
0 — Email only.
3 — Email plus one more channel, but the second lives in its own inbox: no shared history, and a customer who switches channel starts again.
5 — Email, a web form or portal and live chat all landing as tickets in one queue, with the customer's history visible whichever channel they used.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp, Signal or similar) with its consent handling stated, and a customer portal where a requester can see their own tickets.
10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.
The Support Lead
Live chat, email and the WhatsApp and Instagram messengers are confirmed landing in one dashboard, which reads as a genuinely shared inbox rather than a logo wall. We found no public information on telephony with call logging, a customer portal where a requester sees their own tickets, or how messenger consent is handled, so I credit the unified multi-channel case and stop there. 1
The Agent Advocate
Live chat, email, and messengers including WhatsApp and Instagram are stated to land in one dashboard, which is real channel convergence. I found no public information on telephony, a portal where requesters see their own tickets, WhatsApp consent handling, or whether one customer history follows them across channels, so this reads as channels gathered rather than channels unified. 1
The Data Protection Officer
Live chat, email and messengers including WhatsApp and Instagram are stated to land together in one dashboard, which is the substance of a shared queue. I found no public information on telephony, a customer portal where a requester sees their own tickets, messenger consent handling, or whether history follows the customer across channels. 1
The Shop Operator
Live chat, email, WhatsApp and Instagram are stated to land in one dashboard, which is the single queue I judge by — the messenger part is real and named, not just logos. We found no public information on telephony, a customer portal, WhatsApp consent handling, or whether a customer switching channel mid-issue keeps one history. 1
The Integrator
Live chat, email and messengers including WhatsApp and Instagram are said to unite in one dashboard, which is a genuine multichannel claim. We found no public information on telephony, a customer portal, messenger consent handling, or whether the customer's history follows them across channels, so this sits between a basic second channel and a full single-queue story. 1
The Skeptic
Live chat, email, WhatsApp and Instagram are claimed 'in one dashboard', which is four channels on one screen, but I found no public information on whether they share one queue and one history, and no portal, telephony or consent handling is described. The channel logos are counted; the single conversation behind them is asserted, not evidenced. 1
Knowledge base & deflection
Show reasoningHide reasoning
How this is scored
Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.
0 — No knowledge base; answers live in agents' heads and old tickets.
3 — A basic article list, public or internal, with no editorial workflow, no versioning and no link between articles and tickets.
5 — A searchable public help centre with categories, draft and publish states, and agents able to insert an article into a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates that flag stale content, and reporting on which articles deflect.
10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.
The Support Lead
A public help centre is confirmed — WYSIWYG editor, SEO optimisation, usable as a stand-alone site or in-widget — plus an AI editor for drafting articles, which is more than a bare article list. But we found no public information on draft and publish workflow, versioning, review dates, article suggestions to customers or agents, or reporting on which articles deflect, so knowledge looks like a publishing surface rather than a managed asset. 1
The Agent Advocate
A knowledge base with a WYSIWYG editor, SEO optimization, and both a stand-alone help centre and an in-widget version is evidenced, plus an AI editor for writing articles. I found no public information on search, categories, draft and publish workflow, review dates, any link between articles and tickets, or deflection measurement, so this is a basic public article list rather than a managed asset. 1
The Data Protection Officer
A public help centre with a WYSIWYG editor, SEO optimisation and stand-alone site or widget delivery is evidenced, alongside an AI editor for writing articles. I found no public information on draft-and-publish states, versioning, review dates, article suggestions to customers or agents, or any deflection reporting. 1
The Shop Operator
A full-fledged public help centre with a WYSIWYG editor, SEO optimisation and a stand-alone site or widget is evidenced, plus an AI editor for writing articles. We found no public information on editorial workflow, versioning, article suggestions to customers before they submit, or any deflection reporting — I can't tell from this page whether the ticket count falls in December. 1
The Integrator
A knowledge base with a WYSIWYG editor, SEO optimisation, and a stand-alone site or widget is confirmed, alongside an AI editor for writing help articles. We found no public information on editorial workflow, versioning, inserting articles into replies, suggestions to customers or agents, multilingual content, or any deflection reporting. 1
The Skeptic
A public help centre is described with a WYSIWYG editor, SEO optimisation and a stand-alone site or widget, plus an AI editor for writing articles. I found no public information on draft and publish states, agents inserting articles into replies, suggestions before submission or deflection reporting, so it reads as publishing tooling rather than a managed knowledge asset. 1
Customer data protection
Show reasoningHide reasoning
How this is scored
A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights, and what the vendor does with attachments — judged on what executes rather than what is promised.
0 — No retention policy stated, no deletion path, agents all see everything, and no DPA is published.
3 — A DPA on request and coarse roles; deletion is described as something the customer arranges, and there is no stated retention period.
5 — A signable DPA published, configurable agent roles and queue-level visibility, a stated retention period, and deletion of a requester's data that can actually be executed.
8 — Automatic retention rules per queue or data category, attachment handling stated, an audit log of who opened which ticket, documented support for access and erasure requests, and pseudonymisation or redaction of ticket content.
10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.
The Support Lead
The only protection fact on record is that a GDPR page exists, and that is a promise rather than an executed control. We found no public information on a signable DPA, stated retention periods, a deletion path that can actually be run, agent roles and queue-level visibility, or an audit log of who opened which ticket — and a ticket archive is personal data the data subject wrote themselves. 1
The Agent Advocate
A GDPR page exists; beyond that I found no public information on a signable DPA, retention periods, agent roles or queue-level visibility, deletion paths for a requester's data, audit logs, or attachment handling. For a product holding chat transcripts the visitor wrote themselves, that silence lands close to the bottom of the scale. 1
The Data Protection Officer
A GDPR page exists and nothing more: I found no public information on a signable DPA, a stated retention period, deletion that actually executes, agent roles or queue-level visibility, an audit log of who opened which ticket, redaction, or attachment handling. For a product meant to hold years of customers' own typed words, including the things they should not have sent, that silence decides the score. 1
The Shop Operator
A GDPR page is stated to be available, and free data migration is offered, but we found no public information on a published or signable data-processing agreement, retention periods, deletion of a requester's data that can be executed, agent roles and visibility, or an audit log of who opened which conversation. 1
The Integrator
Only the existence of a GDPR page is confirmed; we found no public information on a signable DPA, retention periods, agent roles or queue visibility, executable deletion of a requester's data, audit logs, or attachment handling. Protection here rests entirely on one compliance page whose contents are not captured. 1
The Skeptic
A GDPR page exists, and that is the whole of the record here: I found no public information on retention periods, an executable deletion path, agent roles or queue visibility, audit logs, or a published signable data-processing agreement. A compliance page is a promise; nothing that executes is evidenced. 1
Integrations & API
Show reasoningHide reasoning
How this is scored
The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.
0 — No API and no named integrations; context is copied in by hand.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common CRM and shop systems, a documented REST API with keys, webhooks for the core ticket events, and SSO.
8 — Maintained bidirectional integrations, customer context from other systems shown inside the ticket, SCIM provisioning, documented rate limits and a sandbox.
10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.
The Support Lead
The API surface is listed as REST API, JavaScript API and webhooks, with iOS, Android and React Native SDKs, plus Zapier for the long tail — webhooks alone lift this clear of a read-only API. We found no public information on named CRM or shop integrations, SSO, SCIM provisioning, documented rate limits or a sandbox, so the ecosystem rides on Zapier rather than maintained connectors. 1
The Agent Advocate
A genuine API surface is listed — REST API, JavaScript API, webhooks, and iOS, Android and React Native SDKs — with Zapier on top. But the integrations pitch names no specific tool, and I found no public information on CRM or shop integrations, SSO, documented rate limits, or a sandbox, so this sits between a modest offering and a documented ecosystem. 1
The Data Protection Officer
A REST API, webhooks, a JavaScript API and mobile SDKs are named, plus Zapier, which is a genuine building surface rather than a brochure list. I found no public information on named CRM or shop integrations, SSO, SCIM provisioning, documented rate limits, or a sandbox. 1
The Shop Operator
REST and JavaScript APIs, webhooks, iOS, Android and React Native SDKs and Zapier are named, which is a genuine developer surface. We found no public information on named shop or CRM integrations, SSO, rate limits, or customer order context shown inside the conversation — the order-in-front-of-the-agent-without-a-second-login piece I need is not evidenced. 1
The Integrator
The API surface is named — JavaScript API, REST API, webhooks, and iOS, Android and React Native SDKs — with Zapier for further connections and free data migration offered. But we found no public information on API documentation, rate limits, SSO, SCIM provisioning, a sandbox, or named CRM, shop or identity integrations, so this is a list of interface names rather than evidence of one I could build against. 1
The Skeptic
REST API, webhooks, a JavaScript API, iOS, Android and React Native SDKs plus Zapier are publicly named, which is a real building surface. I found no public information on named CRM or shop integrations, SSO, SCIM, documented rate limits or a sandbox, so the catalogue behind the API surface is not evidenced. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — support tooling, analytics, AI features — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.
The Support Lead
The contracting entity is HelpCrunch Corporation, 1811 Silverside Rd, Wilmington, DE — a US entity — and the sovereignty pipeline has no attributes on record for this vendor. We found no public information on where the ticket archive is hosted, the data-centre provider, or any subprocessor list; a GDPR page signals compliance intent but carries no location facts. I cannot tell my DPO where the data sits or who else touches it, which is the worst case for this buyer. 1
The Agent Advocate
The contracting entity is HelpCrunch Corporation of Wilmington, Delaware — a US entity — and nothing is on record about hosting location, subprocessors, or where the chat archive is stored. No certification is named, and as this buyer weighs it, that lands at the bottom of the scale. 1
The Data Protection Officer
The contracting entity is HelpCrunch Corporation of Wilmington, Delaware, hosting is unstated, and no subprocessor list appears anywhere captured — a GDPR page title is offered in place of any of this. I found no public information on EU hosting, a data-centre provider, or whether the vendor's own support can open a customer's ticket, which is the question I would ask first. 1
The Shop Operator
The contracting entity is HelpCrunch Corporation of 1811 Silverside Rd, Wilmington, DE, USA, and hosting location is unstated. We found no public information on EU hosting options, subprocessors, or where the ticket archive actually sits, which for me is the whole question. 1
The Integrator
The contracting entity is HelpCrunch Corporation, 1811 Silverside Rd, Wilmington, DE 19810, USA, and we found no public information on hosting location, data-centre provider, subprocessors, or vendor support access to customer data. Nothing in the evidence speaks to a European chain of custody for the archive. 1
The Skeptic
The contracting entity is HelpCrunch Corporation of Wilmington, Delaware, hosting location is unstated, no subprocessor list appears and no sovereignty attributes are on record. For a buyer weighing where the ticket archive lives and who can read it, the published material offers a Delaware copyright line and a GDPR page, nothing more. 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A per-agent headline exists, but the tier where the needed channel or SLA feature begins is unstated, or light-agent and contact limits are not mentioned.
5 — Per-agent prices public for the main tiers with billing period stated, but at least one commonly needed capability (telephony, messengers, SLA policies) sits in an unpriced bundle.
8 — Every tier and add-on priced publicly with per-agent maths, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.
The Support Lead
We found no public prices in the captured pages — no per-agent figure, no tier structure, no billing period — so an annual invoice for my headcount is not computable from anything published here. The pricing facts that do exist carry no numbers: unlimited contacts and chats, a free trial with no credit card required, and free data migration. Budget planning means a sales conversation. 1
The Agent Advocate
The only cost facts the captured page gives are a free trial without a credit card, free data migration, and unlimited contacts and chats; I found no public per-agent prices, tier names, billing periods, or VAT treatment. A support lead could not compute even a rough annual invoice from this — there is nothing to compute with. 1
The Data Protection Officer
The only pricing facts captured are a free trial with no credit card required and the claim of "Unlimited contacts and unlimited chats"; I found no public information on per-agent prices, tiers, billing period, minimum term, or where channels and SLA features begin. A support lead cannot compute an annual invoice from what is on the record. 1
The Shop Operator
No price figure appears on the captured page; the only pricing statements are 'Unlimited contacts and unlimited chats' and a free trial with no credit card required. We found no public information on per-agent prices, tiers, billing periods, minimum terms or VAT treatment, so the annual invoice for my agent count cannot be computed. 1
The Integrator
The captured pages state "Unlimited contacts and unlimited chats", a free trial with no credit card required, and free migration — commercial terms, but we found no public information on per-agent prices, tiers, billing periods, add-ons or usage limits. A support lead could not begin to compute an annual invoice from what is public here. 1
The Skeptic
The captured pricing language is 'Unlimited contacts. Unlimited chats.' alongside a free trial with no credit card required, and I found no public information on per-agent prices, tier structure, billing period, minimum term or VAT treatment. A support lead cannot compute even a rough annual invoice from this page. 1
European sovereignty — proven facts
1 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 2 Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Sep 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 residency. The claim appears only in a 2018 GDPR marketing blog post rather than a DPA or trust page, and even there payment information is held by the US processor Stripe rather than on HelpCrunch's own EU servers.
- Weak sourcing — Subprocessors. 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.
- 8 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
- 5 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
- 4 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
- 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 pricing 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page helpcrunch.com Checked 29 Sep 2026 Details →
- 2 Security / trust page — found from the homepage helpcrunch.com Checked 30 Sep 2026 Details →
- 3 Ticketing, queues & SLA — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →
- 5 Channels in one queue — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →
- 6 Knowledge base & deflection — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →
- 7 Knowledge base & deflection — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →
- 8 Customer data protection — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →
- 9 Customer data protection — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →
- 10 Integrations & API — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →
- 11 Integrations & API — found from sitemap docs.helpcrunch.com Checked 1 Oct 2026 Details →