# Engine: Deploy. One agent. The whole journey. Memory across all of it. ![](/assets/einstein-hats.svg) The loop, phase 03 of 04 # Deploy. One agent. The whole journey. This is where the agent meets your customers. Living Memory makes every interaction feel like the agent already knows them, because it does. [Book a pilot→](/en/contact-us/) Why Deploy ## Stop greeting your customers like strangers. Most AI tools speak to a customer like a stranger every time. Even the second visit is a cold open. Deploy changes that. The agent shows up across acquisition, retention, expansion, and support, with full memory and full context. The customer feels known. Because they are. How Deploy works ## Two senses. Always-on context. Living Context ### The agent across the journey. Same agent, every moment. In your tone, on your surfaces, with full context. 1. 01 **Every customer moment.** Acquisition, retention, expansion, support. One agent, one brain. 1. 02 **Your tone, your surfaces.** Website, in-product, portal, chat. In your customer's language. 1. 03 **Front and back awareness.** Up front, the agent knows where the customer is and which Audience they belong to. Behind the scenes, it is connected to your business systems. 1. 04 **Procedures from Train, live in Deploy.** Fires in-app notifications proactively. The right nudge at the right moment, not a marketing blast. 1. 05 **Hands off cleanly.** When it cannot solve, it brings in the right human with full context, not a fresh ticket. Living Memory ### Relationships, automated. The agent treats every interaction like it already knows the customer. Because it does. Three substrates, working in sync. 1. 01 **User profile.** Structured, CRM-style data on each customer - preferences, lifecycle stage, tier, sentiment, goals. 1. 02 **Audience.** Categorized memberships of groups with similar traits. The agent knows which cohort a visitor belongs to before they identify themselves. 1. 03 **Working memory.** A running, qualitative record of every previous interaction. The agent picks up where it left off. Acquisition leans on audience. Retention and support lean on working memory. By the time someone is a customer, the agent uses all three. ## Your customers stay known. Without anyone keeping notes. Privacy posture Living Memory runs through the Privacy Vault. PII is tokenized. Memory stays in your account. Customers can request export or deletion at any time. Acquisition ## The agent never opens cold. Page, audience, lifecycle stage feed every reply. The agent answers from the full picture, so customers feel known from the first message, not the fifth ticket. unless.com/en/dashboard/deploy/acquisition [![](/assets/svg/icon-light.svg)](/) Dashboard ## Acquisition 5 signals · retention - ### Churn risk language Active Cancellation intent, comparison shopping, escalating frustration in conversation. 28 live · last 4m ago - ### Pricing pushback Active Customer questions value, asks for discounts, or compares to competitor pricing. 14 live · last 22m ago - ### Reduced usage Active Login frequency or feature use drops below the customer’s 30-day baseline. 9 live · last 1h ago - ### Renewal approaching Active Contract end date within 60 days; surface renewal pricing and account health. 73 live · last 8m ago - ### Competitor mention Draft Named competitor referenced in a customer-facing exchange. Not yet enabled - Add signal From library Retention ## Save plays where churn lives. Procedures fire inside the product, at the moment a customer hesitates. Cancellation, downgrade, feature confusion - each gets the right intervention before the support queue does. unless.com/en/dashboard/deploy/retention [![](/assets/svg/icon-light.svg)](/) Dashboard ## Retention 5 procedures · acquisition - Book a meeting Active - Qualify the lead Active - Send pricing details Active - Route to an account executive Active - Send a re-engagement email Draft Expansion ## Nudges that earn their place. In-app notifications go out when an expansion signal lights up, not on a marketing schedule. The right offer, at the right moment, with the right owner notified. unless.com/en/dashboard/deploy/expansion [![](/assets/svg/icon-light.svg)](/) Dashboard ## Sales expansion 5 notifications · expansion - Upgrade to Pro offer Card - Add team seats Banner - Annual billing savings Inline - Power-user perks Card - Pro features tour Modal Support ## Your tone, on every channel. Personality is configured once and applied everywhere - every helpdesk, every chat, every escalation. The agent always sounds like you, never like a stock template. unless.com/en/dashboard/deploy/support [![](/assets/svg/icon-light.svg)](/) Dashboard ## Support - Warmth Cool Warm - Pacing Brief Detailed - Formality Casual Formal - Confidence Tentative Assertive > I can absolutely see how frustrating this is — let me look into the account right away and walk you through what I find. You shouldn't have to chase this twice. Next in the loop [Phase 04 Analyze Performance. Value. Maturity. All visible. All live.](/en/engine/analyze/) See it applied [See Deploy across all four customer moments →](/en/agent/acquisition/) unless.com/en/dashboard/train/knowledge [![](/assets/svg/icon-light.svg)](/) Dashboard ## Knowledge base 6 sources · knowledge base - Engineering wiki · 1.2k docs Connected - Sales playbook · 348 docs Team only Connected - Team Assistant · 5.8k tickets Connected - Public docs site · 89 pages Syncing - Compliance library · 0 docs Error - Pricing & contracts · Not connected Disconnected ![](/assets/einstein-hats-paper.svg) ## Meet your customers, already known. One agent across all four moments, with full memory and full context. No cold opens. [Book a pilot→](/en/contact-us/)[Read the Analyze phase](/en/engine/analyze/)