They Are Still Waiting on a Fix. Why Does Your Scheduled Agent Keep Trying to Sell Them Something Else?

A customer has been waiting four days for a billing dispute to be resolved. The charge is wrong, the support thread is still open, and no one has given her a final answer yet. Then your scheduled agent sends her a cheerful message: upgrade to the annual plan and save.

Nothing in the workflow failed. The schedule fired on time, the message went out, and the run log shows success. The failure is quieter: the agent never learned that this customer has an open complaint, so every run treats her like a happy prospect instead of a person waiting on a fix.

That message does damage a discount cannot undo. The customer does not read it as a mistimed offer. She reads it as proof that the business is not listening: her complaint is still unresolved, and the next thing she hears from the company is a sales pitch.

The sales list and the support queue never meet

The usual cause is not a bad prompt. It is two lists that were never joined.

The scheduled agent reads a sales list: customers on a monthly plan who are eligible for an annual upgrade. That list is built from billing records, and billing records say nothing about an open complaint. The complaint lives somewhere else entirely: a support inbox, a helpdesk queue, or a chat thread that the sales workflow never opens.

Each run therefore works from a partial picture. It sees the plan, the tenure, and the upgrade eligibility, and nothing about the dispute. From that narrow view, the pitch looks perfectly reasonable. The agent is not ignoring the complaint. It simply has no way to see it, because no run ever put the complaint where the sales run reads.

Timing makes it worse. A complaint can be opened after the sales list is built and before the message is sent. The list was accurate when frozen, and wrong by the time the message goes out, and a run reading a frozen list cannot catch a complaint that arrived after the freeze.

A pitch during a complaint is not just bad timing

It helps to be clear about why this particular mistake stings more than most automation errors. A wrong-name greeting is embarrassing. A duplicate message is annoying. A sales pitch to a customer with an open complaint feels dismissive, because it arrives at the exact moment the customer is asking to be heard.

The customer is also the person least likely to forgive it quietly. Someone with an open dispute is already paying close attention to every message from the business. She will notice the pitch, forward it to support, and quote it back in the thread where she is still waiting for help. One automated message can turn a routine dispute into a complaint about how the business treats people who raise problems.

Support staff inherit the mess too. They open the thread expecting to resolve a billing dispute and find a customer who is now also angry about an upsell. The dispute takes longer, and the support team spends its time repairing damage from a workflow it never approved.

What a suppression memory actually holds

The fix is not to stop upselling. It is to give the sales run a suppression check it cannot skip: before any pitch goes out, the run reads the customer's current support state.

A useful suppression record is short, and it needs five parts.

First, whether an open case exists, with its case number. A vague note that a customer "had an issue once" is not a suppression rule. An open case with a number is.

Second, what the case is about, in one line: billing dispute, faulty order, delivery problem, refund request. The category matters, because it tells the next run whether the customer is waiting on money, a replacement, or an answer.

Third, the case status and the date of the last update.

Fourth, a simple hold rule: while a case is open, no sales pitch goes out. Not a softer pitch, not a pitch with an apology attached. No pitch. The hold is the rule, and exceptions to it need a named human, not a workflow edit.

Fifth, one place every run reads before it writes. If the sales workflow, the support tool, and the email tool each hold their own version of the customer's state, the pitch will eventually slip through the gap between them. The suppression record has to be the single record the sales run checks.

Hold the pitch, then resume with the resolution first

A hold is not a cancellation. When the case closes, the customer may well be ready to hear about the annual plan. The mistake is pitching mid-dispute, not pitching after resolution.

The right sequence after resolution is also specific. The first message after a case closes should acknowledge the resolution, not open with an offer. It should confirm what was fixed, in the customer's terms, and leave the pitch for a later message, once the customer has confirmed that the fix actually held. A pitch that arrives in the same breath as the resolution reads like the resolution was just a setup for the sale.

Test it the way a customer would experience it. Open a test complaint, let the next scheduled sales run fire, and read what it sends. If the pitch goes out while the case is open, the suppression record is not the thing the run reads, and editing the sales list will not fix that until it is.

Where Vilix AI fits

This is the kind of memory that has to survive between runs and across tools, not just inside one workflow. Vilix AI is a cloud-hosted memory layer, so there is no infrastructure to run: the agent reads and writes memory over MCP, and the same memory follows the customer record across every connected tool instead of living in one workflow's copy.

Because Vilix AI stores full conversation history, not just extracted facts, the complaint thread itself stays retrievable: what the customer reported, what was promised, and what is still outstanding. The sales run reads the current support state before it plans the run, sees the open case, and holds the pitch. When the case closes, the record updates, and the next run sees a resolved customer.

Vilix AI is free forever, with a 7-day Pro trial that needs no credit card, and everything stored can be exported or deleted at any time. Start with the suppression record: open case, category, status, last update, and the hold rule. Give every sales run one place to read it before it writes a pitch, and the upgrade offer stops landing on customers still waiting on a fix.

Your agent will keep meeting customers it already knows. Check the next pitch it sends to a customer with an open complaint: if it goes out anyway, the offer is not the problem. The memory is.

Learn more about giving scheduled agents a memory that survives between runs: Vilix AI