Morning queue check
Sarah Chen, support lead at Acme Ltd, asked which open tickets had no assignee. Memtro listed them with subject, inbox and labels, newest first, and read the messages on the oldest one.
Which Enchant tickets are open and unassigned right now?
Enchant connects Memtro to your shared inbox. It reads tickets by state, inbox, assignee, label and date, and each ticket's messages and customer. It also lists your agents and finds customers by email. When asked and granted, it can add an internal note, email a reply to the customer, open a ticket, change a ticket's state, assignee, inbox or subject, add or remove labels, and create or edit customers and their contacts. With events on, Enchant tells Memtro when a label is added to a ticket, and a job can start on it. You add that webhook in Enchant.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Enchant tool, reads what it needs, and answers with the source cited.
These tools change something in Enchant. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Enchant, choosing the same kinds; the tab shows Enchant's own steps. Each event can start a job, with the event as its input. Enchant signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Enchant 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 Enchant tickets are open and unassigned?
What has the customer said on ticket 4821 so far?
Which tickets labelled refund are on hold?
Which agents are on the help desk?
Add an internal note to ticket 4821 saying the replacement has shipped.
Sarah Chen, support lead at Acme Ltd, asked which open tickets had no assignee. Memtro listed them with subject, inbox and labels, newest first, and read the messages on the oldest one.
At Northwind, a job starts when a label is added to an Enchant ticket. It reads the ticket and its messages and, as granted, adds an internal note summarising the thread for Tom Reilly, the support manager. Only agents see the note.
The teams that lean on Enchant most, a question each of them asks, and what they connect beside it.
A record in Enchant 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 Enchant, open Settings, Apps, API, install the API app and copy the access token it shows. The token has no scopes and full access to the help desk.
In Memtro, open Connections → Enchant and enter your Help desk site, such as acme for acme.enchant.com, and the Access token.
An administrator grants the actions by name, such as emailing replies, to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added in Enchant's Webhooks app.
Ask which Enchant 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 Enchant tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to a ticket; email a reply to the customer on a ticket; open a new email ticket for a customer; change a ticket's state, assignee, inbox or subject, or mark it spam or trash; add labels to a ticket; remove labels from a ticket; create a customer; change a customer's name, summary or contacts; add an email, phone or Twitter contact to a customer; delete a contact from a customer. 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 Enchant records into memory as entities.
Help desk site and access token. In Enchant, open Settings, Apps, API, install the API app and copy the access token it shows. The token has no scopes and full access to the help desk.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Enchant, choosing the same kinds; the tab shows Enchant's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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