Your Price Changed Last Week. Why Is Your Scheduled Agent Still Quoting the Old One?

A customer asks for a quote on Monday and gets one number. A salesperson follows up on Thursday and gives a different number. Neither person made a mistake in the usual sense. The price changed in between, but only one of them heard about it. The scheduled agent quoted the old price because that is the price it still carries into every run.

That is not a small embarrassment. A price is a promise, and a scheduled agent repeats the old price on schedule, to customer after customer, until someone notices. The fix is a memory for prices that the agent reads before it quotes, and that gets updated the moment a price changes.

A price is a fact with an expiry date

Most scheduled agents treat a price like a permanent fact. It was written into a prompt, a document, or a workflow months ago, and every run treats it as still true. Prices are not permanent facts. They change with costs, with seasons, with new plans, and with one-off decisions that nobody writes down in the place the agent reads.

A price also needs more than a number: a start date, an end date for any discount, the product or plan it applies to, and the source allowed to change it. Without those details, an agent cannot tell a current price from a retired one.

The same failure happens when a discount ends or a plan is retired. The agent learned the sale price during the promotion, but the end of a promotion is rarely an event in the agent's workflow. It is a date on a calendar somewhere else, so the agent keeps offering the sale price. Likewise, a retired tier can stay in the agent's instructions long after the business stopped selling it.

Why scheduled runs make stale prices worse

A one-off chat that quotes an old price is one bad answer. A scheduled agent that quotes an old price is a system for producing bad answers on repeat.

First, scheduled runs rarely check for changes before they act. The run wakes up, loads its instructions and its list, and works through it. The run is judged successful because messages went out, not because the numbers in them were current.

Second, the price usually lives in more than one place: the website, the CRM, and the pricing document the agent reads can all disagree. A human can sense that disagreement and ask which price is right. A scheduled agent picks the one it was pointed at when the workflow was built, every time.

Third, price changes often happen outside the agent's world. A website update, a quote template change, or a billing update does not flow back into the agent's instructions unless someone builds that flow. The agent is the last to know, and it is the one talking to customers.

Give the agent one price record to read

The practical fix is simple to state and worth building carefully: one current price record per product, plan, or service, and the agent reads that record before every quote.

That record should carry the price, what is included, the date the price took effect, and the date any discount ends, plus who is allowed to change it. When those fields are present, the agent has something to check. When they are missing, the agent is guessing, even if the number looks confident.

Keep retired prices too, clearly marked as retired with an end date. That history explains why a returning customer was quoted a different number last month. When the agent finds two different prices for the same thing, the right behavior is to stop and ask, not to pick one and send it. Build that pause into the run: if sources disagree, or if the price record has no effective date, the run escalates instead of quoting.

What to check before the next run quotes anything

Before the next run, check four things: where the agent gets its price today, whether that record carries dates, whether a price change reaches the agent, and what the agent logs after quoting. If the price comes from a prompt written months ago, that is the problem. A price without an effective date, and an end date for any discount, cannot be trusted by a scheduled run. If a website change does not reach the agent's record, the gap will keep producing old quotes. And the run should log the price quoted, the record it read, and that record's date, so a complaint becomes a diagnosis instead of a mystery.

A memory that updates once and holds for every run

This is where a shared memory layer changes the problem. Instead of a price baked into one workflow, the price lives in memory that every agent and tool can read. Update the price once, and the next scheduled run reads the updated price from the same memory.

Vilix AI works this way. It is cloud-hosted, so there is nothing to install or maintain. The same memory is available everywhere over MCP, so a scheduled agent, a chat tool, and a sales workflow can all read the same current record instead of carrying their own copies. Vilix AI stores full conversation history, not just isolated facts, so the context around a price change stays attached to the record.

That history also helps when a customer pushes back. If a customer says they were quoted a lower price last month, the agent can look back at what was actually quoted and when, instead of guessing.

Vilix AI has a free plan forever, and a 7-day Pro trial with no credit card. Data stays portable: export everything or delete it anytime. Learn more at https://vilix.ai/?utm_source=vilix-blog&utm_medium=article&utm_campaign=scheduled-agent-quotes-old-price-memory

Frequently asked questions

Why does the agent quote an old price if the website shows the new one? Because the agent does not read the website unless it was built to. It reads the instructions, document, or record it was pointed at when the workflow was created. If that source was never updated, the website change never reaches the run.

Is this a model problem? Usually not. The model is repeating an out-of-date number it was given with confidence.

Should the agent check the price on every run? Yes. Prices are exactly the kind of fact that should be re-read before use, not carried forward from the last run. A quick check against the current record costs far less than honoring a wrong quote.

What if two systems show different prices? Do not let the agent pick one silently. Escalate, record both values and their sources, and fix the disagreement at the source.

The price your agent quotes is the price customers believe

A scheduled agent needs one thing before it quotes: the current price, from the current record, with a date it can trust. When that record is shared, dated, and updated in one place, the old price stops haunting every run.