Monday replies
Sarah Chen, sales development lead at Acme Ltd, asked who had replied to outreach over the weekend. Memtro listed the real replies with campaign, subject and the start of each reply, leaving out bounces and out-of-office notices.
Who replied to our outreach this week, and which leads are still open?
Mailshake connects Memtro to your cold email outreach. It reads campaigns with their message sequence, sender and paused state, a campaign's recipients by what they did, leads by status and assignee, replies with a short excerpt, and sent, opened and clicked activity. When asked, and once an administrator has granted the action by name, it can pause or resume a campaign or a recipient, add recipients, unsubscribe addresses, create a campaign, and create, win, lose, ignore or reopen leads. Every call spends the key's hourly API quota, and the API needs an active paid subscription.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mailshake tool, reads what it needs, and answers with the source cited.
These tools change something in Mailshake. 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 Mailshake 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.
Who replied to our outreach this week?
Which recipients in the Q3 campaign bounced?
Which open leads are assigned to Sarah?
How many emails did the partner campaign send yesterday?
Pause the Q3 outreach campaign
Sarah Chen, sales development lead at Acme Ltd, asked who had replied to outreach over the weekend. Memtro listed the real replies with campaign, subject and the start of each reply, leaving out bounces and out-of-office notices.
Dan Fletcher, head of sales at Northwind, found a wrong price in a running campaign's follow-up. He asked Memtro to pause it. Memtro paused all sending for the campaign in Mailshake, though a batch already being sent was not stopped.
The teams that lean on Mailshake most, a question each of them asks, and what they connect beside it.
A record in Mailshake 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 Mailshake, open Extensions → API as a team administrator. Mailshake refuses keys whose user is not an admin.
Create your key and copy it. It reaches your whole team's campaigns, recipients and leads.
In Memtro, open Connections → Mailshake and paste it into API key.
Ask your first question: who replied to our outreach this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mailshake tools are the same everywhere.
Only when you ask, and only what it has been granted: create a campaign (it cannot send until finished in Mailshake); pause a campaign's sending; resume a paused campaign (its pending emails to prospects are sent); add recipients to a campaign (they are scheduled to be emailed unless the campaign is paused); pause sending to one recipient; resume sending to one recipient (their pending emails are sent); add email addresses to the team's unsubscribe list; create leads from a campaign's recipients; mark a lead won or lost; mark a lead ignored; reopen a won, lost or ignored lead. 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 Mailshake, open Extensions → API as a team administrator. Mailshake refuses keys whose user is not an admin.
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