Ask which campaign drove the most calls this month, and which calls were missed.
Connect CallRail with an API key and Memtro reads calls with direction, duration, company, source, campaign, tags, lead status and value, and call counts by source, campaign or company. Phone numbers are never returned. 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 tag, note and qualify calls, forms and texts, manage tags and companies, and add users. It can also text a customer or place a real outbound call to one, which reaches a person outside the company and cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right CallRail tool, reads what it needs, and answers with the source cited.
These tools change something in CallRail. 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 CallRail for you. Each event can start a job, with the event as its input. CallRail signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce CallRail 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.
CallRail + MemtroWhich campaign drove the most calls this month?
How many calls did we miss last week, and from which sources?
Which first-time callers were marked as leads yesterday?
Mark yesterday's 3:40pm call from the Leeds number as a qualified lead and tag it spring-promo
Text the caller from this morning's missed call that we will ring back after 2pm
The marketing lead at Acme asks which paid campaigns brought in calls last month. Memtro reads CallRail's summary report grouped by campaign and lists total, answered and first-time calls for each, with the leads they produced.
Dan Fletcher, the office manager at Northwind, asks Memtro to ring back a first-time caller who was missed on Monday. Memtro places the call through CallRail, which rings Dan's desk phone first and then dials the customer, and tags the original call as followed up.
The teams that lean on CallRail most, a question each of them asks, and what they connect beside it.
A record in CallRail 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.
Fullstory
WhatConverts
Lightdash
Microsoft Clarity
Eppo
Holistics
MouseflowCreate an API key in CallRail with your own user. It sees exactly the accounts and companies you can see, and can change only what you can, so adding users needs an administrator's key
If the key is refused with a 403, CallRail may have limited API access to administrators, so ask an administrator
In Memtro open Connections → CallRail, paste the API key and connect. Add the Account ID only if the key sees several accounts
Ask which campaign drove the most calls this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The CallRail tools are the same everywhere.
Only when you ask, and only what it has been granted: create a tag for a company; tag, note, value or qualify a call, or correct the caller's name; tag, note, value or qualify a form submission; tag, note, value or qualify a text thread; text a customer from a tracking number; place an outbound call: ring a business phone, then the customer; rename, recolour, enable or disable a tag; delete a tag (removes it from everything it was applied to); create a company; rename a company or change its time zone; disable a company and its tracking numbers; add a user to the account (CallRail emails them). 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. Create an API key in CallRail with your own user. It sees exactly the accounts and companies you can see, and can change only what you can, so adding users needs an administrator's key.
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 CallRail 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
