Customer Service & Helpdesk
Trengo
Provenance unknown Report an error0–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? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Trengo's product is an omnichannel inbox: WhatsApp Business, email, social media, voice calls and live chat land in one team-shared inbox, with WhatsApp and Meta Business Partner status stated, and AI Agents claimed to resolve up to 80% of queries before a human. Omnichannel scores highest, at 6-7. Ticketing core is weakest, clustering at 2: judges found no public information on routing rules, SLA timers, status models, macros or ticket search, reading as an inbox with automation rather than a managed workload. Knowledge and self-service sits at 2-3, resting on the AI resolution claim rather than a customer-facing knowledge base; the Help Centre named is the vendor's own. Customer data protection scores 1-2 and sovereignty 2-3: no sovereignty attributes are on record — a GDPR page and European ownership are stated, and judges found no public information on hosting location or subprocessors. Integrations sits at 3-4 on Shopify, WooCommerce and published API documentation. Scores on every criterion fall within one point — no split among judges. No public prices were found, only a free trial and a customised demo.
Speaks for it
- Omnichannel scored 6-7, with WhatsApp Business, email, social media, voice calls and live chat stated to land in one shared team inbox.
- WhatsApp Business Partner and Meta Business Partner status is stated on the vendor page.
- AI Agents are claimed to resolve up to 80% of queries before a human, active 24/7 and in every language.
- Shopify and WooCommerce are named integrations, API documentation is published, and custom integrations are offered as a vendor build service.
- Channels and AI Agents are claimed to connect and set up in minutes, with no developer needed.
Held against it
- Ticketing core scores cluster at 2, with no public information on routing rules, SLA timers, escalation chains or ticket search.
- Knowledge and self-service scores sit at 2-3, resting on the 80% AI claim rather than a customer-facing knowledge base.
- Customer data protection scores 1-2: a GDPR page and European ownership are the whole of the protection evidence captured.
- Sovereignty scores 2-3 with no sovereignty attributes on record, and no public information on hosting location, data-centre provider or a subprocessor list.
- No public prices, tiers or per-agent figures were found — the recorded offers are a free trial and a customised demo.
Best for
- You run a commerce support queue over messengers and want WhatsApp Business, email, social media, voice calls and live chat in one shared team inbox.
- You want AI Agents handling common asks — booking changes, refunds, returns and order queries — around the clock.
- You sell on Shopify or WooCommerce and want named connectors, an API and vendor-built custom integrations.
Avoid if
- Your team runs on routing rules, SLA timers with breach warnings, priorities, escalation chains and first-response reporting — ticketing core scored 2, judged as an inbox with automation rather than a managed workload.
- You must show a data protection authority an executing regime for a WhatsApp and voice archive — customer data protection scored 1-2, with a GDPR page and European ownership the only evidence captured.
- You are wiring this alongside an existing CRM and identity provider — integrations scored 3-4, with no CRM named and no public information on webhooks, SSO or SCIM provisioning.
- You need a customer-facing knowledge base with editorial workflow and deflection reporting — knowledge and self-service scored 2-3, resting on the AI resolution claim.
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
What my team runs on — routing rules, SLA timers with warnings before breach, priorities, escalation chains and reporting on first response by agent and queue — is exactly what I could not verify; we found no public information on any queue, status model, or search capability. The captured page sells one shared team inbox with automations and an AI agent, which reads as an inbox with automation rather than a managed workload, so I score just above the floor. 1
The Agent Advocate
The page promises one shared inbox with automations and AI, but we found no public information on assignment, status models, SLA timers, macros, or search across ticket history. I judge a tool by the hundredth reply, and nothing here shows how I'd find the old thread or catch a ticket about to breach. 1
The Data Protection Officer
The captured pages show one inbox shared by the team with smart automations and AI agents handling conversations, but this is a shared inbox rather than managed workload. We found no public information on ticket assignment, status models, SLA timers, escalation, or search across ticket bodies. 1
The Shop Operator
A team-shared omnichannel inbox with smart automations is the right starting point, but I found no public information on assignment and status models, SLA timers, escalation chains, macros, or ticket search. For a parcel-volume queue I cannot tell from these pages how work is routed, prioritised or measured. 1
The Integrator
A shared team inbox across channels is the one evidenced structure, with smart automations named but never detailed. We found no public information on queue routing, SLA timers, priorities, a status model, macros, escalation or ticket search, so the engine itself is unevidenced between a mailbox and a real ticketing system. 1
The Skeptic
The page sells a shared omnichannel inbox and automations, but everything I read for SLA work is absent from the capture: no routing rules, no SLA timers or business hours, no escalation chains, no macros or triggers, no reporting on first response or resolution, and nothing on search across ticket bodies. We found no public information on any status model or ownership beyond the one-inbox claim. 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
This is the vendor's clearest story: WhatsApp Business, email, social, voice calls and live chat are all stated to land in one inbox shared by the team, and WhatsApp Business Partner status backs the messenger side. We found no public information on a customer portal where requesters see their own tickets, on call logging, or on stated consent handling, so I stop short of the full multichannel picture even though five channel families are evidenced in one queue. 1
The Agent Advocate
WhatsApp, email, social, voice and live chat are all claimed in one shared inbox with no browser tabs, and the Meta Business Partner badge sits behind the WhatsApp piece. The depth is unproven, though: we found no public information on a customer portal, messenger consent handling, call logging, or one visible history per customer across channels. 1
The Data Protection Officer
WhatsApp Business, email, social media, voice calls and live chat are all stated to land in one shared inbox, and Meta WhatsApp Business partner status is named. We found no public information on consent handling for messengers, a customer portal where a requester sees their own tickets, or a single customer history visible from every channel. 1
The Shop Operator
WhatsApp Business, email, social media, live chat and voice calls are all stated to land in one shared inbox on one screen with no personal devices — exactly the single queue I judge on, and the WhatsApp and Meta Business Partner credential backs the messenger side. I found no public information on messenger consent handling, call logging, or a customer portal where a requester sees their own tickets, which keeps this short of the top band. 1
The Integrator
WhatsApp, email, social media, voice and live chat are all claimed into one shared inbox with one history, which is the substance this criterion wants and goes beyond the mid anchor by putting voice directly in the queue. We found no public information on a customer portal where requesters see their own tickets, and while WhatsApp Business Partner status is stated, consent handling for messengers is not. That keeps it below the stronger anchors despite the broad channel list. 1
The Skeptic
Five channels — WhatsApp Business, email, social, voice and live chat — are claimed to land in one shared inbox, and the Meta Business Partner status is stated, so this is more than a logo wall. But we found no public information on a per-customer unified history across channels, a requester portal, call logging, or WhatsApp consent handling. 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
The only knowledge evidence is the vendor's own Help Centre and Academy, plus an up-to-80-percent AI resolution claim — that is automation deflection, not a managed article base for my customers. We found no public information on article workflow, versioning, article suggestions to agents or customers, review dates, or reporting on which content deflects tickets. 1
The Agent Advocate
The eighty-percent AI resolution claim is deflection of a sort, but a bot answering is not knowledge my team can reuse: we found no public information on a customer-facing help centre, article workflow, versioning, review dates, or deflection reporting. The Help Centre named on the page is the vendor's own, not a product feature. 1
The Data Protection Officer
A Help Centre exists and the pages claim AI agents resolve up to 80 percent of queries before a human steps in, which is deflection, but the claim is marketing rather than reporting the team acts on. We found no public information on a customer-facing knowledge base with editorial workflow, article suggestions, review dates, or deflection measurement. 1
The Shop Operator
Deflection is front and centre — up to 80% of queries resolved before a human, around the clock in every language, with the AI Agent handling refunds, returns and order queries. But I found no public information on a help centre shipped to end-customers, article workflow, versioning, or deflection reported as a number the team can act on, so this rests on AI claims rather than a managed knowledge asset. 1
The Integrator
AI answering is heavily marketed — an AI Agent claimed to resolve up to eighty percent of queries before a human — but that is automated replies, not a knowledge asset. We found no public information on a public help centre product for end customers, article workflow, versioning, article suggestions to agents or customers, or deflection reporting; the Help Centre named is the vendor's own support site. 1
The Skeptic
What the capture shows is the vendor's own Help Centre, Status page and Academy for its users, not a knowledge base a buyer builds for their customers; the 80% resolution figure is an AI-agent claim, not article-based deflection. We found no public information on editorial workflow, versioning, article suggestions to agents or customers, or deflection reporting. 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
A GDPR page and European ownership are stated, which is more than nothing for a ticket archive full of personal data. We found no public information on a signable DPA, a stated retention period, agent roles or queue-level visibility, a deletion path that actually executes, or an audit log of who opened which ticket — nothing here is evidenced as executing. 1
The Agent Advocate
A GDPR information page is the entire protection story on offer; we found no public information on retention periods, deletion paths, agent roles or queue-level visibility, a signable DPA, or an audit log of who opened which ticket. A ticket archive is the customer's own personal data, and nothing here shows what actually executes. 1
The Data Protection Officer
A GDPR page exists and the vendor describes itself as European-owned, but that is the whole of the protection record. We found no public information on retention periods, executable deletion of a requester's data, agent roles and queue-level visibility, an audit log of who opened which ticket, redaction, attachment handling, or a published signable data processing agreement — and an archive of WhatsApp and voice conversations without a stated retention regime is what an authority asks about first. 1
The Shop Operator
A GDPR page is captured and the vendor is European-owned, but I found no public information on a signable DPA, stated retention periods, agent roles and queue-level visibility, or a deletion path for a requester's data. For a ticket archive full of order and address details, nothing here shows protections that execute. 1
The Integrator
A GDPR information page and European ownership are the only protection signals captured. We found no public information on a signable data processing agreement, stated retention periods, deletion paths that can be executed, agent role and queue-level visibility controls, audit logging, or attachment handling. 1
The Skeptic
A GDPR page exists and the company is European-owned, and that is the whole of the protection evidence. We found no public information on retention periods, an executable deletion path for a requester, agent roles or queue-level visibility, a published signable DPA, or an audit of who opened which ticket. 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
Shopify and WooCommerce are named as native integrations, API documentation is available, and the vendor offers to build custom ones — a credible story for a commerce shop. We found no public information on webhooks, documented rate limits, SSO, SCIM provisioning, or CRM integrations, which my stack would need on day one, so this sits between a bare integration list and a documented-API offering. 1
The Agent Advocate
Shopify and WooCommerce are named, API documentation is public, and the vendor will build customs — enough to hope for order context inside a ticket. But we found no public information on CRM integrations, webhooks, rate limits, SSO or SCIM, so a buyer wiring this into their stack is planning blind. 1
The Data Protection Officer
Shopify and WooCommerce are named integrations, API documentation is stated to exist, and custom integrations are offered as a build service by the vendor. We found no public information on webhooks, documented rate limits, SSO, SCIM provisioning, or connectors for CRM systems. 1
The Shop Operator
Shopify and WooCommerce are named integrations with an offer to build custom ones, and API documentation is published, so the shop connection I need is at least named. I found no public information on webhooks, documented rate limits, SSO, or whether order context from the shop appears inside the ticket, which is the whole point when agents answer where-is-my-parcel all day. 1
The Integrator
Shopify and WooCommerce are named, an API documentation link exists, and custom integrations are offered as "we can build it" — a partner conversation where I want a documented path with rate limits, webhooks that retry, SCIM provisioning and a sandbox, none of which appear. We found no public information on webhooks, documented rate limits, SSO, a sandbox, or any named CRM or identity integration, and for wiring this alongside a CRM and an identity provider that predate it, that gap decides the score. 1
The Skeptic
Shopify and WooCommerce are named as native connections, an API is documented, and custom integrations are offered as a service the vendor builds for you. No CRM is named, and we found no public information on webhooks, rate limits, SSO, SCIM provisioning, or a sandbox. 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
European ownership is stated and a GDPR page exists, but the sovereignty record itself is empty. We found no public information on where the ticket archive is hosted, the named data-centre provider, a published subprocessor list, any non-EU processing with its legal basis, or whether vendor support can read customer data — with the subprocessor picture unpublished I cannot go past entry-level confidence. 1
The Agent Advocate
European ownership and a Dutch contracting entity are stated, which is a real start. But we found no public information on hosting location, a named data-centre provider, or any subprocessor list — a gap that matters when WhatsApp routing puts Meta in the chain by definition. 1
The Data Protection Officer
The contracting entity is Trengo B.V., a Dutch company described as European-owned, with a GDPR page available. However, no sovereignty attributes are on record, and we found no public information on hosting location, a published subprocessor list, or which providers process the AI features that touch customer conversations. 1
The Shop Operator
The vendor is European-owned with an EU-form company name and a GDPR page, but there are no sovereignty attributes on record: I found no public information on hosting location, data-centre provider, subprocessors, or whether vendor support can read customer data. That is enough to trust the contracting side and nothing about where the ticket archive actually sits. 1
The Integrator
The contracting entity is European — Trengo B.V., described as European-owned — and a GDPR page exists, which is a real start. We found no public information on where the ticket archive is hosted, the data-centre provider, a subprocessor list, or whether vendor support can read customer data, so the chain beyond the entity is unevidenced. 1
The Skeptic
European ownership is stated and a GDPR page exists, but the sovereignty record is otherwise empty: no hosting location, no contracting entity, no named data-centre provider, and no subprocessor list. We found no public information on where the ticket archive is stored or whether vendor support can read customer instances. 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
The captured page shows a free trial and a funnel to speak to the team for a customised demo, and we found no public prices anywhere in it — no per-agent figure, no tiers, no billing period. I cannot even begin to compute the annual invoice for my twelve agents, so this scores at the bottom. 1
The Agent Advocate
A free trial and a customised sales demo are what's public; we found no public information on per-agent prices, tiers, billing periods, or what voice and WhatsApp usage cost. A support lead cannot get within shouting distance of the annual invoice from these pages. 1
The Data Protection Officer
The only public commercial offers are a free trial and an invitation to speak to the team for a customised demo. We found no public information on per-agent prices, tier boundaries, billing periods, minimum terms, or add-on pricing, so a real annual invoice cannot be computed from public pages. 1
The Shop Operator
The captured page offers a free trial and a customised demo through the sales team, and I found no public price for any tier or channel. As a support lead I cannot begin to compute the annual invoice for my agent count from these pages. 1
The Integrator
We found no public prices at all: the captured page offers a free trial and steers buyers to "get a customised demo" with the sales team. With no per-agent price, no tiers, no billing period and no add-on pricing on the record, an annual invoice cannot be computed from public pages. 1
The Skeptic
The captured page offers a free trial and steers buyers to a customised demo with the sales team; we found no public prices, no tiers, no per-agent maths, no billing period or minimum term, and no public information on channel add-ons or metered usage. An annual invoice for a given agent count is not computable from what was captured. 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 | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited 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 22 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 — 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 found no public information on pricing on the pages we read (trengo.com, trengo.com/security, help.trengo.com/article/routing-customers-to-the-correct-teams, help.trengo.com/article/ticket-details-deep-dive-into-your-tickets, trengo.com/products/omnichannel-inbox, help.trengo.com/article/have-phone-calls-through-sip-via-trengo-voice and 4 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 5 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
- 4 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 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 (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.trengo.com Checked 22 Sep 2026 Details →
- 2 Security / trust page — found from the homepage trengo.com Checked 30 Sep 2026 Details →
- 3 Ticketing, queues & SLA — found from sitemap help.trengo.com Checked 1 Oct 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap help.trengo.com Checked 1 Oct 2026 Details →
- 5 Channels in one queue — found from sitemap trengo.com Checked 1 Oct 2026 Details →
- 6 Channels in one queue — found from sitemap help.trengo.com Checked 1 Oct 2026 Details →
- 7 Knowledge base & deflection — found from sitemap help.trengo.com Checked 1 Oct 2026 Details →
- 8 Customer data protection — found from sitemap trengo.com Checked 1 Oct 2026 Details →
- 9 Integrations & API — found from sitemap trengo.com Checked 1 Oct 2026 Details →
- 10 Integrations & API — found from sitemap trengo.com Checked 1 Oct 2026 Details →