In long support sessions where customers raise several issues, older turns are progressively summarized. Late in these sessions the agent misquotes refund amounts and attributes one order's delivery date to another order. Which two changes most directly address this? (Select two.)

Answer: A and C — Extract amounts, dates, and statuses into a persistent case-facts block included in every prompt, outside the summarized history / Store the facts as a separate structured layer with one entry per issue, keyed by order ID

Summaries blur exact values, so transactional facts belong in a persistent block that is updated but never summarized (A), and in a multi-issue session they should be kept per issue so details don't bleed between orders (C). (B) still relies on a lossy summary to carry exact numbers. (D) uses self-reported confidence, which is a poor signal, and pushes the cost onto the customer.