whats-best.ai
Search Sign in

Customer Service & Helpdesk

Puzzel

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

Puzzel: AI-assisted analysis on whats-best.ai Puzzel: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

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

Puzzel alternatives, European ones first →

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

The Data Protection Officer

Weighted verdict

Sees a ticket archive for what it is: years of personal data customers typed themselves, including the things they should not have. Wants retention that executes, redaction, an audit of who read what, and an answer on whether vendor support can open a ticket.

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

Scored by The Data Protection Officer

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

Ticketing, queues & SLA

How this is scored

The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.

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

Report an error

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

Report an error

Channels in one queue

How this is scored

Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.

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

Report an error

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

Report an error

Knowledge base & deflection

How this is scored

Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.

0 — No knowledge base; 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.

Report an error

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

Report an error

Customer data protection

How this is scored

A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights, 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.

Report an error

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

Report an error

Integrations & API

How this is scored

The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.

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

Report an error

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

Report an error

European sovereignty

How this is scored

Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it.

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.

Report an error

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

Report an error

Pricing transparency not rated — the vendor publishes no price

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.

Report an error

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

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

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

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.

Do you know more about Puzzel? Tell us Report an error on this page

Sources (8)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.puzzel.com Checked 27 Oct 2026 Details →
  2. 2 Security / trust page — found from the homepage www.puzzel.com Checked 27 Oct 2026 Details →
  3. 3 Ticketing, queues & SLA — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
  4. 4 Channels in one queue — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
  5. 5 Knowledge base & deflection — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
  6. 6 Knowledge base & deflection — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
  7. 7 Customer data protection — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →
  8. 8 Integrations & API — found from sitemap www.puzzel.com Checked 27 Oct 2026 Details →