Free forever, no credit card.Get Started for Free →
← All posts
November 18, 2026 · 6 min read

Does Mailshake Remember Between Runs? The Prospect Survives. The Reasoning Does Not.

Does Mailshake Remember Between Runs? The Prospect Survives. The Reasoning Does Not. Short answer: Mailshake keeps the outreach record, not the run. A prospect keeps its fields and its place in a sequence. A campaign keeps its steps, its delays, and its sending settings. A reply keeps its thread in the Lead Catcher. None of them keeps what a scheduled agent worked out while reviewing that prospect, so the next run opens the same complete record and starts its thinking from zero. Open Mailshake

Does Mailshake Remember Between Runs? The Prospect Survives. The Reasoning Does Not.

Short answer: Mailshake keeps the outreach record, not the run. A prospect keeps its fields and its place in a sequence. A campaign keeps its steps, its delays, and its sending settings. A reply keeps its thread in the Lead Catcher. None of them keeps what a scheduled agent worked out while reviewing that prospect, so the next run opens the same complete record and starts its thinking from zero.

Open Mailshake a month later and everything looks remembered. The campaigns are still there with their sequences in order. The prospects still carry the fields from the CSV import. Replies still sit in the Lead Catcher waiting for a decision. Under that complete surface, each run still starts with only the records in front of it, and none of the reasoning from the run before.

What a prospect keeps

A prospect in Mailshake keeps the contact record. Upload a CSV and the fields travel with the prospect: email address, name, company, and the custom fields used for text replacements in the copy. Inside a campaign, the prospect also keeps its place in the sequence, so the system knows who received the first email, who is waiting on a follow-up, and who should receive nothing more.

That place is protected by clear rules. Follow-ups continue until the prospect becomes a lead. Anyone who unsubscribed or bounced is skipped. A reply pauses the prospect in that sequence, so a person who answered does not keep getting automated touches as if nothing happened. Split a large list across campaigns, up to 5,000 prospects on Email Outreach and 10,000 on Sales Engagement, and each prospect still keeps its own status inside its own campaign.

What the record stays silent on is judgment. A prospect holds no note about why a previous run decided this account deserved a shorter sequence, which signals were checked before that call, or what the next run promised to verify before anyone writes to this company again. The status answers what happens next. It says nothing about how the last run judged the prospect in front of it, and that judgment is the part a scheduled review rebuilds from scratch every time.

What a campaign keeps

A campaign keeps its full setup between runs. The first email and every follow-up stay written and in order, each with the delay set after the previous send. Add a follow-up at the end of a sequence that already ran and the delay counts from the last send for that prospect, so timing stays honest. Drip messages sit alongside the sequence as a separate structure, sent on schedule as new emails rather than replies in the thread. A/B tests keep their variants, and the sending calendar and daily limits stay set.

SHAKEspeare, the built-in AI writer, fits the same pattern. Give it the basics about a business and it drafts copy inside Mailshake. The draft becomes part of the campaign. The reasoning behind the angle, which audience it was written for, which objection it was meant to answer, and what a review learned from the replies it produced, lives nowhere in the campaign record.

Read that list again and the shape is clear. A campaign keeps how outreach runs. A sequence keeps when the next touch goes out. Analytics keep how outreach scored. None of them keeps why a run changed the plan mid-flight, which segment was cut after a review and on what evidence, or what the next review was supposed to check before another prospect was added. Those are decisions, and Mailshake stores sends, rules, and counts, not decisions.

The Lead Catcher remembers replies, not reviews

The Lead Catcher is the closest thing in the platform to a shared memory, and it shows the boundary well. Replies land there for review. Open a lead, reply from the same place, and mark it Won, Lost, or Ignored to clear it from the open queue. If the prospect writes again, the lead comes back. A lead can be reassigned or moved to another campaign, so the conversation follows the work.

Even there, the stored thing is the conversation with the prospect, not the work around the prospect. A scheduled agent that triages the Lead Catcher each morning, sorts the warm replies from the noise, and flags the accounts worth a human call finishes its run holding a set of conclusions. Which replies matter and why. Which accounts are warming up. Which segment keeps answering but never booking, and what pattern explains it. When the run ends, the replies stay in the Lead Catcher, the marks stay on the leads, and the conclusions go nowhere the platform reads. The next run opens the same queue and forms the same conclusions again, one thread at a time.

That gap grows when the review touches more than Mailshake. A morning check that also reads a CRM, a spreadsheet, and a chat tool has to rebuild the whole picture in every tool, because no one tool holds the reasoning that connects them.

What a shared memory layer adds

A shared memory layer sits outside any one tool and holds the full context of the work itself. Vilix AI is built for exactly that job. It is cloud-hosted, so there is zero infrastructure to run or maintain. The same memory is available everywhere over MCP, so a scheduled agent, a chat tool, and a coding tool all read the same shared state instead of separate copies.

Vilix AI stores full conversation history, not just extracted facts. That matters when the next run needs the reason, not only the result. The full history shows what was checked, what was ruled out, and what was promised, in the order it happened. A prospect status can hold where a contact stands. Full history holds why that prospect was kept, paused, or moved, which signal changed the call, and what to watch before the next touch.

So the pattern for Mailshake work becomes simple. Mailshake keeps doing what it does well: running sequences, pausing prospects who reply, and gathering every answer into the Lead Catcher. The scheduled agent reads Vilix AI before it reviews a campaign, so it starts from the last run's conclusions instead of rebuilding them. When the run ends, it writes back what it decided and why, which prospects it cleared, which it held, and what the next run must check first. The next run, in any tool that reads the same memory, starts from that note instead of from a blank page.

The outreach record was never the problem. Mailshake keeps that record with care. The missing piece was always the record of the thinking, and that piece needs a home built for it.

Get Started for Free

Free forever, no credit card. Vilix AI offers a free plan forever and a 7-day Pro trial with no credit card required, and data can be exported or deleted at any time.

Get Started for Free

Persistent memory across ChatGPT, Claude, and the AI tools you already use in Vilix AI.

Get Started for Free

Free forever, no credit card.

Keep reading
Does Groove Remember Between Runs? The Conversation Survives. The Reasoning Does Not.

Does Groove Remember Between Runs? The Conversation Survives. The Reasoning Does Not. Short answer: Groove keeps the conversation, not the run. A customer is remembered between conversations. A conversation keeps its full thread, its notes, and its history of actions. None of that keeps what a scheduled agent worked out while reviewing those conversations, so the next run opens the same complete record and starts its thinking from zero. Open a conversation in Groove and nothing looks forgotten

Does Olark Remember Between Runs? The Transcript Survives. The Reasoning Does Not.

Does Olark Remember Between Runs? The Transcript Survives. The Reasoning Does Not. Short answer: Olark keeps the transcript, not the run. A visitor is remembered between visits. A chat keeps its full transcript, its notes, and its place in that visitor's history. None of that keeps what a scheduled agent worked out while reviewing those chats, so the next run opens the same complete record and starts its thinking from zero. Open the Transcripts page in Olark and nothing looks forgotten. Past c

Does Aircall Remember Between Calls? The Call Is Saved. The Run Is Not.

Does Aircall Remember Between Calls? The Call Is Saved. The Run Is Not. Short answer: Aircall keeps the call, not the run. Every call can be recorded, transcribed, summarized by AI, and synced into a CRM record. A caller who phones back is not starting from an empty file. None of that keeps what a scheduled agent worked out while reviewing those calls, so the next run opens the same complete record and starts its thinking from zero. Open the call history in Aircall and nothing looks forgotten.