Ask what a customer has contacted support about, and which Kustomer conversations are still open.
Connect Kustomer with your org name and an API key and Memtro reads customers with email, tags and last activity, conversations by status, priority or date, and each conversation's messages and internal notes. The hourly sync writes customers into memory. When you ask, and once an administrator has granted the action by name, it can add internal notes, save reply drafts, send email or SMS replies to customers, close, snooze, assign or tag conversations, and create or update customers. Replies reach the customer at once and cannot be recalled, SMS is charged by your provider, and deletions are permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Kustomer tool, reads what it needs, and answers with the source cited.
These tools change something in Kustomer. 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 Kustomer for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Kustomer signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Kustomer 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.
Kustomer + MemtroWhat has Brightwave Ltd contacted us about this month?
Which conversations are open with priority 4 or above?
What internal notes are on Priya Nair's conversations?
Add an internal note to the Acme refund conversation: finance approved it
Email Dan Fletcher at BigCo that his refund has been issued, and close the conversation
Support picks up a conversation from Dan Fletcher at BigCo. Memtro finds him by email and reads his last four conversations with their messages and internal notes: two were about invoices, one is still snoozed, and a colleague noted a pending refund.
The support lead, Aisha Khan, asks Memtro to tell Northwind's office manager that the replacement order has shipped. Memtro sends her approved email from the support address into the open conversation, which the customer receives at once, then marks the conversation done.
The teams that lean on Kustomer most, a question each of them asks, and what they connect beside it.
A record in Kustomer 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
Dixa
HelpCrunch
Custify
Atera
Trengo
ConnectWise PSA
Enchant
Frill
Gladly
HaloPSA
HappyFox
Jitbit Helpdesk
Nicereply
Re:amaze
SolarWinds Service Desk
Stonly
Syncro
Tidio
Teamwork DeskOrg name is the word before .kustomerapp.com in your sign-in address: acme.kustomerapp.com means acme
A Kustomer admin opens Settings → Security → API Keys → Add API Key and gives it the read roles for customers, conversations, messages, notes and search
Add the create, update and delete roles for notes, customers and conversations, and apps.read for sending, only for the actions Memtro may take. Roles cannot change later and the token shows once
In Memtro open Connections → Kustomer, enter the Org name, paste the API key and connect
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Kustomer tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to a conversation; create a customer; save an unsent reply draft for an agent to review; send an email reply to a customer from a support address; send an SMS reply to a customer; close, reopen, snooze, prioritise, rename or assign a conversation; add tags to a conversation; remove tags from a conversation; open a new conversation for a customer; update a customer's name, emails, phones or locale; delete a conversation permanently; delete a customer 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. An hourly sync anchors recently changed Kustomer records into memory as entities.
Org name and API key. Org name is the word before .kustomerapp.com in your sign-in address: acme.kustomerapp.com means acme.
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 Kustomer 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