Ask what was said on a customer's last Dialpad call and who took it.
Connect Dialpad with an API key and Memtro reads concluded calls with direction, duration, contact, who took them, labels and CSAT, call transcripts with Dialpad AI moments, contacts and users. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can send texts, place, transfer or hang up calls, queue call backs, manage contacts and call labels, set operators on or off duty, and block numbers. Texts and calls reach people outside the company from a company number, cannot be recalled and may carry charges.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Dialpad tool, reads what it needs, and answers with the source cited.
These tools change something in Dialpad. 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, choose the kinds you want, and Memtro registers its address with Dialpad for you. Each event can start a job, with the event as its input. Dialpad signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Dialpad 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.
Dialpad + MemtroWhat was agreed on our last call with Acme?
Which calls did the support team take yesterday, and how long were they?
Who does the number +44 20 7946 0958 belong to?
Add the label renewal-risk to Tuesday's call with Northwind
Text Dan Fletcher at Northwind that the engineer arrives at 10:00
The account lead missed a call between support and Northwind. She asks Memtro what was said. It finds the concluded call, reads the transcript and Dialpad AI moments, and answers with the questions raised, who took the call and how long it ran.
Priya Sharma asks Memtro to have the support team call back a customer at Brightwave Ltd who rang while the queue was full. Memtro queues a call back to that number in the support call centre, and the next free operator dials it within the centre's hours.
The teams that lean on Dialpad most, a question each of them asks, and what they connect beside it.
A record in Dialpad 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.
Capsule CRM
Copper
Freshsales
folk
Insightly
Nutshell
Vitally
Nimble
OnePageCRM
Salesflare
CloudTalk
Hunter
Lusha
Ontraport
Reply
Streak
EspoCRM
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
Planning Center
ChurchSuite
Affinity
Kommo
Pipeline CRM
KeapOnly a Company Admin can make API keys, and a key reads every user's calls in the company, and some Dialpad plans may not include API keys
In Dialpad Admin Settings → My Company → Authentication → API Keys, Add Key with a name and expiry, add calls:list and whatever scopes Dialpad offers for transcripts, contacts and users, and copy it, since it is shown once
In Memtro open Connections → Dialpad, paste the API key and connect
Ask what was agreed on the last call with a customer
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Dialpad tools are the same everywhere.
Only when you ask, and only what it has been granted: create a contact in Dialpad; add labels to a Dialpad call; send a text message from a Dialpad user to phone numbers or a channel; send one text from a Dialpad number to up to 50 phone numbers; change a Dialpad contact's name, company, job title, emails or phones; permanently delete a Dialpad contact; ring a Dialpad user's devices to call a phone number; hang up a live Dialpad call; transfer a live Dialpad call to a number, user, department, call centre or office; queue a call back to a number in a Dialpad call centre; set a Dialpad operator on or off duty in their call centres; block phone numbers company-wide in Dialpad; unblock phone numbers company-wide in Dialpad. 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. Only a Company Admin can make API keys, and a key reads every user's calls in the company, and some Dialpad plans may not include API keys.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Dialpad for you. 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