Does Instantly Remember Between Runs? The Lead Survives. The Reasoning Does Not.
Does Instantly Remember Between Runs? The Lead Survives. The Reasoning Does Not. Short answer: Instantly keeps the sending record, not the run. A lead keeps its address and its status. A campaign keeps its sequence and its schedule. A reply keeps its place in the Unibox. None of them keeps what a scheduled agent worked out while handling that lead, so the next run opens the same tidy record and starts its thinking from zero. Open Instantly a week later and everything looks remembered. The lead
Does Instantly Remember Between Runs? The Lead Survives. The Reasoning Does Not.
Short answer: Instantly keeps the sending record, not the run. A lead keeps its address and its status. A campaign keeps its sequence and its schedule. A reply keeps its place in the Unibox. None of them keeps what a scheduled agent worked out while handling that lead, so the next run opens the same tidy record and starts its thinking from zero.
Open Instantly a week later and everything looks remembered. The lead list still holds every contact. The campaign still holds its steps in order. The Unibox still holds the replies, sorted and labeled. Under that tidy 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 list actually holds
A lead list is the center of Instantly work. A list holds the leads themselves: email address, first name, last name, company, job title, website, and any custom variables added on import or through enrichment. Each lead also holds a status inside a campaign, so the system knows who has been contacted, who replied, who bounced, and who finished the sequence.
That is useful storage, and an outreach team runs on it. It is also present-tense storage. A list says where a lead stands right now. It does not say why a previous run judged this account worth a second campaign, which signals were checked before that call, or what the next run promised to verify before anyone contacts this lead again. The status answers what happens next. It stays silent on how the last run judged the lead in front of it.
Leads can be reused and moved between campaigns, and that reuse carries the record with them. A lead pulled into a new campaign brings its fields and its variables. What it does not bring is a note about the work done around it: which angle was already tried in a different sequence, which reply was warm but badly timed, or why the team agreed to hold outreach until a hiring round closes. Those are judgments about a company, not fields on a contact, and the list has no place built to hold them.
The block list remembers refusal, not judgment
The protective side of Instantly is built to stop bad sends, and it remembers refusal well. Unsubscribes are honored. Bounced addresses are flagged. A block list holds addresses and domains that must not be contacted again, and it applies across campaigns, so a lead blocked in one place stays blocked in the next. Warmup keeps sending accounts healthy in the background, and inbox rotation spreads volume so no single account carries the whole campaign.
Then comes the part that matters for memory. All of that holds the guardrail. None of it holds the judgment. Which segment keeps replying but never booking and why, which sending account keeps landing in spam for one kind of lead, and which campaign a run paused last week for a named reason: none of that lives in the block list, the warmup pool, or the rotation, and none of it greets the next run when it opens the campaign. The protection is remembered perfectly. The experience of running the outreach is remembered nowhere.
A scheduled job that reviews campaigns to decide the next move gets a clean answer about statuses, blocks, and account health, and no answer at all about the judgment built up across the runs before it. Which leads were already reviewed and cleared, which reply was flagged as a future opportunity rather than a dead end, and why a segment was split in two: none of that rides along in the list, the block list, or the analytics view.
Unibox, analytics, and the same gap everywhere
The rest of the platform stores the same kind of thing, well. The Unibox gathers replies from every connected account into one inbox, with labels for reply types, sentiment sorting, notes, reminders, and saved reply macros, so a conversation can be picked up without hunting across inboxes. Campaign analytics keep the counts that matter: emails sent, opens, clicks, replies, and opportunities, broken down by step, by variant, and by sending account. SuperSearch, the built-in lead database, keeps a large pool of contacts ready to pull into a fresh list.
That is the pattern across the whole platform. Instantly remembers the lead, the sequence, and the reply. It does not remember the work. Every scheduled review, enrichment pass, or follow-up run re-reads the same records and rebuilds the same conclusions, because the conclusions were never stored anywhere the next run looks.
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.
For an Instantly workflow, that changes each run. A daily run that reviews replies and campaign health can save why each lead was kept, held, or dropped, which sequence angle is wearing out, and what to check first tomorrow. The next run reads that record first, checks only what changed in Instantly, and continues instead of rebuilding the judgment from statuses and counts that never held the reasoning.
Plans and control
Vilix AI has a free plan forever, and a 7-day Pro trial with no credit card required. Data can be exported or deleted at any time, so the memory stays under the operator's control.
Get Started for Free Free forever, no credit card.
So, does Instantly remember between runs? Instantly remembers leads, fields, statuses, sequences, schedules, block lists, warmup health, replies, labels, and campaign counts. It does not remember decisions, reasoning, or next steps between runs. Keep Instantly as the system of record for sending. Give the agents and automations around it one shared memory, and each run starts where the last run actually left off.