Help desk or ticket system
Trengo
Trengo is listed here as a help desk or ticket system.
Trengo is a European-owned shared inbox in which a business's support and sales staff answer customers on WhatsApp Business, email, live chat, Instagram, Facebook Messenger, TikTok, SMS and voice calls. It is aimed especially at travel and leisure operators such as hotels and B&Bs, tour operators, theme parks, camps and holiday rentals, along with online shops, spas and health tourism businesses. In Trengo a conversation starts with a message sent from the inbox and covers seven days with that customer, after which further contact opens a new conversation.
What these workflow templates do
Every workflow template below works from an export from a help desk or ticket system and changes nothing in it.
Workflows for help desks and ticket systems
No workflow template names Trengo yet. The templates below are not written for Trengo by name; each is written for a help desk or ticket system.
Customer satisfaction detractor follow-up Workflow template
Works from an export from a help desk or ticket system.
Can see: tickets and their notes. Can change: nothing.
Evaluation unit trial review Workflow template
Works from an export from a help desk or ticket system.
Can see: support history rows with ticket id, date, summary and status. Can change: nothing.
Help article from a resolved issue Workflow template
Works from an export from a help desk or ticket system.
Can see: the resolved ticket thread with internal notes. Can change: nothing.
Help centre gap review Workflow template
Works from an export from a help desk or ticket system.
Can see: each ticket's topic, subject, article sent and resolution. Can change: nothing.
Policy answers from the handbook Workflow template
Works from an export from a help desk or ticket system.
Can see: staff questions typed or exported from the help desk. Can change: nothing.
Service inbox routing plan Workflow template
Teams doing this work typically use a help desk or ticket system.
Can see: queue names and owners. Can change: nothing.
Stale ticket sweep Workflow template
Works from an export from a help desk or ticket system.
Can see: open-ticket export. Can change: nothing.
Support escalation brief Workflow template
Works from an export from a help desk or ticket system.
Can see: ticket history export. Can change: nothing.
Support service level definition Workflow template
Works from an export from a help desk or ticket system.
Can see: ticket export with created, first reply and resolved times. Can change: nothing.
Support ticket triage Workflow template
Works from an export from a help desk or ticket system.
Can see: queue export of new or unassigned tickets. Can change: nothing.
Teams that run these workflow templates:
How it connects
Each connector below is one we know of, with who publishes it, where and when we found it, and its trust level.
Published by its maker
Programming interface from the maker of Trengo
A programming interface for software developers.
Published by Trengo, as the maker's own page states.
Found in the maker's own documentation on 12 November 2026. Last checked on 12 November 2026.
ListedFound in a named public source on a stated date. We have not reviewed or used it.
What setup takes, and who approves it
Connecting a workflow to Trengo is agreed when the work is scoped: a person who looks after Trengo at your company approves how the workflow signs in and what it may see and change.
No time is promised here. Where no connector exists, the workflow works from an export.
What was checked, and when
- The maker's own pages: read on 12 November 2026.
- The workflow templates above: each link was read from the template's own text and reviewed, most recently on 12 November 2026.
Next step
Want a workflow above built for your team? Open it and choose how to start, or book a fit call.
Technical details
- Trengo REST API · Public APIFound in the maker's own documentation
https://app.trengo.com/api/v2Trengo's developer docs describe a REST API that a person reaches with a personal access token, which it sends as a Bearer credential.The maker’s page