Catching up on a ticket
Maya Okafor, support lead at Acme Ltd, asked what the latest was on ticket 2501567. Memtro read the ticket's messages and said the customer had chased twice since Tuesday, and an agent's internal note promised a replacement.
What's the latest on this customer's ticket, and what have we said so far?
Trengo connects Memtro to your shared inbox. It reads tickets by status, contact and update time, with subject, channel, assigned agent and a preview of the last message, and a ticket's messages in order, including internal notes. It finds contacts and lists your agents. When asked, and once an administrator has granted the action by name, it can add internal notes, reply to the customer on the ticket's channel, which cannot be recalled, send WhatsApp templates that Meta may charge for, open, assign and close tickets, and create, change or permanently delete contacts. It never returns a contact's phone number.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Trengo tool, reads what it needs, and answers with the source cited.
These tools change something in Trengo. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Trengo is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What's the latest on ticket 2501567?
Which open tickets were updated since Monday?
Show me every ticket from ada@acme.com.
Add an internal note to ticket 2501567 saying the refund was approved.
Reply to ticket 2501890 that the parcel left today.
Maya Okafor, support lead at Acme Ltd, asked what the latest was on ticket 2501567. Memtro read the ticket's messages and said the customer had chased twice since Tuesday, and an agent's internal note promised a replacement.
Dan Fletcher, a support agent at Northwind, asked Memtro to tell the customer on ticket 2501890 that the refund was approved and would arrive within five days. Memtro read the ticket first, then sent his approved words as a reply on the ticket's email channel. The customer received it at once.
The teams that lean on Trengo most, a question each of them asks, and what they connect beside it.
A record in Trengo is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Trengo, open Settings → Integrations → Rest API.
Create a token, preferably for a service account (trsa_…) with a narrow role so Memtro's access is its own, and copy it. Old-format tokens stop working on 31 January 2027.
In Memtro, open Connections → Trengo and paste it into API token.
Ask: what's the latest on ticket 2501567?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Trengo tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to a ticket (visible to agents only, never sent to the customer); reply to the customer on a ticket's channel (email, WhatsApp, chat); assign a ticket to an agent or a team; close a ticket, optionally with a ticket result; open a new ticket for a contact on a channel (sends nothing by itself); send an approved WhatsApp template to a phone number or a ticket's contact; create a contact on a channel; rename a contact or set its contact groups; delete a contact (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Trengo records into memory as entities.
API token. In Trengo, open Settings → Integrations → Rest API.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time