Who is waiting in Crisp, what they said and who they are, in one question.
Connect Crisp with a private plugin's identifier and key and your website id, and Memtro reads conversations by state, unread or assignee, full threads with operator names, contact profiles with company, segments and notes, and operators. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted each action by name, it can message a visitor as an operator, leave private notes, resolve, assign or move conversations, block a visitor, email a transcript and update contacts. A sent message or transcript cannot be recalled, and deleting a conversation or contact is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Crisp tool, reads what it needs, and answers with the source cited.
These tools change something in Crisp. 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 Crisp, choosing the same kinds; the tab shows Crisp's own steps. Each event can start a job, with the event as its input. Crisp signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Crisp 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.
Crisp + MemtroWhich conversations are unresolved and unread right now, and who are they assigned to?
What did Lee Fenwick say in their last conversation with us?
Which contacts in the Enterprise segment have been active this week?
Assign the conversation with lee@brightpath.io to Ana and mark it resolved
Send a note on that conversation for the team: customer is on the annual plan, do not offer the monthly discount
Mid-afternoon the founder asks who is waiting in Crisp. Memtro lists the unresolved conversations with unread messages, each with the visitor's name, segment and last line, and which operator it is assigned to, so the longest wait is dealt with first.
Lee Fenwick from Brightpath asks on the chat whether their export issue is fixed. Ana Ruiz, the operator, checks with engineering and asks Memtro to reply with wording she approves. Memtro sends the message as an operator, Lee receives it on the chat at once, and Memtro resolves the conversation when Ana asks.
The teams that lean on Crisp most, a question each of them asks, and what they connect beside it.
A record in Crisp 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
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 DeskAt marketplace.crisp.chat create a private plugin, open Tokens and ask for a production token with website:conversation:sessions (read), website:conversation:messages (read, and write only if Memtro may send), website:people:profiles (read) and website:operators (read)
For the other actions add only the write scopes named in Memtro's help, such as website:conversation:states and website:conversation:routing to resolve or assign. Install the plugin on your website and trust it, since a plugin token only works where it is installed
Find your Website id under Settings → Website Settings → Setup instructions, then in Memtro open Connections → Crisp, enter the Plugin identifier, Plugin key and Website id, and connect
Ask who is waiting unanswered. Plugin tokens are metered by a daily quota, and development tokens have a small one
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Crisp tools are the same everywhere.
Only when you ask, and only what it has been granted: send a message, or a private operator note, in a conversation; resolve, reopen or mark a conversation pending; assign a conversation to an operator, or unassign it; set a conversation's contact name, email, phone, subject, segments or data; move a conversation to another inbox; block or unblock a visitor's further messages; email a conversation's transcript to an operator or an address; delete a conversation permanently; create or update a contact profile, or add an event to its timeline; delete a contact profile permanently. 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.
Plugin identifier, Plugin key and Website id. At marketplace.crisp.chat create a private plugin, open Tokens and ask for a production token with website:conversation:sessions (read), website:conversation:messages (read, and write only if Memtro may send), website:people:profiles (read) and website:operators (read).
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Crisp, choosing the same kinds; the tab shows Crisp'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