The agent that remembers: account context and "what was promised" in AI support, and why most AI forgets at the handoff

A customer who writes to your business twice expects the second reply to know about the first. When an AI assistant answers, that expectation acquires a legal edge: in Moffatt v. Air Canada (2024 BCCRT 149), a British Columbia tribunal held the airline to its chatbot's wrong answer and ordered CAD $812.02.² Yet the record of what an assistant said is exactly what many tools discard when a person takes over. Meta's Business Agent documentation states that on hand-back "the agent loses earlier conversation context."¹ This piece sets out what an agent must know before it replies, what it should and may know, and how to keep a written record of every promise.

What does AI customer support that remembers actually mean?#

AI customer support that remembers is an agent that replies with three distinct records in view, and passes all three to whoever answers next. The three are often blurred together in vendor copy, so it helps to define them separately.

• Account context. The standing facts about this customer: plan or package, order or booking on file, the address they write from, anything flagged.
• Conversation history. What this customer asked before and what was answered, in which channel, and when.
• The promise record. Every commitment the business made: a quoted price, a time held, an add-on agreed, a reply-by time given, a refund said to be under review.

The demand for all three is explicit in owner and customer language. A thread in r/smallbusiness (10+ comments, September 2026) described the wanted assistant as one that "remembers every customer: what they asked, what you promised".⁸ On Hacker News in June 2026, one commenter praised an AI support experience because "I never have to repeat myself", and another called "has previously contacted us about something, and we want records of this" "a basic need."⁵ A third commenter, who ran a rollout, reported that bot-only containment "shot up past 50%" with "basic knowledge support with account awareness."⁵ That is one practitioner's report, not a measured benchmark, and it should be read as such.

Is a business bound by what its AI assistant told a customer?#

A business may be bound by its assistant's statements, and the public decisions so far point in that direction rather than away from it. The status of each matters, because a tribunal order, a voluntary settlement and a company apology carry different weight.

Three points of applicability follow. First, a Civil Resolution Tribunal decision binds its parties; it is not a statutory mandate and it does not bind courts in other provinces or states. Second, the tribunal did not treat the chatbot's separate status as an affirmative defense, and PYMNTS summarised the wider pattern in July 2026 as courts telling companies that they own what their chatbot says.¹¹ Third, no public decision we found sets a materiality threshold below which an assistant's statement can be ignored; the Air Canada amount was small and still ordered.

The BMW case is the most instructive for memory. The Drive reported that the root cause was a figure a human employee had miscommunicated, which the bot then treated as the buyback offer.³ The failure was a record problem: the assistant held the wrong version of what had been promised, and nothing showed the dealer which version it used until the customer held them to it.

Why does AI support forget at the handoff?#

AI support forgets at the handoff because, in many products, the conversation and the human queue are separate systems, and nothing obliges the first to pass its record to the second. Vendor documentation states this plainly when you look for it. Meta's Business Agent, per 360dialog's known-limitations page, "stops answering that chat" once it hands off to a human, and on hand-back "loses earlier conversation context."¹

Buyers ask the question in public. A thread in r/CRM (60+ comments, 2026) put it directly: "When AI escalates to a human, how much context actually transfers?"⁹ A builder in r/LLMDevs (9 comments, 2026) wrote that "Most assistants completely forget customer context between conversations".¹⁰ And the outcome of a handoff without a record is measurable: Gorgias found that one-third of support tickets handed off by AI never received a human reply, and that the median wait after handoff was 10 hours (Oct 2025 to Apr 2026 data).⁶

Billing definitions can make the gap worse. Fin's pricing page counts a resolution when "No further help is requested after Fin's last answer," at $0.99 per outcome.⁷ A customer who gives up because the agent did not know their account looks the same, under that definition, as one whose problem was solved.

What must an AI support agent know before it replies?#

An AI support agent must know enough to avoid contradicting the business, and no more than the reply needs. The matrix below uses the three modal levels with their ordinary force: must is a precondition for sending any reply, should is expected practice, and may is discretionary. These are operating rules for a small business, not legal obligations.

The order matters. A business that gives an agent account access before it writes down its prices and its open promises has built recall without a reference point, and the BMW case shows where that ends.

The promise ledger: one record per commitment#

The promise ledger is a running list of every commitment made to a customer, whoever made it, with the source and the time. It is the record a person reads before replying, and the record an assistant must check before sending. The sample below is an illustration, not a real customer.

The fourth row is the one most systems lose, because a person agreed it outside the assistant's conversation. If that add-on is forgotten once a month, the business either waives $500 or argues with a customer who has the email; at one a month that is $6,000 a year on an illustrative basis. The ledger's rule is simple: a promise made by anyone, in any channel, goes on the same list.

What must an agent with memory never do?#

An agent with memory must never treat what it remembers as permission. Recall widens what an assistant can say, so the limits on what it may say need to be written down before access is granted. In the June 2026 Hacker News thread, one commenter raised the risk that an account-aware support bot leaks data to the wrong person.⁵ The rules below address that risk and the promise risk together.

1. Match before you recall. Account details are used only when the sender matches the account. An unknown address asking about "my order" gets general facts and a request to write from the address on file.
2. Never invent a promise. The agent may repeat a promise from the ledger. It may not extend, improve or create one; discounts, refunds and exceptions go to a person.
3. Carry the record across the handoff. The person who takes over sees the conversation, the open promises and the reason for the handoff in one place, and the customer is told who replies and by when.
4. Log what was used. Each reply records which facts and which ledger entries it relied on, so a wrong answer can be traced to a wrong source.
5. Keep less. Store only the fields a reply needs. Privacy law on inquiry data was outside the scope of this piece; ask counsel what applies in your jurisdiction.

Questions to take to counsel#

Several questions remain unsettled, and a small business should decide them in writing rather than leave them to the next dispute. No decision we found answers them directly.

• Does a time held by an assistant, with an expiry stated to the customer, create an obligation to honour that time if the hold lapses unnoticed?
• Does labelling every reply as AI-written change how a tribunal reads a wrong statement? The public summaries relied on here do not answer that.
• If a human employee feeds the assistant a wrong figure, as in the BMW report, who in your business owns the correction?
• How long should the promise ledger and conversation history be kept, and who may read them?

For the customer-facing side of the handoff, the handoff contract sets out what the customer should be told. For what a billed "resolution" means across vendors, see what counts as an AI resolution, and for running support@ as a founder, the solo-founder runbook.

Where Valet fits#

Valet is an AI assistant for written inquiries that you forward to it; replies go out from your own address. It answers only from the facts you give it and never invents a price, discount or policy. Each inquiry sits in one of the Valet Inquiry States with a next step and a time. Every reply comes with a Valet receipt: what was asked, the rule used, the sources used and where it was sent from, which is the written record a person reads before stepping in. Money, complaints and contracts go to you with one-tap replies, and the customer is told when you will reply. Valet does not read the rest of your inbox, and messages are not used to train AI models. To see what your current replies remember and forget, start with the free lead check.