Finding unhappy accounts
Sarah Chen, head of customer success at Acme Ltd, asked which accounts had the lowest NPS. Memtro listed the companies by score with their number of contacts, and quoted recent detractor comments from the lowest.
How has our NPS moved this month, and which accounts are unhappy?
Retently connects Memtro to your customer experience surveys. It reads the latest NPS, CSAT, CES and star scores with promoters, passives and detractors, campaign reports with trend and delivery numbers, and responses with score, tags, topics and the customer's comment. It also reads companies with their scores, campaigns, and one customer's survey status. When asked, and once an administrator has granted the action by name, it can tag responses and set topics, add or update customers, send surveys, which uses survey credits, unsubscribe or resubscribe customers, and permanently delete customers or responses.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Retently tool, reads what it needs, and answers with the source cited.
These tools change something in Retently. 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 Retently 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 is our NPS this month?
Which companies have the lowest NPS?
What did detractors say last week?
How many survey credits do we have left?
Tag yesterday's detractor responses as onboarding
Sarah Chen, head of customer success at Acme Ltd, asked which accounts had the lowest NPS. Memtro listed the companies by score with their number of contacts, and quoted recent detractor comments from the lowest.
Maya Okafor, product manager at Northwind, asked Memtro to tag last week's detractor responses that mentioned onboarding. Memtro added the onboarding tag to each in Retently. Nobody was notified.
The teams that lean on Retently most, a question each of them asks, and what they connect beside it.
A record in Retently 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 Retently, open Settings → Integrations → API and create an API key.
Choose Write permission to let Memtro change things when asked. A key with Read permission gets 403 on every change.
In Memtro, open Connections → Retently and paste it into API key.
Ask your first question: what is our NPS this month?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Retently tools are the same everywhere.
Only when you ask, and only what it has been granted: tag a survey response (append or replace); set a survey response's topics and their sentiment; add or update a customer (email, name, company, tags); send a survey from a transactional campaign to customers (emails them and uses survey credits); unsubscribe customers from surveys; resubscribe customers who were unsubscribed by the account; delete customers and all their data (permanent); delete survey responses (scores are recalculated). 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 Retently, open Settings → Integrations → API and create an API key.
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