Does Kustomer Remember Between Runs? The Timeline Survives. The Reasoning Does Not.
Does Kustomer Remember Between Runs? The Timeline Survives. The Reasoning Does Not. Short answer: Kustomer keeps the customer record, not the run. A customer keeps one permanent record with every conversation attached to it. A conversation keeps its messages, its internal notes, its status, and its assignment. A custom object keeps the orders, subscriptions, and other records a team chose to model. None of them keeps what a scheduled agent worked out while working that record, so the next run o
Does Kustomer Remember Between Runs? The Timeline Survives. The Reasoning Does Not.
Short answer: Kustomer keeps the customer record, not the run. A customer keeps one permanent record with every conversation attached to it. A conversation keeps its messages, its internal notes, its status, and its assignment. A custom object keeps the orders, subscriptions, and other records a team chose to model. None of them keeps what a scheduled agent worked out while working that record, so the next run opens the same complete timeline and starts its thinking from zero.
Open Kustomer a month later and everything looks remembered. The timeline still shows every contact in order. Old conversations are still there, next to orders and events. 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 customer keeps
A customer in Kustomer is the center of the whole system. That is the design choice that sets the platform apart. Instead of a ticket standing alone, every conversation belongs to exactly one customer, and that customer record stays permanent while conversations come and go around it.
That gives a returning customer real continuity. A third contact this month does not arrive as a stranger. The record shows who the person is, which company they belong to, and what conversations they already had. A scheduled agent that reads the customer first can see the shape of the relationship before it replies, instead of treating each new message as a first contact.
What the customer record stays silent on is judgment. It holds no note about why a previous run decided this customer needed a careful human reply instead of a fast automated one, which earlier conversation explained the current complaint, or what the next run promised to verify before closing the case. The record answers who this person is and what happened with them. It says nothing about how the last run judged the situation, and that judgment is the part a scheduled review rebuilds from scratch every time.
What a timeline and a conversation keep
The timeline is the view that pulls the record together. Conversations with their messages and notes, custom objects such as orders and subscriptions, and tracked events all land on one timeline, merged and sorted by time. An order placed last week sits next to the conversation where the customer asks about it. That placement is the point. Context is visible without hunting through separate systems.
A conversation keeps its own working state. Inside it are the messages exchanged with the customer and the internal notes a team wrote to each other. It carries its queue, its assignee, its status as open, snoozed, or done, and the channels it used. Its events record each change, with before and after values, so a reader can see what changed and when.
Custom objects add the structured layer. A Klass defines the schema for a type of record, such as an order or a booking. Each record created from that schema is an object that hangs off a customer or a company and shows up on the timeline. Because those attributes are typed, workflows can route, escalate, or send a message based on an order status or a subscription tier.
Read that list again and the shape is clear. A timeline keeps what happened, in order. A conversation keeps what was said and where the work stands. A custom object keeps the business record a team modeled. None of them keeps why a run escalated one conversation and closed another, which pattern across thirty timelines pointed to the same fault, or what the next review was supposed to check first. Those are decisions, and Kustomer stores records, events, and statuses, not decisions.
Workflows remember steps, not triage
Workflows and business rules hold a different kind of memory. A business rule performs actions when a conversation is created or updated, based on customer, company, conversation, and message attributes. A workflow runs a set of conditions and actions after an event, and each step inside that one workflow can use data collected by the steps before it.
That last point matters, and it has a clear boundary. Data can move forward inside a single workflow run. It does not become a shared record of reasoning that the next scheduled run can read. When a workflow finishes, its conditions and actions stay ready for the next event. The conclusions it reached about this customer, this order, and this morning do not stay in a form the next run starts from.
That gap grows when the review touches more than Kustomer. A morning check that also reads a billing tool, a store, and a chat tool has to rebuild the whole picture in every tool, because no one tool holds the reasoning that connects them. The timeline is complete inside Kustomer. The thinking that linked the timeline to everything outside it leaves with the run.
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 timeline can hold where a customer stands. Full history holds why a conversation was escalated, which order explained the complaint, and what to watch before the next reply.
So the pattern for Kustomer work becomes simple. Kustomer keeps doing what it does well: holding one permanent customer record, showing every conversation and object on one timeline, and automating steps with workflows and rules. The scheduled agent reads Vilix AI before it reviews the timeline, 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 conversations 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 customer record was never the problem. Kustomer 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.