Call quality review
Priya Sharma, customer operations lead at BigCo, asked how the booking agent's calls went yesterday. Memtro listed them with how each ended, Retell's summary and sentiment, and flagged the unsuccessful ones.
How did our AI agents' calls go, and what did they cost?
Retell AI shows you calls with their agent, direction, status, duration, how they ended, Retell's summary, sentiment, success and cost. It reads chats, agents, phone numbers with the agents that answer them, and live concurrency. When asked and granted, it can place an outbound AI call or start an SMS conversation, both billed. It can also stop a call, end a chat, delete calls, re-run analysis, manage contacts and publish an agent version. Retell can tell Memtro as it happens when a call finishes, and a job can start on it. Transcripts and recordings are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Retell AI tool, reads what it needs, and answers with the source cited.
These tools change something in Retell AI. 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 Retell AI, choosing the same kinds; the tab shows Retell AI's own steps. Each event can start a job, with the event as its input. Retell AI signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Retell AI 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.
How did yesterday's outbound calls end?
Which calls had negative sentiment this week?
Which agent answers our support number?
How many calls are live right now?
What did the renewal agent's calls cost last week?
Priya Sharma, customer operations lead at BigCo, asked how the booking agent's calls went yesterday. Memtro listed them with how each ended, Retell's summary and sentiment, and flagged the unsuccessful ones.
When a call finished in Retell, a job started for Dan Fletcher at Northwind. It read the call's summary, sentiment and success, and listed the unsuccessful calls for his team to follow up.
The teams that lean on Retell AI most, a question each of them asks, and what they connect beside it.
A record in Retell AI 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 the Retell dashboard open Settings, then API Keys, add a key named Memtro and copy it. Restrict its permissions if you want reads only.
In Memtro open Connections → Retell AI and paste the API key.
An administrator grants the call, SMS and agent actions by name, since calls and texts are billed. Events are turned on from the connection's Events tab, and the address is then added in Retell's webhook settings.
Ask: how did yesterday's outbound calls end?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Retell AI tools are the same everywhere.
Only when you ask, and only what it has been granted: place an outbound AI phone call to a number (rings the person; billed per minute); start an outbound SMS conversation with a number (texts the person; billed); stop a live call; end an ongoing chat; set a call's metadata, custom attributes or data retention; re-run a call's post-call analysis (billed); delete a call and its recording and transcript; delete a chat; add a contact; edit a contact or mark it do-not-call; delete a contact; point a phone number at an agent for inbound or outbound calls or texts; publish a draft agent version. 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 the Retell dashboard open Settings, then API Keys, add a key named Memtro and copy it. Restrict its permissions if you want reads only.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Retell AI, choosing the same kinds; the tab shows Retell AI'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