An AI agent platform — companies use Leo AI to build agents that handle customer conversations across chat, voice and messaging, with human handoff when needed.
Each app targets a specific user and a specific moment in the AI-first support workflow.
Multi-tenant from above — sees every customer org, every agent fleet, all billing and all incidents in one place. A dense, professional internal tool optimised for fast scanning and drill-down.
Not a plain admin tool — an AI-native product. Building an agent should feel like describing what you want and having Copilot draft it. Three agents: Retail Support EU, Order Assistant, Returns Concierge.
Not a generic help desk. Every conversation here is a continuation of an AI conversation — the human agent arrives with full AI context, what the AI tried, why it escalated.
The only Leo AI surface the end consumer ever sees — and it wears the customer's brand, not Leo AI's. Northwind Retail's teal widget. Leo AI is invisible infrastructure.
--cs-brand* tokens drive the entire lookEvery agent on Leo AI has 12 layers. Layers 1–9 are configured by the customer in Studio. Layers 10–12 are operational systems.
v1 of each app builds against local mock fixtures — no backend required to start. Full backend stack is specified in each app's docs/ARCHITECTURE.md.