Product patterns

MemoryRouter is most valuable when the product relationship gets better over time. These patterns show what to remember, why it matters, and how to implement it cleanly.

AI companions

Remember: names, preferences, recurring topics, boundaries, emotional context, routines, important people, long-term story arcs.

Why it matters: a companion without memory is a chat window. A companion with memory becomes a relationship.

Implementation notes: keep one Memory Key per user. Store explicit preferences and high-signal relationship context. Avoid storing sensitive details the user has opted out of remembering.

AI coaches

Remember: goals, habits, check-ins, blockers, wins, accountability style, prior advice, milestones.

Why it matters: coaching compounds when the product knows what the user committed to last week.

Implementation notes: use memory to keep the plan stable across sessions. Import existing onboarding answers and progress logs with the upload endpoint.

AI tutors

Remember: learning style, current curriculum, weak spots, mastered topics, past mistakes, pacing, accommodations.

Why it matters: tutoring gets better when the product knows what the student almost understands.

Implementation notes: store progress as durable memory and keep session transcripts scoped to the learner. Use deletion/export workflows for education privacy requirements.

Support agents

Remember: customer preferences, prior tickets, product usage, unresolved issues, escalation history, account context.

Why it matters: users hate explaining the same problem twice. Memory turns support from reactive to continuous.

Implementation notes: map Memory Keys to customer or account identity depending on your support model. Be explicit about whether memory is per user, per account, or per workspace.

Sales assistants

Remember: company context, contacts, objections, buying stage, previous conversations, renewal dates, implementation concerns.

Why it matters: sales agents need account continuity. Memory keeps the assistant aligned with the relationship, not just the latest email.

Implementation notes: decide whether the vault boundary is a person, account, or sales workspace. Never mix unrelated accounts in one vault.

Internal copilots

Remember: employee preferences, team terminology, project history, architecture decisions, recurring workflows.

Why it matters: internal copilots become useful when they know how your organization actually works.

Implementation notes: use one vault per employee for personal context, or one vault per workspace for shared team memory. Keep access boundaries aligned with your internal permissions.