Persistent memory can help support, but I’d make retrieval deliberately narrow: start with the customer’s account or product and issue category, then surface only a few prior cases with resolution, version, and date. Keep the source ticket attached so an agent can verify the memory instead of treating a summary as policy. I’d also separate durable facts (device model, confirmed workaround) from one-off guesses, and expire or re-check anything tied to a software version. For evaluation, replay a small set of repeat-contact tickets and measure whether the suggested context is correct and reduces time-to-resolution; route low-confidence matches to a human rather than letting memory silently steer the answer.