What is open in the inbox and what a customer has written in about, from Groove.
Connect Groove with an admin's private access token and Memtro reads conversations by state, assignee, tag, contact or keyword, one conversation with its messages and internal notes, contacts with their companies, agents and tags. The hourly sync writes conversations into memory. When you ask, and once an administrator has granted the action by name, it can reply to a customer or start a new email conversation, add internal notes and tags, close, reopen, snooze, assign or merge conversations, and mark them as spam or trash them. Replies and new emails reach customers and cannot be recalled, and merging is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Groove tool, reads what it needs, and answers with the source cited.
These tools change something in Groove. 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.
Once Groove 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.
Groove + MemtroWhat is open in the inbox right now, and who is it assigned to?
What has priya@brightwave.co.uk written in about this year?
Which conversations were tagged billing this week?
Show me conversation 4812 with its notes
Reply to conversation 4812 that the refund went out today, then close it
Before a renewal call the account lead asks what Acme has written to support. Memtro finds the contact, lists their conversations with state and tags, and reads the latest in full, so the call opens with the open billing question.
Dan Fletcher asks Memtro to tell the customer on conversation 4812 that the Northwind refund went out today. Memtro shows the reply, and once he approves the words, sends it from Groove as his agent to the customer's address and closes the conversation.
The teams that lean on Groove most, a question each of them asks, and what they connect beside it.
A record in Groove 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
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 Groove open Settings → Organization → API and copy the private access token, which only an admin can see and which carries that admin's access
In Memtro open Connections → Groove, paste the Access token and connect
Memtro changes or sends anything only when asked, and only the actions an administrator granted
Ask what a customer has written in about
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Groove tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to a conversation; add tags to a conversation; create a tag; reply to a customer on a conversation (sends an email); start a new email conversation (sends an email); close a conversation; reopen a conversation; mark a conversation as spam; move a conversation to the trash; assign a conversation to an agent or team; unassign a conversation; snooze a conversation; remove tags from a conversation; change a conversation's subject; merge two conversations. 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 Groove records into memory as entities.
Access token from an admin. In Groove open Settings → Organization → API and copy the private access token, which only an admin can see and which carries that admin's access.
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