Which urgent Tidio tickets are still open, and who has them?
Tidio connects Memtro to your support inbox. It reads tickets with status, priority and assignment, and each ticket's message history showing who wrote when. It finds contacts by email and shows who wrote when in their live chat, plus operators, departments, tags and custom fields. When asked and granted, it can reply to a ticket or add an internal note, update or open tickets, manage contacts, and delete a contact or a ticket. Tidio can tell Memtro as a ticket is created or a customer leaves a rating, and a job can start on it. Message text is never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Tidio tool, reads what it needs, and answers with the source cited.
These tools change something in Tidio. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Tidio, choosing the same kinds; the tab shows Tidio's own steps. Each event can start a job, with the event as its input. Tidio signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Tidio 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.
Tidio + MemtroWhich open tickets have urgent priority?
Who wrote last on the Northwind refund ticket, and when?
Which operators are active?
Which ticket custom fields must be filled before solving?
Add an internal note to the Northwind refund ticket saying we are waiting on the courier.
Priya Sharma, support lead at Acme Ltd, asked which urgent tickets were still open and who had them. Memtro listed them with operator, department and contact id, and showed from each history who wrote last and when. She took the two with no operator herself.
Northwind set a job to start when a customer left a satisfaction rating in Tidio. When one arrived, Memtro found the contact's latest ticket and added an internal note flagging the rating for the team, as granted. Only operators saw the note, and Tom Reilly, head of support, followed it up the next morning.
The teams that lean on Tidio most, a question each of them asks, and what they connect beside it.
A record in Tidio 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.
Freshdesk
Gorgias
Crisp
Groove
Plain
Freshchat
Freshservice
Kustomer
Dixa
HelpCrunch
Custify
Atera
Trengo
ConnectWise PSA
Enchant
Frill
Gladly
HaloPSA
HappyFox
Jitbit Helpdesk
Nicereply
Re:amaze
SolarWinds Service Desk
Stonly
Syncro
Teamwork DeskIn the Tidio panel, open Settings, then Developer, then OpenAPI, and choose Generate API Key. Only a project owner or admin sees this section, and it needs the Plus or Premium plan.
In Memtro, open Connections → Tidio and paste the Client ID, which starts ci_, and the Client secret, which starts cs_.
The pair has full read and write access, so an administrator grants the reply, update and delete actions by name to the support teams that may use them.
Ask which urgent tickets are still open. Events are turned on from the connection's Events tab, and the address is then added in Tidio's webhook settings.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Tidio tools are the same everywhere.
Only when you ask, and only what it has been granted: reply to a ticket (reaches the customer) or add an internal note; change a ticket's status, priority, assignee, tags or custom fields; open a ticket on behalf of a customer; create a contact; update a contact; delete a contact; delete a ticket. 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.
Client ID and client secret. In the Tidio panel, open Settings, then Developer, then OpenAPI, and choose Generate API Key. Only a project owner or admin sees this section, and it needs the Plus or Premium plan.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Tidio, choosing the same kinds; the tab shows Tidio's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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