A command palette, not a chatbot.
It sits over whatever screen you are on, so the question you ask means the thing in front of you.
Operator reads the current page’s context, so "follow up with everyone who went cold this week" means the right people on the screen in front of you, not a generic query.
Operator generates a multi-step plan and tells you the reasoning behind it before anything happens.
Execution waits for your approval where policy requires it. It remembers the thread across sessions, and it can reverse the last action.
Every competitor sells agents that do work. None sell a way to ask the whole system a question.
⌘J opens "What do you need?" without leaving the page you are on. Ask, act, or search in place.
Not a canned response. It queries your actual pipeline and tells you what it found.
It dispatches your Agents, reads Intelligence signals, and moves work through the Workflow Engine.
Real commands, not demo theatre.
Each of these maps to a shipped capability, and each one lands in the audit log.
Operator drives the rest of the platform. It dispatches your Agents, reads Revenue Intelligence signals, and moves work through the Workflow Engine.
Operator acts inside the same controls as everything else. It proposes, you approve where policy requires it, and every step it takes lands in the audit log.