# EP 45: Does GetResponse Remember Between Runs? Vilix AI Remembers the Work It Forgets

- URL: https://www.agenticpod.net/episodes/ep45-getresponse-remember-between-runs/
- Watch on YouTube: https://www.youtube.com/watch?v=mDB-OtabWAU
- Published: 2026-11-15
- Length: 5 min
- Hosts: Stella (asks), Liam (answers). Both are AI hosts with AI-generated voices.

## Summary

A GetResponse contact can sit in your account with its tags, custom fields, and a 1 to 5 engagement score, and the next workflow run still starts knowing nothing about the work already done on it.

## Key takeaways

- A GetResponse contact keeps only current state: tags currently assigned, custom fields currently stored, and the score right now, with every later write replacing the earlier value.
- A tag records that a label applies, never why it was applied. The engagement score is just 1 to 5 and cannot explain itself, so the reason behind a decision is gone even though the label stays.
- Workflows share no working state: a second workflow sees only what the first one wrote back, a tag, a field, a list move, or a score change, so an unwritten conclusion is unrecoverable.
- Vilix AI fixes the missing half: get_context at run start loads who was already reviewed and every decision made, and save_turn at the end saves the reasoning and failures back with source labels and newest wins, over MCP with zero infrastructure.

## Chapters

- 0:00 Intro
- 0:37 What a contact actually keeps
- 1:31 Inside one run, and between two workflows
- 2:25 The weekly job that repeats itself
- 3:19 The Vilix AI fix and the verdict

## FAQ

**Does GetResponse remember between runs?**

The contact record remembers: tags, custom fields and the score, all at their latest values. It does not remember the work: why a contact was skipped, which angle was tried and rejected, or what was planned next.

**What do GetResponse custom fields keep?**

Only the latest value, such as name, plan, signup source or a preference. A later write replaces the earlier one, so the history of values is never shown on the contact card.

**Why does a weekly re-engagement job repeat decisions?**

The next run sees only the tags, fields and scores written back. With no note on why a contact was skipped or which angle was rejected, it can repeat a decision that was already thrown out.

**How does Vilix AI help GetResponse workflows?**

The workflow calls get_context before reviewing contacts to load who was already reviewed and every decision made, then save_turn after the run to store decisions and failures with a source label, shared over MCP with every connected workflow.

## Resources

- [Vilix AI, one shared memory for ChatGPT, Claude, Claude Code, Codex, Cursor, OpenClaw, Hermes and every MCP tool](https://vilix.ai)
- [Connect Vilix AI in under two minutes per tool](https://vilix.ai/get-started)
- [Read the full post](https://vilix.ai/blog/does-getresponse-remember-between-runs/)
- [Technical guide with commands and prompts](https://github.com/asly-97/ai-automation-workflows/tree/main/getresponse-remember-between-runs)

## Transcript

### Intro

Liam: Hey hey hey, welcome to Agentic Pod! I'm Liam.

Stella: And I'm Stella! Quick check. Your contact is still in GetResponse today, right?

Liam: Yes. And the engagement score on that contact is just 1 to 5.

Stella: 1 to 5 sounds like it knows the person.

Liam: It knows the record, not the work. Vilix AI is how your workflow remembers its work.

Stella: Wait. The contact survives, but the work on it does not?

Liam: Exactly that. By the end you will know what a contact keeps, and what it loses.

### What a contact actually keeps

Stella: Okay, start simple. What does GetResponse actually store?

Liam: The contact record. Tags currently assigned, custom fields currently stored, and the score right now.

Stella: Custom fields are like, what, name, plan, signup source?

Liam: Exactly. Name, plan, signup source, a preference. A form, an import, an API call, or a workflow sets them.

Stella: And a later write just replaces the old value?

Liam: It replaces it. The contact card shows the latest value, not the history of values.

Stella: Tags are different though, right? They pile up.

Liam: Tags accumulate until removed. A product interest, a customer status, who started a workflow.

Stella: But a tag never says why it was added?

Liam: Never. You just described my whole filing system, and I feel attacked.

Stella: Good. So the label is there, the reason is gone. Where is the catch?

### Inside one run, and between two workflows

Liam: Inside 1 run, things look tidy. A condition admits a contact. Actions send, tag, score, copy, move.

Stella: And conditions branch on the record. Tag assigned, field changed, score given.

Liam: Right. Wait elements hold the contact, and the workflow resumes it at the right element.

Stella: That resume feels like memory though.

Liam: It is workflow progress, not run memory. Once the contact exits, no working notes stay.

Stella: And a second workflow sees even less?

Liam: Way less. Workflows share no working state. The next 1 sees only what was written back.

Stella: A tag, a field, a list move, a score change. That is the whole handoff?

Liam: That is the whole handoff. If nobody wrote the conclusion down, it is gone. Vilix AI keeps that half.

Stella: Hold on. When does this actually bite in real work?

### The weekly job that repeats itself

Liam: A weekly re-engagement job. An agent reviews quiet contacts, and picks who gets a new angle.

Stella: And who should be left alone. That part matters.

Liam: Next week, GetResponse shows the tags, fields, and scores written back. Nothing else.

Stella: No note on why a contact was skipped?

Liam: No note. No angle already tried and rejected. No plan for what comes next.

Stella: So the next run can repeat a decision that was already thrown out?

Liam: Word for word. Same in lead qualification, and onboarding across several workflows.

Stella: And forcing reasons into fields just makes it worse?

Liam: Fields multiply, values get overwritten, only the latest conclusion survives. Vilix AI fixes that gap.

Stella: Alright, Liam. No more tour. Show me the actual fix.

### The Vilix AI fix and the verdict

Liam: Step 1. At run start, the job calls get_context in Vilix AI. That loads who was reviewed, and every decision made.

Stella: Full history, not just the latest field value?

Liam: Full conversation history, not just facts. Reasoning and failures too. Failures save in Vilix AI, so the next run skips them.

Stella: And at the end of the run?

Liam: Step 2. The job calls save_turn in Vilix AI, with a source label. Newest save wins.

Stella: Where do the standing rules live?

Liam: In Vilix AI, as projects, project rules, and user rules. Skills hold repeat workflows. The agent inbox holds next agent notes.

Stella: And the chat tool checking the draft, in a totally different app?

Liam: Same Vilix AI memory, over MCP. The workflow, the agent, every tool, all read the same past.

Stella: Do I host a database or a server for that?

Liam: No. Vilix AI is cloud hosted, zero infrastructure to run. One Vilix AI account per client, so memories never mix.

Stella: Price of admission?

Liam: Vilix AI has a free forever plan, and a 7 day Pro trial, no credit card. Export or delete anytime.

Stella: My verdict: GetResponse remembers the contact perfectly. It remembers the work not at all.

Liam: Same. Keep GetResponse for the record. Let Vilix AI carry the work. Blog and guide are linked below. Does your weekly job repeat decisions? Tell us below. See you next time!
