Unassigned queue
Sarah Chen, support manager at Acme Ltd, asked which high-priority tickets had nobody assigned. Memtro listed them with subject, category, contact and due date.
Which high-priority HappyFox tickets are unassigned?
HappyFox connects Memtro to your help desk. It reads tickets by status, category, search, contact or date, with their conversation and private notes. It also reads contacts and contact groups, and the categories, statuses, priorities, agents and custom fields that ids refer to. When asked and granted, it can create tickets, reply as an agent, change status, priority, assignee, due date, tags or custom fields, add private notes, subscribe agents, move, forward or delete tickets, and add or edit contacts. A reply emails the contact only when you say so. Contact 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 HappyFox tool, reads what it needs, and answers with the source cited.
These tools change something in HappyFox. 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 HappyFox 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 high-priority tickets are unassigned?
Which tickets have had no response yet?
What is the latest update on ticket 4410?
Which tickets has Northwind raised this month?
Add a private note to ticket 4410 that the fix ships on Friday.
Sarah Chen, support manager at Acme Ltd, asked which high-priority tickets had nobody assigned. Memtro listed them with subject, category, contact and due date.
Dan Fletcher, support agent at Northwind, asked Memtro to move a ticket to the Engineering category with a note. As granted, Memtro moved it and left a private note, and the new category's agents may have been notified. The contact never saw the note.
The teams that lean on HappyFox most, a question each of them asks, and what they connect beside it.
A record in HappyFox 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 HappyFox, an administrator opens Apps, Goodies, API, enables it and adds a new API key. Hover over its row and click see auth code to copy both.
In Memtro, open Connections → HappyFox and enter the Help desk address, such as acme.happyfox.com, the API key and the Auth code.
An administrator grants the actions by name, such as forwarding tickets, to the teams that may use them. Accounts hosted in the EU use an address ending happyfox.net.
Ask which high-priority tickets are unassigned.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The HappyFox tools are the same everywhere.
Only when you ask, and only what it has been granted: create a ticket (HappyFox emails the contact as usual); reply to a ticket as an agent, emailing the contact only when told to; change a ticket's status, priority, assignee or due date; add a private note to a ticket; set a ticket's custom fields; add or remove tags on a ticket; subscribe agents to a ticket; unsubscribe an agent from a ticket; move a ticket to another category; forward a ticket to an outside email address; delete a ticket; add a contact; edit a contact's name or email. 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 HappyFox records into memory as entities.
Help desk address, API key and auth code. In HappyFox, an administrator opens Apps, Goodies, API, enables it and adds a new API key. Hover over its row and click see auth code to copy both.
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