Every Zammad ticket, reply and internal note, answered and remembered as it changes.
Connect Zammad, hosted or self-hosted, with its URL and an agent's access token, and Memtro searches tickets by state, group, customer, owner or words, reads a ticket with its articles including internal notes, counts tickets by state, and looks up users and organisations. Every hour it writes each changed ticket into memory. When asked, and once an administrator has granted each action by name, it adds notes or email replies to the customer, creates, updates, closes, tags and links tickets, and creates or updates customers and organisations. An email reply cannot be recalled, and deleting a ticket is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Zammad tool, reads what it needs, and answers with the source cited.
These tools change something in Zammad. 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 Zammad 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.
How many tickets are open in the Sales group and how many are pending reminder?
Which tickets from Lindqvist AB are still open and who owns them?
Show me ticket 1184 with the internal notes
Add an internal note to ticket 1184: replacement unit dispatched on 5 November, tracking sent
Reply to ticket 1190 that the parcel left today, then set it to pending close
The support manager asks for the state of the queue before the weekly meeting. Memtro counts open, new and pending tickets in each group, names the oldest open ones with their owners, and lists what changed since yesterday from the hourly sync.
An Acme customer escalates by phone. Lucy Ward asks Memtro for ticket 1184, reads every article and the internal notes, then asks it to email the customer that a replacement left today and raise the priority. Memtro sends the approved reply in her name and changes the priority, both kept in the ticket's history.
The teams that lean on Zammad most, a question each of them asks, and what they connect beside it.
A record in Zammad 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
Tidio
Teamwork DeskAn administrator first switches Token Access on under Settings → System → API. Then in Zammad open your avatar → Profile → Token Access and create a token
Tick ticket.agent for tickets, users and the note or reply action, admin.group for the group list, admin.organization only for creating and updating organisations, and admin only if deleting tickets is wanted. Copy the token: it is shown once and never has more rights than you do
In Memtro open Connections → Zammad, paste the Base URL and the Access token, and connect
Ask how many tickets are open in Sales. Searches by state, group or customer need Zammad's Elasticsearch index, which a standard install has
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Zammad tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note or an email reply to a ticket; create a ticket; change a ticket's title, group, state or priority; close a ticket; tag or untag a ticket; link two tickets; create a user (customer); update a user's contact details; create an organisation; update an organisation; delete a ticket (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 Zammad records into memory as entities.
Base URL and access token. An administrator first switches Token Access on under Settings → System → API. Then in Zammad open your avatar → Profile → Token Access and create a token.
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