Pricing on the sales call
Tom Reilly, account executive at Northwind, asked what was said about pricing on the last recorded sales call. Memtro found the moments where pricing came up and gave the speaker-by-speaker lines around each one.
What was said about pricing on our last recorded sales call?
AssemblyAI shows you the transcripts your key made in the last 30 days, with their status. Memtro reads any transcript's text or speaker-by-speaker utterances, with its summary, chapters, key phrases and topics where they were requested. It can also page through paragraphs and find where given words were said. When asked and granted, it can transcribe an audio file at a URL, billed per audio second, or delete a transcript's data permanently. AssemblyAI can tell Memtro when a transcript is ready or has failed, and a job can start on it. Each transcription request must name the Memtro address itself.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right AssemblyAI tool, reads what it needs, and answers with the source cited.
These tools change something in AssemblyAI. 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 AssemblyAI, choosing the same kinds; the tab shows AssemblyAI's own steps. Each event can start a job, with the event as its input. AssemblyAI sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce AssemblyAI 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 was said about pricing on the last recorded sales call?
Which transcripts failed this week, and why?
Summarise the chapters of yesterday's board meeting recording.
Where in the onboarding call did anyone mention SSO?
Transcribe the recording at this link.
Tom Reilly, account executive at Northwind, asked what was said about pricing on the last recorded sales call. Memtro found the moments where pricing came up and gave the speaker-by-speaker lines around each one.
At Acme Ltd, a job starts when AssemblyAI says a transcript is ready. It reads the summary and chapters, then finds where the words renewal and discount were said. Priya Sharma, customer success lead, gets those moments to review.
The teams that lean on AssemblyAI most, a question each of them asks, and what they connect beside it.
A record in AssemblyAI 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 assemblyai.com/dashboard, open API Keys and create a new key or copy an existing one. A key has the whole account's access, with no scopes.
Open Connections → AssemblyAI in Memtro and paste the API key. Set Region to eu if the key and its transcripts live in the EU.
An administrator grants transcribe and delete by name to the teams that may use them. Events are turned on from the connection's Events tab, and each transcription request then names the Memtro address as its webhook.
Ask what was said about pricing on the last recorded sales call.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The AssemblyAI tools are the same everywhere.
Only when you ask, and only what it has been granted: transcribe an audio or video file at a URL (billed per audio second); delete a transcript's text and data 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.
API key. In assemblyai.com/dashboard, open API Keys and create a new key or copy an existing one. A key has the whole account's access, with no scopes.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in AssemblyAI, choosing the same kinds; the tab shows AssemblyAI'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