Ask what a visitor asked about on LiveChat, and find old chats by words or date.
Connect LiveChat with your Account ID and a personal access token and Memtro reads current chats, archived threads searched by words, date, group, agent or customer email, a thread's transcript with its tags, and the agents, groups and tags. Customer emails and IP addresses are not read. 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 add internal notes, tag threads, reply to customers, transfer, close, start or resume chats, and ban a customer. A reply reaches the customer and cannot be unsent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right LiveChat tool, reads what it needs, and answers with the source cited.
These tools change something in LiveChat. 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 LiveChat, choosing the same kinds; the tab shows LiveChat's own steps. Each event can start a job, with the event as its input. LiveChat sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce LiveChat 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 did visitors ask about pricing on chat last week?
Show me the transcript of Dan Fletcher's last chat
Which chats in the Sales group are active right now?
Tag the Northwind chat thread as Refund
Reply in the Acme chat that the order ships tomorrow, then transfer it to Billing
On Monday the head of support asks what visitors raised over the weekend. Memtro searches the archive for Saturday and Sunday and reads the transcripts: eleven threads, six about a delivery delay, two tagged Refund and one sales lead from BigCo.
An agent, Sam Okafor, asks Memtro to tell a Brightwave Ltd visitor that billing will pick up their question, then pass the chat on. Memtro sends his approved reply, which the visitor sees at once, adds an internal note for context, and transfers the chat to the Billing group.
The teams that lean on LiveChat most, a question each of them asks, and what they connect beside it.
A record in LiveChat 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 DeskIn the Developer Console open Settings → Authorization → Personal Access Tokens and select chats--all:ro, agents--all:ro, groups--all:ro and tags--all:ro
Add chats--all:rw only to let Memtro reply, add notes and tags, and transfer, close, start or resume chats, and customers.ban:rw only to ban a customer. Scopes cannot change later, and the token acts as the account that made it
In Memtro open Connections → LiveChat, paste the Account ID and the Personal Access Token, and connect
Ask what visitors asked about pricing last week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The LiveChat tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to a chat, visible to agents only; tag a chat thread with an existing tag; reply to the customer in a chat, which they see; transfer a chat to agents or a group; close (deactivate) a chat; start a chat, optionally with a first message the customer sees; resume an archived chat; remove a tag from a chat thread; add an agent to a chat; ban a customer from chatting for a number of days. 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.
Account ID and Personal Access Token. In the Developer Console open Settings → Authorization → Personal Access Tokens and select chats--all:ro, agents--all:ro, groups--all:ro and tags--all:ro.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in LiveChat, choosing the same kinds; the tab shows LiveChat'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