SLA breaches before standup
Sarah Chen, support manager at Acme Ltd, asked which tickets had breached their SLA this week. Memtro listed them with inbox, agent, customer and response minutes, and flagged two still unassigned.
Which Teamwork Desk tickets are breaching their SLA, and who has them?
Teamwork Desk connects Memtro to your help desk. It reads tickets with subject, status, priority, inbox, assigned agent, customer, tags, and response and resolution times, and a ticket's messages cut short. It finds customers by name or company and reads inboxes, agents, statuses, priorities, ticket types and tags. When asked, and once an administrator has granted the action by name, it can open a ticket without notifying the customer, reply to the customer, change status, priority, agent or inbox, add a customer, log time and delete a ticket. Phone numbers, addresses and notes are not read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Teamwork Desk tool, reads what it needs, and answers with the source cited.
These tools change something in Teamwork Desk. 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 Teamwork Desk 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 have breached their SLA this week?
What has BigCo raised with support this month?
Which urgent tickets are unassigned?
What did the customer say in the last message on ticket 2210?
Assign ticket 2210 to Sarah and set it to high priority
Sarah Chen, support manager at Acme Ltd, asked which tickets had breached their SLA this week. Memtro listed them with inbox, agent, customer and response minutes, and flagged two still unassigned.
Dan Fletcher, support lead at Northwind, asked Memtro to move a BigCo ticket to the billing inbox and give it to Priya Sharma at high priority. Memtro changed the inbox, agent and priority in Desk. The customer was not emailed, though Desk's own rules may tell the new agent.
The teams that lean on Teamwork Desk most, a question each of them asks, and what they connect beside it.
A record in Teamwork Desk 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 Teamwork Desk, open your avatar → View Profile → API Keys.
Create an API key and copy the Key. It acts as you and sees what you see in Desk, so consider a dedicated Desk user for Memtro.
In Memtro, open Connections → Teamwork Desk and paste Site (acme.teamwork.com, or acme.eu.teamwork.com for an EU-hosted account) and API key.
Ask your first question: which tickets have breached their SLA this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Teamwork Desk tools are the same everywhere.
Only when you ask, and only what it has been granted: open a ticket for a customer, without notifying them; reply to a ticket's customer (sent to them by e-mail); change a ticket's status, priority, assigned agent or inbox; add a customer, without a welcome e-mail; log time against a ticket as the key's user; 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. An hourly sync anchors recently changed Teamwork Desk records into memory as entities.
Site and API key. In Teamwork Desk, open your avatar → View Profile → API Keys.
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