Ask what the last conversation with a prospect was, and which Reply sequences have stalled.
Connect Reply with an API key and Memtro reads contacts by email, LinkedIn URL, stage or owner with the notes on their timeline, sequences with status and health, tasks, and the inbox of email and LinkedIn conversations. Phone numbers, location and custom fields are never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can send a one-off email or reply in a thread, start sequences that email prospects, enrol or remove contacts, opt them out, add notes, manage tasks, and permanently delete a contact.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Reply tool, reads what it needs, and answers with the source cited.
These tools change something in Reply. 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 Reply 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.
Reply + MemtroWhat was the last conversation with Dan Fletcher at Northwind?
Which sequences are stalled or blocked right now?
What call tasks are due this week, and for which contacts?
Reply to Dan's thread that Thursday at two works for the call
Pause the Q3 outbound sequence
The account executive asks what Brightwave Ltd last said. Memtro finds the contact by email, reads the inbox thread and the notes on the timeline, and answers that Dan Fletcher replied on LinkedIn last Thursday asking for a call after the quarter closes.
Priya Nair asks Memtro to answer Dan Fletcher at Brightwave Ltd that Thursday at two suits. Memtro shows her the reply, and once she approves the words it sends it in the same LinkedIn thread, which Dan receives and which cannot be recalled.
The teams that lean on Reply most, a question each of them asks, and what they connect beside it.
A record in Reply 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
Dialpad
folk
Insightly
Nutshell
Vitally
Nimble
OnePageCRM
Salesflare
CloudTalk
Hunter
Lusha
Ontraport
Streak
EspoCRM
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
Planning Center
ChurchSuite
Affinity
Kommo
Pipeline CRM
KeapIn run.reply.io open Settings → API Key and create a key or copy an existing one. Reply's docs do not say which plans include API access
Give it contacts:read, sequences:read, tasks:read and inbox:read, and add contacts:operate, tasks:write, contacts:write, sequences:operate, inbox:operate or tasks:operate only for the actions Memtro may take. Leave them out for a read-only connection
In Memtro open Connections → Reply, paste the API key and connect
Ask what the last conversation with your newest prospect was
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Reply tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a contact; create a to-do, call or meeting task; create a contact (refused when the email already exists); update a contact's fields; delete a contact; opt contacts out of outreach, or clear it; start or resume a sequence; pause a sequence; archive a sequence; add contacts to a sequence; move a contact to another sequence; remove a contact from a sequence; send a contact a one-off email; reply in an inbox thread; file an inbox thread under a category; complete a task; reassign a task; delete a task. 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 run.reply.io open Settings → API Key and create a key or copy an existing one. Reply's docs do not say which plans include API access.
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