Customer Service & Helpdesk
Puzzel
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Puzzel AS · www.puzzel.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.
Puzzel at a glance
- Vendor
- Puzzel AS
- Headquarters
- Not stated on the vendor’s pages as of 27 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 27 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 27 Oct 2026
- Panel verdict
- The AI panel rates Puzzel 2.5/5, the mean of 6 judges. Puzzel AS is a Norwegian vendor selling an AI-powered customer-service platform that combines Contact Centre as a Service with Self-Service Automation; this bench judged its captured public pages only. how scores are made
- As of
- Vendor pages captured 27 Oct 2026; evaluated by the panel 27 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Puzzel AS is a Norwegian vendor selling an AI-powered customer-service platform that combines Contact Centre as a Service with Self-Service Automation; this bench judged its captured public pages only. Strongest is omnichannel, scoring 7-8: voice, chat, email, SMS and social are stated to sit in one workspace feeding a single customer view, with WhatsApp and Meta named. Ticketing core and customer data protection each sit at 4 — routing, prioritisation, internal notes and bulk actions are stated, but the bench found no public information on SLA timers, breach warnings, escalation chains, retention periods or audit logs. Pricing transparency scores 0 and is reported but not counted, as is normal in this market. The widest spreads, 4-6, appear on knowledge and self-service, integrations and sovereignty: higher scores credit the deflection-focused Public FAQ, connector depth and a European hosting posture; lower scores point to deflection asserted rather than measured, no public information on a documented API, and a sovereignty story that rests on the vendor's own account.
Speaks for it
- Voice, chat, email, SMS and social are stated to sit in one workspace feeding a single customer view, with WhatsApp and Meta named as channels
- Skill-based routing, ticket prioritisation, ticket attributes, internal notes and bulk actions are all stated for the ticketing module
- The catalogue names 45 integrations, including Salesforce, Microsoft Dynamics, Zendesk, Microsoft Teams and a Calabrio sync running every 15 minutes
- The GDPR statement provides a Data Processing Agreement, names the CISO as Data Protection Officer and cites an ISO 27001 certified ISMS
- The trust page states incorporation in Norway, hosting across an Oslo private cloud plus EU and UK Azure regions specified in the contract, no US data touchpoints and EU-based support
Held against it
- We found no public information on SLA timers, breach warnings, escalation chains or first-response and resolution-time reporting
- We found no public information on a stated retention period, agent roles, queue-level visibility or an audit log of who opened which ticket
- Beyond the connector catalogue we found no public information on a documented API, webhooks, rate limits, SCIM provisioning or a sandbox
- We found no published subprocessor list or named provider for the Oslo private cloud, and the independently sourced checks on contracting entity, residency and subprocessor exposure came back unconfirmed
- The captured pages show no pricing figures — no per-agent price, tier name or billing period — even though Case Management and the Public FAQ are sold as add-ons
Best for
- You run a European contact centre and want voice, chat, email, SMS and social landing in one queue with a single customer view per conversation
- Your agents already work inside Salesforce, Microsoft Dynamics, Zendesk or Microsoft Teams and should handle calls and customer context in that same screen
- You want to deflect repetitive questions with a searchable, branded Public FAQ published from a centralised knowledge base, with handoff to a live agent when needed
- A stated Norwegian incorporation, hosting specified in your contract across an Oslo private cloud and EU and UK Azure regions, and no US data touchpoints matter to your procurement
Avoid if
- You want a helpdesk-first product — ticketing sits inside Case Management, an add-on to the Puzzel CX Platform, and ticketing core scores cluster at 4 with the SLA machinery undocumented on the public pages
- You run an online shop and need order context in the queue — ask the vendor: the public pages we read do not show it
- Your procurement or DPO requires independently confirmed residency and a published subprocessor list before signature — the captured sovereignty checks on contracting entity, residency and subprocessor exposure came back unconfirmed
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 2 of 5 |
| Channels in one queue | 3.5 of 5 |
| Knowledge base & deflection | 2.5 of 5 |
| Customer data protection | 2 of 5 |
| Integrations & API | 2 of 5 |
| European sovereignty | 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 — 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
Skill-based routing, ticket prioritisation, attributes, internal notes and bulk actions are all evidenced, which is a genuine start for my twelve agents. I found no public information on SLA timers, breach warnings, escalation chains, or first-response and resolution reporting by agent and queue — the parts I defend at a quarterly review — so I can't trust this engine for the SLAs my team carries. 3 4
The Agent Advocate
Skill-based routing and ticket prioritisation are stated plainly, and detailed ticket notes for internal collaboration genuinely save the hunt for context. Beyond that I found no public information on SLA timers, a status model, macros, merge and split, or full-text search across ticket bodies — the parts that decide whether I can pull up the old thread on the hundredth reply — and ticketing itself arrives as an add-on to the wider platform rather than its core. 3
The Data Protection Officer
Ticketing arrives as an add-on module with attributes, tagging and prioritisation, skill-based routing, bulk actions and internal notes — real queue management, not a shared mailbox. But the captured pages stop short of the engine: I found no public information on SLA timers with breach warnings, escalation chains, a defined status model, search across ticket bodies, or any audit of status changes. Routing and priority are evidenced; measurement and history are not. 3 4
The Shop Operator
Skill-based routing, ticket prioritisation and attributes, bulk actions and internal notes are stated on the ticketing page, which is better than manual assignment, but I found no public information on SLA timers, breach warnings, escalation chains or reporting on first-response and resolution time. The only search claim is that notes save time in searching, which does not tell me an agent can find the parcel ticket from a half-remembered phrase. 3
The Integrator
Ticketing is described as an add-on with attributes, tagging, prioritisation, skill-based routing, internal notes and bulk actions — real queue mechanics, not just a shared inbox. But the captured pages say nothing about SLA timers, breach warnings, escalation chains or a status model, and I found no public information on search beyond notes and attributes or on reporting of first-response and resolution times by agent and queue. 3 4
The Skeptic
Skill-based routing, ticket prioritisation, attributes, bulk actions and internal notes are described on the ticketing page, which is more than a labelled mailbox and more than manual routing. I read for where SLA policies begin and found no public information on SLA timers, breach warnings, a status model, escalation chains or full-text search across ticket bodies — and ticketing itself is positioned as an add-on to the platform. 3
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
Voice, chat, email, SMS and social are stated to sit in one workspace with every channel feeding the same customer view so the conversation carries on where it left off, and WhatsApp and Meta are named alongside native telephony. I found no public information on a customer portal where a requester sees their own tickets, or on consent handling for messengers, which holds this below the top band. 4 8 6
The Agent Advocate
Voice, chat, email, SMS and social sit in one workspace with one customer view, and the vendor says the conversation carries on where it left off — exactly what I want after years of watching customers repeat themselves across tabs. WhatsApp and Meta are named as supported channels too. I found no public information on a customer portal where requesters see their own tickets, or on consent handling for the messengers. 4 8
The Data Protection Officer
Voice, chat, email, SMS and social sit in one workspace with a single customer view and the conversation carrying over between channels, and telephony is native to the platform rather than bolted on, with interaction records flowing to workforce tools. WhatsApp and Meta are supported channels. I found no public information on consent handling for messengers or a portal where a requester can see their own tickets. 4 8
The Shop Operator
Voice, chat, email, SMS and social are stated to sit in one workspace with one customer view so the conversation carries on where it left off, and WhatsApp is supported — that is the single queue I judge by. I found no public information on consent handling for the messenger, on a customer portal where a requester sees their own tickets, or on a shop or order-system integration landing in that queue. 4 8
The Integrator
Voice, chat, email, SMS and social are stated to sit in one workspace with every channel feeding the same customer view, and WhatsApp is named among the supported channels — that is most of the way to a genuine single queue. What holds it under the higher band: I found no public information on consent handling for messengers, and I found no public information on a customer portal where a requester can see their own tickets. 4 8
The Skeptic
Voice, chat, email, SMS and social are claimed in one workspace with every channel feeding the same view of the customer and the conversation carrying on where it left off, and WhatsApp and Meta are named beyond the logo row. I found no public information on consent handling for the messengers or on a portal where a requester can see their own tickets, which keeps this short of the band above. 4 8 6
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 searchable, branded public FAQ built on centralised Knowledge Management, with deflecting repeat contacts explicitly the goal and escalation from self-service to a live agent, is clearly evidenced. I found no public information on article categories, draft and publish states, agents inserting an article into a reply, review dates for stale content, or deflection reported as a number I could act on. 5 6
The Agent Advocate
The Public FAQ is more than a brochure — searchable, brandable for the website, aimed at deflecting repetitive questions before they reach the contact centre, with knowledge centralised across self-service, chatbots and live support. I found no public information on categories, draft-and-publish workflow, article suggestions to agents while they answer, review dates for stale content, or reporting on which articles actually deflect. 5 6
The Data Protection Officer
The Public FAQ is searchable, AI-optimised and published branded to the customer's website on a centralised knowledge base shared across self-service, chatbots and live support, and deflection is the stated purpose. That is a managed knowledge asset rather than an article dump. I found no public information on multilingual articles, review dates that flag stale content, editorial workflow, or reporting on which articles actually deflect. 5 6
The Shop Operator
A searchable Public FAQ published on the website and positioned explicitly as deflecting repetitive contacts before they reach the contact centre, plus virtual agents for chat, voice and email with handoff to live conversations, is a real deflection story. I found no public information on article suggestions to agents while answering, multilingual articles, stale-content review dates, or reporting on which articles deflect. 5 6
The Integrator
A searchable, branded Public FAQ publishes from a centralised knowledge store shared across self-service, chatbots and live support, with deflection as an explicit design goal and a stated hand-off from self-service to live conversations. I found no public information on categories, editorial draft states, agents inserting articles into replies, review dates for stale content, or per-article deflection reporting. 5 6
The Skeptic
The Public FAQ is searchable, branded for the customer's website and pitched as deflecting repetitive questions before they reach the contact centre, with knowledge centralised across self-service, chatbots and live support. But it is positioned as an AI-powered add-on to Knowledge Management, and I found no public information on draft and publish states, categories, inserting an article into a reply, multilingual content, stale-content review or deflection reporting — deflection is asserted, not measured on any captured page. 5 6
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 GDPR statement commits Puzzel as processor and controller, a Data Processing Agreement is provided, the CISO serves as Data Protection Officer, and the platform is described as able to quickly identify and delete end-user data on request. I found no public information on a stated retention period, configurable agent roles or queue-level visibility, audit logs of who opened which ticket, or attachment handling, so this reads as commitment plus a DPA rather than executed controls. 7 2
The Agent Advocate
The GDPR page gets specific where it counts: a Data Processing Agreement is provided, the CISO serves as Data Protection Officer, an ISO 27001 certified ISMS is claimed, and end-user data can be identified and deleted quickly on request. I found no public information on a stated retention period, configurable agent roles or queue-level visibility, attachment handling, or an audit log of who opened which ticket. 7 2
The Data Protection Officer
The GDPR statement is more than a nod: a Data Processing Agreement is provided, the CISO is named Data Protection Officer, ISO27001 is certified, and end-user data can be quickly identified and deleted on request with consent collection documented. What I cannot find is what an audit runs on: no stated retention period, and no public information on agent roles, queue-level visibility, an audit log of who opened which ticket, attachment handling, redaction, or a subprocessor list. Deletion that executes on request is real; retention left unstated is the gap. 2 7
The Shop Operator
The GDPR statement offers a Data Processing Agreement, names the CISO as Data Protection Officer, cites an ISO 27001 certified ISMS, and describes quickly identifying and deleting end-user data on request — deletion that executes rather than something the customer arranges. I found no stated retention period, and no public information on audit logging, attachment handling, or role-based ticket visibility. 7
The Integrator
The GDPR statement provides a Data Processing Agreement, names the CISO as Data Protection Officer, cites an ISO 27001-certified ISMS, and describes being able to quickly identify and delete end-user data on request. But I found no public information on a stated retention period, agent roles or queue-level visibility, attachment handling, redaction, or an audit log of who opened which ticket. 7 2
The Skeptic
The GDPR statement offers a DPA, an ISO27001-certified ISMS, a CISO assigned as DPO, and the ability to quickly identify and delete end-user data on request plus documented approvals — subject-rights support is at least written down. I found no public information on a stated retention period, configurable agent roles or queue-level visibility, an audit log of who opened which ticket, or attachment handling, and the DPA is described as provided rather than published for signature. 7 2
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
Forty-five integrations are listed with named CRM and collaboration connections — Salesforce, Microsoft Dynamics, Teams, Zendesk — and a bidirectional Calabrio sync every fifteen minutes is described in real detail. I found no public information on a documented API, webhooks, rate limits, SCIM provisioning or a sandbox, which matters to me when I want to build rather than browse a catalogue. 8 4
The Agent Advocate
Forty-five named integrations is a real catalogue, the Calabrio write-up describes actual mechanics — full data synchronisation every fifteen minutes with the record types spelled out — and the Salesforce, Dynamics and Zendesk connectors keep handling inside one screen. For the builder's half of the question I found no public information on a documented API, webhooks, rate limits or a sandbox, which caps what I can credit. 8 6
The Data Protection Officer
Forty-five listed integrations include maintained, bidirectional ones — Calabrio synchronises agent and interaction data every fifteen minutes, and Salesforce, Microsoft Dynamics and Zendesk put calls and customer context inside the agent's screen. That is integration depth, not logo count. I found no public information on a documented REST API, webhooks, rate limits, a sandbox or SCIM provisioning, so a buyer cannot yet build against this platform on paper. 4 8
The Shop Operator
Forty-five named integrations include Salesforce with SSO, a Microsoft Dynamics CRM widget, Zendesk embedded so agents handle calls without switching screens, and a Calabrio workforce sync every 15 minutes — genuine CRM context in front of the agent. No shop or order-management system appears in the named list, and I found no public information on a documented REST API, webhooks, rate limits, SCIM or a sandbox. 8
The Integrator
The connector catalogue is real: 45 named integrations spanning Salesforce, Microsoft Dynamics, Zendesk, Microsoft Teams, WhatsApp and a Calabrio workforce-management sync running every 15 minutes, with the agent application embedded inside CRMs as well as CRMs inside Puzzel. But as the one who has to wire a helpdesk into a CRM, a shop and an identity provider, the captured pages show vendor-built connectors and I found no public information on a documented API, webhooks and their retry behaviour, rate limits, SCIM provisioning or a sandbox — the difference between a connector list and an integration platform. 8 6
The Skeptic
Forty-five integrations are listed with real substance in a few — Calabrio synchronises data every fifteen minutes, Zendesk embeds Puzzel calls inside its own interface, and Microsoft Dynamics gets a CRM widget. I counted the logos: several entries are voice-analysis connectors and one is a headset maker, and beyond the list I found no public information on a documented API, webhooks, rate limits, SCIM or a sandbox. 8 6
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
Norway incorporation, hosting across an Oslo private cloud plus EU and UK Azure regions specified in the contract, a stated absence of US data touchpoints, and EU-based support give me a European posture I could take to procurement. I found no public information on a published subprocessor list or a self-hosted option, so the chain end to end is not evidenced. 2 1
The Agent Advocate
The trust page makes European claims with unusual specificity: incorporated in Norway, an Oslo private cloud plus EU and UK Azure regions named in the contract, EU-based support and AI processing, and no US data touchpoints. I found no public information on a published subprocessor list, so the picture rests on the vendor's own word, and while the UK Azure option is named in the contract I found no public information on a legal basis for that non-EU processing. 2 7
The Data Protection Officer
The captured pages show a Norwegian contracting entity, hosting in an Oslo private cloud plus EU and UK Azure regions specified in the contract, EU-based support, no US data touchpoints and AI processing in Europe — the posture I want. But independent sourcing could not confirm the legal entity or data residency from the vendor's own captured pages, and I found no published subprocessor list, no named data-centre provider behind the Oslo cloud, and no published certification document. Claims I like, on a paper trail I cannot yet audit. 1 2 7
The Shop Operator
The captured pages state incorporation in Norway, hosting in an Oslo private cloud plus EU and UK Azure regions specified in contract, no US data touchpoints, EU-based support and AI processing in Europe. I found no published subprocessor list and no stated legal basis for the UK regions, and no option to run the archive on the buyer's own infrastructure. 2 1
The Integrator
The trust page states incorporation in Norway, hosting specified in the contract across an Oslo private cloud and EU and UK Azure regions, no US data touchpoints, EU-based support and AI processing kept in Europe — a genuinely European posture for a buyer like me. But I found no published subprocessor list and no named provider for the Oslo private cloud, and the independently sourced checks on contracting entity, residency and subprocessor exposure came back unconfirmed, so the posture rests on the vendor's own account. 1 2 6
The Skeptic
The vendor's own trust page states incorporation in Norway, hosting in an Oslo private cloud plus EU and UK Azure regions specified in contract, EU-based support, AI processing in Europe and no US data touchpoints — strong words. The independently sourced attributes mark residency, jurisdiction and subprocessor exposure as not confirmed, and we found no published subprocessor list or named data-centre provider for the Oslo cloud, so the picture is asserted rather than evidenced end to end. 2 1 7
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
I found no public information on per-agent prices, tier boundaries, billing periods, minimum terms or add-on costs, and with Case Management and the Public FAQ presented as separate add-ons on a modular platform, nothing in the captured pages lets me compute an annual invoice for twelve agents. 3 5 1
The Agent Advocate
Not one captured page carries a number: the platform is sold as modules with ticketing inside Case Management as an add-on, and I found no public information on per-agent prices, tier boundaries, billing period, minimum terms or VAT treatment. Computing an annual invoice for a given agent count from public pages alone is impossible — that is a sales conversation. 1 3
The Data Protection Officer
No price appears anywhere in the captured pages: no per-agent figure, no tiers with numbers, not even for the Case Management add-on that contains ticketing. A support lead cannot compute a single line of the annual invoice from public information. Everything quoted is outcome percentages — ROI and response times — not money. 1 3
The Shop Operator
I found no public information on prices anywhere — no tier, per-agent figure or billing period — and both Case Management, which contains the ticketing, and the Public FAQ are described as add-ons without numbers. A support lead cannot compute any part of an annual invoice from these pages. 3 5
The Integrator
The captured pages show no pricing figures — no per-agent price, tier names, billing period or VAT treatment — even though Case Management ticketing and the Public FAQ are both described as add-ons that a buyer would need to price. I found no public information on what any module costs, so a support lead cannot compute an annual invoice for their agent count from public pages. 3 5
The Skeptic
No captured page shows a per-agent price, a tier, a billing period, a minimum term or VAT treatment — we found no public information on pricing at all. And the components a helpdesk actually needs are nested: ticketing is an add-on to the platform and the Public FAQ is an AI-powered add-on on top of Knowledge Management, and we found no public price for any of them. 3 5 1
European sovereignty — proven facts
0 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 ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Puzzel
Is Puzzel European?
Not determined: the vendor’s pages as captured do not say where Puzzel is based.
Where does Puzzel store data?
Not stated on the vendor’s pages as of 27 Oct 2026.
Does Puzzel have a free plan?
Not stated on the vendor’s pages as of 27 Oct 2026.
What are the best alternatives to Puzzel?
As of 27 Oct 2026, the panel rates Zendesk (3.5/5), HubSpot Service Hub (3/5) and Crisp (3/5) highest among the other 32 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). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Puzzel alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 27 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 — Legal entity, Data residency, 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.
- We could not confirm any pricing information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 36 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
- 7 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 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
- 1 integrations 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 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.puzzel.com Checked 27 Oct 2026 Details →
- 2 Security / trust page — found from the homepage www.puzzel.com Checked 27 Oct 2026 Details →
- 3 Ticketing, queues & SLA — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
- 4 Channels in one queue — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
- 5 Knowledge base & deflection — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
- 6 Knowledge base & deflection — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
- 7 Customer data protection — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
- 8 Integrations & API — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →