Does Woodpecker Remember Between Runs? The Prospect Survives. The Reasoning Does Not.
Does Woodpecker Remember Between Runs? The Prospect Survives. The Reasoning Does Not. Short answer: Woodpecker keeps the outreach record, not the run. A prospect keeps its fields and its status. A campaign keeps its steps, its conditions, and its schedule. A reply keeps its thread in the inbox. 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 Woodpecker a month later and ev
Does Woodpecker Remember Between Runs? The Prospect Survives. The Reasoning Does Not.
Short answer: Woodpecker keeps the outreach record, not the run. A prospect keeps its fields and its status. A campaign keeps its steps, its conditions, and its schedule. A reply keeps its thread in the inbox. 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 Woodpecker a month later and everything looks remembered. Campaigns are still there with steps in order. Prospects still carry import fields. Replies still sit in the inbox. Under that surface, each run 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 Woodpecker keeps the person record. A prospect carries fields such as first name, last name, email, company, and position, plus custom fields and snippets a team adds for personalisation. Prospects arrive by import, by manual add, or through an integration, and the same prospect record can be reused across campaigns instead of being rebuilt each time.
Inside a campaign, the prospect also keeps its place. The system knows which step was sent, which step comes next, and whether this person should still receive anything at all. A campaign stops sending follow-ups to a prospect when that prospect replies. An opt-out or blacklist status excludes an address across the account, even if that address is added to a new campaign by mistake. An autoresponder is marked AUTOREPLIED, and follow-ups are suspended while that state is reviewed. That protection is real memory, and it is the reason outreach does not blindly restart for people who already answered or already opted out.
What the record stays silent on is judgment. A prospect holds no note about why a previous run decided this account deserved a longer sequence instead of a short one, which signals were checked before that call, or what the next run promised to verify before anyone contacts 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 plan between runs. A campaign can hold up to 16 steps in a single sequence, mixing email steps with manual, LinkedIn, or call tasks. Steps can branch on a condition, so a prospect who meets a condition follows one path and a prospect who does not follows another. Follow-up timing stays set, with a delay in days before each next step, and follow-ups can be sent in the same thread as the earlier message or as a separate message.
A/B test variants stay set too, and the stats stay attached to the campaign. The campaign view keeps counts for prospects, delivered, opened, and responded, along with interest level, invalid addresses, bounces, and the queue still waiting to send. The To Check tab keeps a different kind of record: prospects who were not contacted yet and whose sending was suspended, waiting for a person or a run to fill missing data, change a status, or set a new date.
Read that list again and the shape is clear. A campaign keeps how outreach runs. A step keeps when the next touch goes out. Stats 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 Woodpecker stores sends, rules, and counts, not decisions.
The inbox remembers replies, not reviews
The Woodpecker inbox is the closest thing in the platform to a shared memory, and it shows the boundary well. Replies from campaigns land in one place, so a thread can be picked up without digging through a personal mailbox. A reply is matched to its prospect and its campaign, the full email thread stays readable, and the prospect record shows last activity: when an email was sent, when it was opened, and when the prospect responded. Bounced messages have their own place for review as well.
Even there, the stored thing is the conversation with the prospect, not the work around the prospect. A scheduled agent that triages the 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 updates stay on the prospects, and the conclusions go nowhere the platform reads. The next run opens the same inbox and forms the same conclusions again, one thread at a time.
That gap grows when the review touches more than Woodpecker. 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 person 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 Woodpecker work becomes simple. Woodpecker keeps doing what it does well: running cold email sequences, stopping a sequence when a person replies, and gathering every answer 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 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. Woodpecker keeps that record with care. The missing piece was always the record of the thinking, and that piece needs a home built for it.
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.