The engine your team runs on.

UNLESS Engine is the platform side of Unless. It is the system the Customer Agent and the Team Assistant run on: three senses that ground the agent and four phases that close the loop. The Engine is what makes the agent learn on a loop instead of just answering one question at a time.

Living Knowledge, Living Memory, and Living Context. Living Knowledge is what the agent knows about your business - your tickets, docs, Slack, Confluence, Drive, recordings, all pulled into one non-ambiguous library. Living Memory is who the agent is talking to: preferences, history, sentiment, goals. Living Context is where the agent is acting: CRM, billing, ERP, support tools, custom APIs.

Train, Test, Deploy, Analyze. Train turns your content into Living Knowledge and Living Context. Test previews every role and simulates every skill before a customer sees it. Deploy puts the agent in front of customers across all four moments. Analyze closes the loop with performance, business value, and AI maturity, then feeds Train.

Train builds Living Knowledge and Living Context from the sources you already have. Help center articles, ticket logs, product docs, Slack channels, recordings, CRM fields - all of it pulled into one library the agent can read without ambiguity. You stop maintaining duplicate content ops; the system maintains itself.

Test lets you preview every role, simulate every skill, and audit every decision before a customer or auditor ever sees it. Run a control set of questions, replay real conversations, and read the audit trail in plain language. Your DPO and your auditor see the same thing you do.

Deploy puts one agent in front of customers across all four moments. The agent carries Living Memory and Living Context from one moment to the next, so a visitor who became a customer never has to introduce themselves again. No cold opens, no four separate bots.

Analyze shows performance, business value, and AI maturity in one view. You can see deflection, resolution time, CSAT, and revenue impact by moment, by topic, and by segment. The same dashboard tells your CFO and your DPO what they each need to hear, with the numbers backed by the audit trail.

The Team Assistant is the team-facing side of the agent. It works inside the helpdesk your team already uses, drafts replies, summarizes accounts, and surfaces the next-best action. Every accepted draft, edit, and override feeds Living Knowledge back, so the loop tightens with every ticket.

Living Knowledge maintains itself. It re-reads the sources you connected, picks up new tickets and conversations as your team handles them, and rewrites or restructures content when the underlying truth changes. Documentation ops drop to near-zero. Nobody is paid to keep a wiki tidy anymore.

Unless runs a constellation of models from providers like Mistral, OpenAI, Google, and Anthropic, rather than betting the platform on one. The constellation lets us pick the right model for the job and switch quickly if regulation or vendor terms change. Customer data is never used to train public models.