Morning queue check
Sarah Chen, support lead at Acme Ltd, asked which tickets were open and unassigned. Memtro listed them with requester, priority and when each was last messaged, oldest first.
Which HelpDesk tickets are open and waiting on the team?
HelpDesk connects Memtro to your email ticketing on HelpDesk.com. It reads tickets with subject, requester, status, priority, team, assigned agent, tags and rating, and one ticket's messages with private notes marked. It also reads agents, teams and tags. When asked, and once an administrator has granted the action by name, it can open a ticket, reply to the requester, add an internal note, change status, priority, subject or assignment, tag a ticket, add followers, ask the customer to rate, and delete a ticket. Replies, new tickets and rating requests reach the customer by email.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right HelpDesk tool, reads what it needs, and answers with the source cited.
These tools change something in HelpDesk. 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 HelpDesk 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 open and unassigned?
What did BigCo's last ticket say?
Which tickets were rated bad this month?
How many open tickets carry the billing tag?
Add a note to ticket 1042 saying the refund is approved
Sarah Chen, support lead at Acme Ltd, asked which tickets were open and unassigned. Memtro listed them with requester, priority and when each was last messaged, oldest first.
Tom Reilly, support agent at Northwind, asked Memtro to add a note to a customer's ticket saying the refund had been approved and to mark it pending. Memtro added the private note and changed the status. The customer saw nothing, as private notes are never sent to the requester.
The teams that lean on HelpDesk most, a question each of them asks, and what they connect beside it.
A record in HelpDesk 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.
Sign in to developers.livechat.com/console with your HelpDesk email and password, and open Tools → Personal Access Tokens.
Create a token named Memtro with the scope accounts--my:ro, and copy it with the Account ID shown beside it. The token acts as you, so consider a dedicated agent for Memtro.
In Memtro, open Connections → HelpDesk and paste Account ID and Personal access token.
Ask your first question: which tickets are open and unassigned?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The HelpDesk tools are the same everywhere.
Only when you ask, and only what it has been granted: open a ticket for a requester (HelpDesk e-mails them the first message); reply to a ticket's requester (sent to them by e-mail); add an internal note to a ticket (agents only); change a ticket's status, priority, subject, team or assigned agent; add tags to a ticket; add agents as followers of a ticket; send the customer a request to rate the ticket (e-mails them); delete a ticket (to the trash, purged after 30 days). 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.
Account ID and Personal access token. Sign in to developers.livechat.com/console with your HelpDesk email and password, and open Tools → Personal Access Tokens.
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