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 Trengo B.V. · www.trengo.com

Report an error on this page Is this your product? →

Link to this page

Trengo: AI-assisted analysis on whats-best.ai Trengo: 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.

Trengo at a glance

Vendor
Trengo B.V.
Headquarters
Not stated on the vendor’s pages as of 1 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 1 Oct 2026
Free plan
Not stated on the vendor’s pages as of 1 Oct 2026
Panel verdict
The AI panel rates Trengo 2/5, the mean of 6 judges. Trengo, a customer-service and helpdesk platform, is judged strongest on omnichannel: apart from the data protection officer persona, which recorded 0 on every criterion, judges placed it at 6-7 for one shared inbox taking WhatsApp, email, social, live chat and voice, with SIP telephony documented in depth — calls made and received, logged under a linked user, feeding ticket creation — alongside customer-360 profiles and Meta and WhatsApp Business partner status. how scores are made
As of
Vendor pages captured 22 Sep 2026 to 1 Oct 2026; evaluated by the panel 28 Oct 2026. all sources

Trengo alternatives, European ones first →

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

The panel's verdict

Trengo, a customer-service and helpdesk platform, is judged strongest on omnichannel: apart from the data protection officer persona, which recorded 0 on every criterion, judges placed it at 6-7 for one shared inbox taking WhatsApp, email, social, live chat and voice, with SIP telephony documented in depth — calls made and received, logged under a linked user, feeding ticket creation — alongside customer-360 profiles and Meta and WhatsApp Business partner status. Ticketing scores cluster at 6 on Open, Assigned and Closed statuses, combinable filters and a business-hours first-response metric. Knowledge and self-service sits at 4: content is evidenced as fuel for the AI Agent rather than a managed help centre, with no public information on branding, article workflow or deflection reporting. The bench genuinely splits on data protection and sovereignty: some judges credit security-page commitments such as encrypted backups and PCI-DSS payment handling; others weigh the absence of a published data processing agreement, retention rules, stated server region and subprocessor list. The vendor publishes no prices — entry points are a free trial and a sales-team demo.

Report an error

Speaks for it

  • WhatsApp, email, social, live chat and voice land in one shared inbox, with customer-360 profiles beside the conversation.
  • SIP calls are made, received and logged under a linked user, feeding ticket creation and assignment, with desk-phone support.
  • Tickets carry Open, Assigned and Closed statuses with combinable filters by team, channel, label and date, CSV export and a business-hours first-response metric.
  • Shopify, WooCommerce and Lightspeed are named, the API is documented with multiple tokens and webhooks that fire on new messages, and integrations are built and maintained by the vendor's own team.
  • The security page commits to fully encrypted backups, data minimisation, never selling data, and no stored payment data as payments run through the PCI-DSS-compliant processor Mollie.

Report an error

Held against it

  • No public information on a data processing agreement, ticket retention or deletion rules, an audit log of agent access, or ticket redaction.
  • European ownership is stated, while hosting sits on AWS with no server region stated and no public information on a subprocessor list or the contracting entity's jurisdiction.
  • No public information on SLA policies with breach warnings and escalation, macros, or merge and split.
  • Knowledge serves the AI Agent, with no public information on a brandable public help centre, article draft-and-publish workflow, multilingual content or deflection reporting.
  • No public information on a customer portal where requesters see their own tickets, or on consent handling for the messenger channels.

Report an error

Best for

  • You run e-commerce support across WhatsApp, email, social and phone and want one shared queue with customer profiles beside every conversation.
  • Your team needs telephony inside the helpdesk, with SIP calls logged and turned into tickets.
  • You connect Shopify, WooCommerce or Lightspeed and rely on a documented API with multiple tokens and webhooks.
  • You want first-line deflection built from your own content — snippets, websites and documents — through the AI Agent.

Report an error

Avoid if

  • Your procurement must see a data processing agreement, retention and deletion rules and access audit logging before signing — the bench scored data protection at 2-3.
  • You must be able to state where the ticket archive lives, including server region and subprocessor locations, for a European review.
  • You need SLA breach warnings and escalation, macros, and per-agent resolution reporting to manage the queue day to day.
  • You need published per-agent prices to compute a budget before entering a sales conversation.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Ticketing, queues & SLA 3 of 5
Channels in one queue 3.5 of 5
Knowledge base & deflection 2 of 5
Customer data protection 1.5 of 5
Integrations & API 3 of 5
European sovereignty 1.5 of 5

Ticketing, queues & SLA

panel disagrees Show 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.

Report an error

The Support Lead

Tickets carry statuses of Open, Assigned and Closed, filter by team, channel, label and date with combinable filters, and there is a first-response-time metric that counts business hours only — a number I could take to a quarterly review. Routing to teams is configurable through pre-chat department choices and custom answers mapping each choice to a team. We found no public information on SLA policies with breach warnings or escalation. 3 4 5

Report an error

The Agent Advocate

Tickets carry Open, Assigned and Closed statuses with combinable filters by team, channel, label and date, a business-hours first-response metric, and CSV export — a queue I can work from one screen, with routing to teams via custom answers and a pre-chat department selector. But I found no public information on SLA policies with breach warnings or escalation, macros, or merge and split, which is the machinery the hard days need. 3 4 5

Report an error

The Data Protection Officer

Tickets carry a status of Open, Assigned or Closed, team assignment and labels, worked through combinable filters and a Ticket Details page that lets agents explore and export them. Routing to teams is documented via a pre-chat department selector and custom answers, alongside auto-close automations and a first-response-time metric that counts only business hours. I found no public information on SLA policies with breach warnings and escalation, macros, or per-agent resolution reporting, so this stays at the solid middle band. 3 4 5

Report an error

The Shop Operator

Tickets carry a status of open, assigned or closed and route to teams through the live-chat department selector and custom answers, and the ticket details page lets me slice the pile by team, channel, label and date with combinable filters and a CSV export. First response time is measured with business hours, which is exactly the number I defend in January. I found no public information on SLA targets with breach warnings or escalation, macros, or per-agent resolution reporting. 3 4 5

Report an error

The Integrator

Tickets carry statuses (Open, Assigned, Closed) and team assignment, routing rules send pre-chat choices to teams, and filters by team, channel, label and date combine into search, with a first-response metric computed on business hours. We found no public information on SLA policies with breach warnings or escalation, merge and split, or resolution reporting by agent and queue, which is what keeps this below the top band. 3 4 5

Report an error

The Skeptic

Tickets carry a real status (Open, Assigned, Closed), team routing via a pre-chat Department Selector and custom answers that map each choice to a team, and combinable filters by team, channel, label and date; first response time is measured against business hours, so routing and measurement are genuinely documented. We found no public information on SLA policies with breach warnings or escalation, merge and split, or skills- or load-based assignment, so the queue is evidenced as routable and tracked, not managed. 3 4 5

Report an error

Channels in one queue

panel disagrees Show 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.

Report an error

The Support Lead

WhatsApp Business, Facebook, Instagram, Telegram, email, live chat and voice all land in one shared inbox, calls are logged in Trengo against a linked user, and a customer-360 profile sits beside the conversation across channels; Trengo presents itself as a Meta and WhatsApp Business partner. We found no public information on a customer portal where a requester sees their own tickets, or on consent handling for the messengers. 1 5 6

Report an error

The Agent Advocate

Email, WhatsApp, Facebook, Instagram, Telegram and live chat land in one shared inbox, and voice is genuinely wired in: calls made and received, logged in Trengo, and tied to ticket creation and assignment, with customer profiles beside the conversation across channels. I found no public information on a customer portal where a requester sees their own tickets, or on consent handling for the messengers, so it stops short of the top. 1 5 6

Report an error

The Data Protection Officer

WhatsApp, Facebook, Instagram, Telegram, email and live chat all land in one shared inbox, with a customer 360 view keeping earlier conversations visible to the agent across channels. Telephony is real and documented: calls are made and received over SIP, logged in the product under a linked user, with voicemail and welcome-message handling inside the product. I found no public information on a customer portal where requesters see their own tickets, or on consent handling for the messenger channels, which is what holds this below the top band. 1 5 6

Report an error

The Shop Operator

WhatsApp Business, email, social media, voice calls and live chat land in one shared inbox, with customer profiles kept in a 360 view next to conversations across channels — that is my one-queue test passed. Voice is documented in real depth: SIP calls made and received, logged under a linked user, feeding ticket creation and assignment, with desk-phone support on top. I found no public information on a customer portal where a requester sees their own tickets, or on consent handling for the messengers, so it sits just under the full mark. 1 5 6

Report an error

The Integrator

WhatsApp, email, social, voice and live chat land in one shared inbox with a customer-360 profile beside the conversation, and SIP telephony is logged and tied to a user for ticket creation, with credentials restricted to admins. Meta and WhatsApp Business Partner status covers the messaging side; we found no public information on a customer portal where requesters see their own tickets, which is the gap against the top band. 1 5 6

Report an error

The Skeptic

Email, live chat, WhatsApp, Facebook, Instagram, Telegram and voice are all claimed into one shared inbox, customer profiles travel across channels, the ticket filters actually filter by channel, and SIP calls are logged and create tickets under a linked user — more than logo-counting. Two items keep it out of the top bands: we found no public information on WhatsApp consent handling, and no public information on a customer portal where a requester can see their own tickets. 1 5 6

Report an error

Knowledge base & deflection

panel disagrees Show 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.

Report an error

The Support Lead

The AI Agent draws on snippets, websites, documents in PDF, TXT or CSV, and a Help Center that can be connected as a knowledge source, with the vendor claiming a share of repetitive conversations resolved. We found no public information on a searchable public help centre with its own branding and article workflow, multilingual content, or reporting on which articles deflect. 1 5 7

Report an error

The Agent Advocate

The knowledge base feeds the AI Agent — snippets, documents in PDF, TXT and CSV, websites and a connectable Help Center — and the marketing page claims a share of repetitive conversations resolved instantly. I found no public information on article draft and publish workflow, versioning or review dates, multilingual articles, or reporting on which content actually deflects, so it reads as an answering machine more than a managed knowledge asset. 1 5 7

Report an error

The Data Protection Officer

An AI Agent knowledge base is documented with snippets, connected websites, uploaded documents and a connectable Help Center, and the vendor claims a share of repetitive conversations resolved instantly by the agent — that is genuine deflection intent. But this evidence is about machine answering, not a managed knowledge asset. I found no public information on a brandable public help centre with draft and publish states, article suggestions to agents while they answer, or reporting on which content actually deflects. 1 5 7

Report an error

The Shop Operator

The AI Agent answers from a genuine knowledge base of snippets, websites and documents, the vendor's own help centre can be connected as a source, and the homepage claims a share of repetitive conversations — refunds, returns, order queries — resolved instantly, which is the deflection I judge by. I found no public information on article workflow: a public help centre with its own branding and draft and publish states, suggestions to agents while they answer, multilingual articles, or deflection reporting a team could act on. 1 5 7

Report an error

The Integrator

Knowledge exists mainly as fuel for the AI Agent: snippets, connected websites, PDF/TXT/CSV documents and the Help Center as sources, with a marketing counter claiming a share of repetitive conversations resolved. We found no public information on article workflow, versioning, multilingual content, agent-side suggestions, or deflection reporting a team could act on. 1 7 5

Report an error

The Skeptic

The AI Agent answers from a real knowledge base — snippets, connected websites, PDF/TXT/CSV documents, and the Help Center connectable as a source — and the homepage sells deflection as a counter of "repetitive conversations resolved". We found no public information on the help centre's own branding, draft and publish states, multilingual or versioned articles, or reporting on which articles deflect, so knowledge feeds the AI but is not evidenced as a managed asset. 1 5 7

Report an error

Customer data protection

panel disagrees Show 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.

Report an error

The Support Lead

There is a GDPR/AVG policy in the terms, fully encrypted backups, payment data kept away from Trengo and handled by a PCI-DSS-compliant processor, a stated commitment never to sell data, and SIP credentials restricted to admins. We found no public information on retention or deletion rules for tickets, an audit log of agent access, or redaction. 2 6 8

Report an error

The Agent Advocate

There is a GDPR policy in the Terms and Conditions, encrypted backups, statements of data minimisation and no resale of data, no stored payment data via a PCI-DSS processor, and voice SIP credentials gated to admins. I found no public information on a data processing agreement, documented ticket or requester deletion, retention rules, an audit log of agent access, or redaction — the paperwork a DSGVO review asks for is not on these pages. 2 6 8

Report an error

The Data Protection Officer

A security page commits to encrypted backups, no stored payment data, data minimisation and no selling of data, and points to a GDPR policy inside the terms and conditions — statements, not executed controls. For a ticket archive the execution is what I judge, and I found no public information on a data processing agreement, retention or deletion rules that run, an audit log of who read a ticket, redaction of ticket content, or whether the vendor's own support can open a customer ticket. The one access control I can verify is narrow: only administrators can generate telephony credentials. 2 6 8

Report an error

The Shop Operator

The security page commits to data minimisation, fully encrypted backups, never selling data and no stored payment details (payments run through Mollie under PCI-DSS), and the current GDPR/AVG policy sits in the terms and conditions; only admins can generate SIP credentials, which is at least one role limit in practice. I found no public information on a signable data processing agreement, retention or deletion rules for tickets, an audit log of agent access, or documented support for access and erasure requests. For an archive full of my customers' order data, that is the paperwork I would demand before signing. 2 6 8

Report an error

The Integrator

The security page commits to data minimisation, fully encrypted backups, never selling data and third-party sharing only to run the product, payments run through a PCI-DSS processor, and the GDPR/AVG policy sits in the terms, with admin-only access to SIP credentials as one role limit. We found no public information on a published data processing agreement, ticket or requester deletion, retention rules, redaction, or an audit log. 2 6 8

Report an error

The Skeptic

A GDPR page points into the Terms & Conditions, backups are fully encrypted, card data never touches Trengo (Mollie, PCI-DSS), the vendor pledges never to sell data, and only admins can generate SIP credentials — one real role boundary, plus CSV export of tickets. We found no public information on a data processing agreement, retention or deletion rules, ticket redaction, or an audit log of agent access, which is what a ticket archive of personal data needs to show. 2 4 6 8

Report an error

Integrations & API

panel disagrees Show 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.

Report an error

The Support Lead

Shopify, WooCommerce and Lightspeed are named, the API has its own documentation with multiple tokens and webhooks that push new messages out, and integrations are built and maintained by Trengo's own team with partner-built ones alongside. Adding integrations to your pricing plan goes through a contact conversation and some are labelled "Coming soon"; we found no public information on single sign-on, user provisioning or documented rate limits. 1 5 9 10

Report an error

The Agent Advocate

Shopify, WooCommerce and Lightspeed are named, the API has documentation with multiple tokens and webhooks that fire on new messages, and integrations are built and maintained by the vendor's own team alongside partner-built ones — maintenance, not just a logo wall. I found no public information on SSO or SCIM provisioning, documented rate limits or a sandbox, and adding integrations to a pricing plan goes through a contact conversation. 1 9 10

Report an error

The Data Protection Officer

Named shop integrations such as Shopify, WooCommerce and Lightspeed are documented, alongside public API documentation, multiple API tokens and webhooks. Integrations are built and cared for by the vendor's own team, with partner-built custom work offered, which is more than a bare connector list. I found no public information on SSO and SCIM provisioning, documented rate limits or a sandbox, and adding integrations to a plan is handled by contacting the vendor. 1 9 10

Report an error

The Shop Operator

Shopify, WooCommerce and Lightspeed are named, the API is documented with multiple tokens, and webhooks fire when new messages arrive — the order context I need is at least within reach. Trengo builds and maintains its own integrations rather than merely listing them, which I respect. I found no public information on a maintained marketplace with bidirectional sync, SSO or SCIM provisioning, rate limits or a sandbox, and adding an integration to your plan is handled by contacting them. 1 5 9 10

Report an error

The Integrator

The API is documented with multiple tokens and webhooks that fire when new messages appear, and Shopify, WooCommerce and Lightspeed are named and — for the vendor's own set — built and maintained by the in-house team, which is more than a logo wall. But I found no public information on rate limits, webhook retries, SCIM provisioning or a sandbox, and adding integrations to a pricing plan is routed through a contact form, which is the kind of gate that makes the integration story partly a sales conversation. 1 9 10

Report an error

The Skeptic

API documentation, multiple API tokens and webhooks that fire on new messages are documented; Shopify, WooCommerce and Lightspeed are named; and Trengo says its own integrations are built and cared for by its own team — vendor-maintained, not just listed. Adding integrations to a pricing plan is a "contact us" conversation, and we found no public information on an app marketplace, bidirectional sync, SSO/SCIM provisioning, or documented rate limits and a sandbox. 1 5 9 10

Report an error

European sovereignty panel opinion

panel disagrees Show 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.

Report an error

The Support Lead

The vendor states it is European-owned on its footer, security page and integrations page, and hosts on Amazon Web Services, while the captured pages leave the server region and the contracting entity's jurisdiction unstated and flag exposure to the US Cloud Act through the hosting provider. We found no public information on a published subprocessor list or a data processing agreement, so this is one European element proven with the rest of the chain open. 2 5 9

Report an error

The Agent Advocate

European-owned is stated in the footer and repeated on the product pages, which is one proven European element. Hosting sits on Amazon Web Services with no server region stated, and I found no published subprocessor list with locations or a stated data-residency option, so the rest of the chain is dark. 2 5 9

Report an error

The Data Protection Officer

The vendor states it is European-owned in its own footer, and that is the single European element the evidence proves. Hosting sits on Amazon Web Services — a US-headquartered provider — with no server region stated, payments run through Mollie whose location is not stated, and the contracting entity's jurisdiction and subprocessor locations are unknown. I found no public information on EU data residency as standard or a published data processing agreement, so for a European archive the chain cannot be relied on. 2 5

Report an error

The Shop Operator

The vendor calls itself European-owned in its footer and publishes a GDPR policy — one European element proven. Hosting runs on Amazon Web Services, a US-headquartered provider regardless of where servers sit, the payment processor's location is not given, and I found no public information on an EU hosting option, a subprocessor list with locations, or the contracting entity's jurisdiction. Knowing where my customers' order history sits matters to me, and most of that chain is simply not stated. 2 5 8

Report an error

The Integrator

The vendor states it is European-owned and points to a GDPR/AVG paragraph in its terms, but the application is hosted on AWS, a US-headquartered provider, and the captured pages state no server region, subprocessor locations, EU contracting entity or published data processing agreement. For a buyer who has to answer where the ticket archive lives, one ownership claim and this much of the chain unestablished is barely a start. 2 8

Report an error

The Skeptic

The vendor's own footer states European-owned, and that is the one European element the captured pages prove. Everything downstream is unstated: the application runs on AWS, a US-headquartered provider, with no server region given, no contracting-entity jurisdiction, no subprocessor list, and payments routed through Mollie, whose location the security page omits — leaving the US Cloud Act question open. 2 5

Report an error

Pricing transparency not rated — the vendor publishes no price

Show 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.

Report an error

The Support Lead not rated — no public information

We found no public information on prices: no tier costs, per-agent figures, billing periods or VAT treatment appear in the captured pages. The only pricing-related statements are a free trial and guidance to contact the team about adding integrations to your pricing plan. 1 10

Report an error

The Agent Advocate

I found no public prices on any page I read — no tiers, no per-agent rate, no billing period, no VAT treatment. The way in is a free trial and a customised demo from the sales team, and even adding integrations to your plan is handled by contacting them. 1 10

Report an error

The Data Protection Officer

The captured pages show a free trial and a demo arranged through the sales team, and integrations are added to a pricing plan by contacting the vendor. The only priced item visible is a paid push add-on inside the Zoiper calling app, bought from that app's vendor on one-month or one-year terms — not a price for the product itself. I found no public information on plan prices, per-agent rates or billing terms, so a support lead cannot compute an annual invoice from what is public. 1 6 10

Report an error

The Shop Operator

I found no price figures on any page I read — the entry points are a free trial and a customised demo with the sales team, and adding integrations to a pricing plan is explicitly a contact-us matter. The only concrete cost anywhere was a third-party softphone's paid push add-on bought in that app's own store, which does nothing for my budget. I cannot compute the annual invoice for my agent count from these pages. 1 6 10

Report an error

The Integrator not rated — no public information

We found no public information on pricing on the pages we read: the homepage offers a free trial and a customised demo through contact, the telephony article documents a third-party calling app's paid push add-on, and integration plan questions are routed to contact, with no tier price, billing period or per-agent maths on any captured page. 1 6 10

Report an error

The Skeptic

The only commercial terms on the captured pages are a free trial, a "speak to our team" customised demo, and "contact us" for adding integrations to a pricing plan; we found no public information on per-agent prices, tier features, billing periods or channel costs. A support lead cannot compute an annual invoice from these pages — the buying motion on display is a sales conversation. 1 10

Report an error

European sovereignty — proven facts

0 of 6 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.

Hosting location Not determined — 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 — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Trengo

Is Trengo European?

Not determined: the vendor’s pages as captured do not say where Trengo is based.

Where does Trengo store data?

Not stated on the vendor’s pages as of 1 Oct 2026.

Does Trengo have a free plan?

Not stated on the vendor’s pages as of 1 Oct 2026.

What are the best alternatives to Trengo?

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: Trengo 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.

Sources (10)

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

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