Does lemlist Remember Between Runs? The Lead Survives. The Reasoning Does Not.
Does lemlist Remember Between Runs? The Lead Survives. The Reasoning Does Not. No. A lemlist workspace holds no memory of the work around a campaign between runs. When a scheduled automation or an AI agent opens lemlist, it works from what is in front of it at that moment: the lead, the campaign, the sequence steps, and the activity saved on those records. Anything an earlier run worked out survives only if that run wrote it into a lead field, a custom variable, or a note that a later run can r
Does lemlist Remember Between Runs? The Lead Survives. The Reasoning Does Not.
No. A lemlist workspace holds no memory of the work around a campaign between runs. When a scheduled automation or an AI agent opens lemlist, it works from what is in front of it at that moment: the lead, the campaign, the sequence steps, and the activity saved on those records. Anything an earlier run worked out survives only if that run wrote it into a lead field, a custom variable, or a note that a later run can read.
Open the same workspace a week later and everything looks remembered. The campaign still shows its sequence, step by step. The lead still carries its enrichment and custom variables. The inbox still holds the reply thread. 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 actually holds
A lead is the center of lemlist work, and the lead record holds the present state of that prospect. It carries the contact details, the company, the enrichment results, and the custom variables used to personalize each step. A lead sits inside a campaign, and its position in that campaign is real storage: which steps have run, which step comes next, and when it is due.
That is useful storage, and an outreach team runs on it. It is also present-tense storage. A lead record says who the prospect is and where they stand in one sequence. It does not say why a previous run moved this lead into the campaign and left a near twin out, which personalization angle was tried and quietly failed, or what the next run promised to check before this lead gets touched again. The record answers where the lead stands. It stays silent on how the last run judged it.
The contact layer widens the record a little. Contacts and companies live in a CRM-style database beside the campaigns, with lists, custom fields, and an unsubscribe list that every send respects. A contact can be pushed onward to HubSpot, Salesforce, or Pipedrive. Each of these is a record of a person, not a record of the work done about that person across campaigns.
The four step fields, and the reset hiding inside them
lemlist makes the limit unusually concrete on a contact. Four campaign step fields show where a contact stands: the last executed step number, the date that step ran, the type of the next pending step, and the date that next step is due. Read together, they tell a run what already happened in a sequence and what comes next, without opening the campaign.
Then comes the part that matters for memory. Those four fields describe one campaign only: the last campaign the contact was launched in. Launch the same contact in another campaign and all four fields reset to the new campaign. Step one of the new sequence overwrites the position the contact had reached in the old one. The fields are not designed to report on more than one campaign per contact, so the history of the earlier run survives, if it survives at all, only inside that older campaign itself.
A scheduled job that reads a contact to decide the next move gets a clean answer about the newest campaign and no answer at all about the judgment built up across the ones before it. Which angle earned the reply, which objection came up on a call, and why the team agreed to wait a quarter before trying again: none of that rides along in the step fields.
Inbox, stats, and an assistant that remembers preferences
The rest of the platform stores the same kind of thing, well. The inbox keeps full conversation threads, with filters for unread, replied, and interested. Campaign stats keep opens, clicks, replies, bounces, and unsubscribes over a chosen period, and a consolidated report rolls those numbers up across campaigns. Call activities keep their transcript, recording, and metadata. An agent working through the lemlist MCP can read all of it: campaigns, sequences, leads, threads, tasks, and reports.
lemlist's MCP even has an explicit memory of its own. Its Save memory tool stores persistent context such as your ICP, tone preferences, and campaign goals, so the assistant remembers them across conversations, and Get memory retrieves that context later. That is a real convenience for the person directing the work. It is also a narrow one. It holds the standing preferences the assistant was told to keep. It does not hold what a scheduled run concluded last Tuesday about a specific account, why it paused one sequence and not another, or what it planned to verify on the next pass. Preferences persist. Run reasoning does not, unless a run writes that reasoning somewhere a later run reads.
That is the pattern across the whole platform. lemlist remembers the lead, the campaign, and the activity. It does not remember the work.
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 thread shows what was checked, what was ruled out, and what was promised, in the order it happened. A step field can hold that a lead reached step four. Full history holds why step four was changed for that lead, and what happens if the reply is warm but the timing is wrong.
For an outreach workflow, that changes each run. A daily run that reviews replies and refreshes campaigns can save why each lead was kept, paused, or dropped, which accounts are waiting on a named event, and what to check first tomorrow. The next run reads that record first, checks only what changed in lemlist, and continues instead of rebuilding the judgment from leads and step fields 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 lemlist remember between runs? lemlist remembers leads, custom variables, sequences, step positions, inbox threads, and campaign stats. It does not remember decisions, reasoning, or next steps between runs. Keep lemlist as the system of record for outreach. Give the agents and automations around it one shared memory, and each run starts where the last run actually left off.