Morning support check
Each morning the support lead asks what is open. Memtro lists threads in Todo by priority with the customer, assignee, labels and a preview, so the urgent ones from Brightwave Ltd are picked up before the rest.
What is open in support, what a customer said and which threads carry which label.
Connect Plain with an API key from a machine user and Memtro reads support threads by status, priority, customer, label or date, a full-text search across titles, messages and customers, a thread's timeline, customers with their companies, and label types. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can reply to customers or email them, which they receive at once, start threads, add notes, labels and internal tasks, mark threads done, snooze, assign, reprioritise or rename them, and permanently delete a thread.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Plain tool, reads what it needs, and answers with the source cited.
These tools change something in Plain. 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, choose the kinds you want, and Memtro registers its address with Plain for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Plain signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Plain 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.
What is open in support right now, by priority?
Which threads from Acme have come in this month?
Has anyone reported the export timeout error this week?
Reply to thread T-123 that the fix ships on Thursday
Label that thread as Bug and assign it to Dan Fletcher
Each morning the support lead asks what is open. Memtro lists threads in Todo by priority with the customer, assignee, labels and a preview, so the urgent ones from Brightwave Ltd are picked up before the rest.
Engineer Ravi Patel finds the cause of a failed CSV import and asks Memtro to tell the Northwind customer. Memtro shows the reply, and once he approves it sends it on the thread's own channel, labels the thread Bug and marks it Done. The customer receives the reply at once.
The teams that lean on Plain most, a question each of them asks, and what they connect beside it.
A record in Plain 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 Plain open Settings → Machine users & agents, add a machine user, then add an API key
Give it thread:read, timeline:read, customer:read and labelType:read, and add only the write permissions for what Memtro should do, such as note:create, thread:reply or thread:edit. Copy the key, Plain shows it once
In Memtro open Connections → Plain, paste the API key and connect
Ask what is open in support since Monday
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Plain tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to a customer or one of their threads; add labels to a thread; create an internal task for the support team; reply to the customer on a thread; email a customer, as a new thread or on an existing one; reply to a customer's email; start a new thread for a customer; mark a thread Done; move a thread back to Todo; snooze a thread; assign a thread to a teammate; unassign a thread; change a thread's priority; rename a thread; remove labels from a thread; update an internal task; permanently delete a thread. 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.
API key. In Plain open Settings → Machine users & agents, add a machine user, then add an API key.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Plain for you. 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