Renewals at risk
At the Monday meeting the head of customer success asks which renewals are at risk. Memtro lists accounts renewing this quarter with low health, each with MRR, NPS, CSM and the latest note, so the riskiest get attention first.
Which Vitally accounts renew soon with low health, and what the CS team noted.
Connect Vitally with an API key, and Memtro reads customer accounts with MRR, health score, NPS, user count, next renewal date and CSM, the notes and tasks the customer success team keeps on each account, and end users with last seen date and last NPS score. It reads on demand and there is no hourly sync. When you ask, with an Unrestricted key, and once an administrator has granted the action by name, it can add, edit, complete or archive notes and tasks, create accounts, organisations and end users, rename or move accounts, and start or update projects from templates.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Vitally tool, reads what it needs, and answers with the source cited.
These tools change something in Vitally. 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 Vitally 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.
Which accounts renew in the next 60 days with a health score under 6?
What did the CS team note about Northwind last month?
Which open tasks are overdue for my accounts?
Add a note to Brightwave Ltd: QBR held, they want SSO before renewal
Start an onboarding project for Globex from our standard template
At the Monday meeting the head of customer success asks which renewals are at risk. Memtro lists accounts renewing this quarter with low health, each with MRR, NPS, CSM and the latest note, so the riskiest get attention first.
Globex signs, and CSM Laura Chen asks Memtro to set them up. Memtro creates the account with the external id she gives, adds their two admins as end users, and starts an onboarding project from the team's template, which adds the template's own tasks to the account.
The teams that lean on Vitally most, a question each of them asks, and what they connect beside it.
A record in Vitally 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 Vitally an admin opens Settings → Integrations → Vitally REST API and creates a key. Unrestricted lets Memtro make the changes you ask for, Read-only keeps it to reading, and the level cannot be changed later
Note the region, us (the default) or eu, and for a US workspace the subdomain, acme for acme.vitally.io
In Memtro open Connections → Vitally, paste the API key, enter the Region and, for a US workspace, the Subdomain, and connect
Ask which accounts renew in the next 60 days with a low health score
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Vitally tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a customer account; add a task to a customer account; edit, reassign or complete a Vitally task; delete (archive) a Vitally task; edit a Vitally note; delete (archive) a Vitally note; create a Vitally customer account; rename a Vitally account or move it to another organization; add an end user to a Vitally account or organization; edit a Vitally end user; create a Vitally organization; start a Vitally project from a template; update a Vitally project's status, owner or dates. 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 Vitally an admin opens Settings → Integrations → Vitally REST API and creates a key. Unrestricted lets Memtro make the changes you ask for, Read-only keeps it to reading, and the level cannot be changed later.
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