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

Does Smartlead Remember Between Runs? The Mailbox Pool Survives. The Judgment Does Not.

Does Smartlead Remember Between Runs? The Mailbox Pool Survives. The Judgment Does Not. Short answer: Smartlead keeps the sending record, not the run. A lead keeps its fields and its status. A campaign keeps its sequence, its schedule, and its mailbox pool. A reply keeps its thread and its category in the Master Inbox. None of them keeps what a scheduled agent worked out while handling that lead, so the next run opens the same complete record and starts its thinking from zero. Open Smartlead a

Does Smartlead Remember Between Runs? The Mailbox Pool Survives. The Judgment Does Not.

Short answer: Smartlead keeps the sending record, not the run. A lead keeps its fields and its status. A campaign keeps its sequence, its schedule, and its mailbox pool. A reply keeps its thread and its category in the Master Inbox. None of them keeps what a scheduled agent worked out while handling that lead, so the next run opens the same complete record and starts its thinking from zero.

Open Smartlead a month later and everything looks remembered. The mailboxes are still connected and warmed. The campaigns still hold their steps in order. The Master Inbox still holds every reply from every account in one place. 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 lead keeps

A lead in Smartlead keeps the contact record. The fields travel with the lead: email address, name, company, and any custom variables added on import or pulled from the built-in prospect database. Inside a campaign, the lead also keeps its place in the sequence and its status, so the system knows who has been sent step one, who is waiting on a follow-up, who replied, and who should receive nothing more.

That record persists between runs, and an outreach program runs on it. Reuse a lead in a later campaign and the fields come with it. Check a list next week and the statuses still stand. The sending engine never has to guess where a contact stands.

What the record stays silent on is judgment. A lead holds no note about why a previous run decided this account deserved a short sequence instead of the standard one, 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 lead in front of it, and that judgment is the part a scheduled review rebuilds from scratch every time.

What a campaign and a mailbox pool keep

A campaign keeps its full setup between runs. The sequence steps stay written and in order, with the delays between them. A/B variants stay in place, so a tested subject line keeps its record. The schedule and the sending limits stay set. Campaigns move through clear statuses, from draft to active to paused or stopped, and analytics keep the counts that matter: emails sent, opened, clicked, replied, and bounced, broken down across the run of the campaign.

The mailbox pool keeps the other half of the operation. Connected accounts stay connected. Warmup keeps each account building and holding its sending reputation in the background. Rotation spreads volume across the pool, so no single inbox carries a campaign alone and burns out. For agencies, client workspaces keep each client's campaigns and accounts separate, with separate access and separate records.

Read that list again and the shape is clear. A campaign keeps how outreach runs. A mailbox pool keeps how outreach stays healthy. 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 lead was added. Those are decisions, and Smartlead stores sends, rules, and counts, not decisions.

The Master Inbox remembers replies, not reviews

The Master Inbox is the closest thing in the platform to a shared memory, and it shows the boundary well. Every reply from every connected mailbox lands in one view. Replies are categorized, with labels such as interested, not interested, out of office, and unsubscribe, and a lead category can trigger a subsequence, so a reply moves the lead into the right follow-up path without a human sorting it first. Threads stay whole, so a conversation can be read from the first touch to the latest answer.

Even there, the stored thing is the conversation with the lead, not the work around the lead. A scheduled agent that triages the Master Inbox 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 inbox, the categories stay on the leads, and the conclusions go nowhere the platform reads. Tomorrow's run opens the same categorized inbox and forms the same conclusions again, one thread at a time.

Smartlead's own assistant makes the same point from the other side. The assistant lives inside the Smartlead account, learns the account as it is used, and holds memory across conversations inside the platform. It only works inside Smartlead, so that memory helps inside one tool and stops at the tool's edge. A scheduled workflow that also touches a CRM, a spreadsheet, a chat tool, and a coding agent gets no share of it.

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 lead status can hold where a contact stands. Full history holds why that lead was kept, paused, or moved, which signal changed the call, and what to watch before the next touch.

So the pattern for Smartlead work becomes simple. Smartlead keeps doing what it does well: sending at volume, rotating mailboxes, warming accounts, and gathering every reply into one inbox. 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 leads 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 sending record was never the problem. Smartlead 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.