SLA risk at lunchtime
Sarah Chen, a support lead at Acme Ltd, asked which tickets were awaiting an agent and breaching SLA. Memtro listed them with subject, urgency, department and creation date, oldest first, so she could hand them out.
Which Deskpro tickets are awaiting an agent and breaching SLA?
Deskpro is your helpdesk. Memtro reads tickets by status, agent, requester, organisation, department, label, SLA and date, one ticket in full, its messages and internal notes, and people, organisations, departments and agents. When asked and granted, it can create tickets, reply to the requester, add internal notes, change a ticket's status, agent, department, urgency, labels or hold, merge or delete tickets, add CCs, note people and organisations, and create organisations. The key acts as one agent, whose permissions apply, and email addresses and phone numbers are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Deskpro tool, reads what it needs, and answers with the source cited.
These tools change something in Deskpro. 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 Deskpro 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.
Which tickets are awaiting an agent and breaching SLA?
What has the customer said on ticket ABCD-1234 so far?
How many open tickets does Northwind have?
Which tickets in the billing department are on hold?
Add an internal note to ticket ABCD-1234 that the refund is approved.
Sarah Chen, a support lead at Acme Ltd, asked which tickets were awaiting an agent and breaching SLA. Memtro listed them with subject, urgency, department and creation date, oldest first, so she could hand them out.
Dan Fletcher, a support agent at BigCo, asked Memtro to note on a ticket that engineering had found the cause. Memtro added an internal note, which the other agents saw on the ticket while the requester was not emailed.
The teams that lean on Deskpro most, a question each of them asks, and what they connect beside it.
A record in Deskpro 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 Deskpro Admin, open Apps & Integrations → API Keys and create a key named Memtro for API v2, with the agent Memtro acts as. Only an administrator can make one.
In Memtro, open Connections → Deskpro and paste the Helpdesk host, with no https://, and the whole API key, id:code.
Endpoint tags on the key can deny deletes, for example -*.delete. An administrator grants the reply, merge and delete actions by name to the teams that may use them.
Ask which tickets are awaiting an agent and breaching SLA.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Deskpro tools are the same everywhere.
Only when you ask, and only what it has been granted: create a ticket (triggers may email the requester); reply to a ticket (emailed to the requester); add an internal note to a ticket; change a ticket's status, agent, team, department, urgency, labels or hold; merge one ticket into another (permanent); delete a ticket; add a CC to a ticket (they receive its replies); add a note to a person; add a note to an organisation; create an organisation. 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.
Helpdesk host and API key. In Deskpro Admin, open Apps & Integrations → API Keys and create a key named Memtro for API v2, with the agent Memtro acts as. Only an administrator can make one.
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