Define a shared process once. An Operation applies it across your client book, with a Mission for each client outcome. Keep the CRM and specialist tools you use; InVice coordinates the work between them. Your team sees progress, ownership and exceptions together.
InViceInteractive example · fictional workspaceFollowing up on the photo ID. The intake meeting is already on the calendar.
The appointment is booked within the scheduling rules. InVice is preparing the file for the meeting.
The requested extension crosses the deadline you set. Review the proposed date before InVice updates the file.
Select a client to see their context and next step.
A mission ends. An operation does not. It is the standing responsibility for a category of work for as long as you run that work: a client book, a pipeline, a renewal calendar. The operation persists; the AI agent working inside it, and the model beneath it, can change. It handles the operational work, so only the decisions that need you reach you. A system of action over the systems of record you already keep.
Each client in the operation gets a dedicated mission. They share the operation’s rules, vault scope, and memory, and differ in the file they own. When one needs to coordinate a resource, it spawns a sub-mission of its own. You see the parent; the system runs the rest.
The trigger is usually an inbound: a client emails or submits a form, or arrives through a CSV or a CRM webhook. On each one, the operation spawns a mission for that client automatically, applies the playbook, and begins. You do not configure twice.
What worked on one file informs the next. What broke on file 12 becomes a rule for file 200. The operation’s memory is your firm’s memory: discoverable, exportable, yours.
An operation sits at the top, watching every inbound. Each one becomes a mission that handles a single client, and a mission spawns a sub-mission when it needs to coordinate a resource. A mission can also start on its own, straight from you.
InViceInteractive example · fictional workspace
9:24 · Bank statement receivedSaved to the client file · Bank statement.pdf
Photo ID is the remaining document for this step.
Reply sent to LucaThanks, Luca. Your bank statement is on file. Please upload your photo ID through your document link. We are set for Thursday at 2 pm.
InVice is watching for the photo ID and will follow up on your schedule.
One Operation keeps mortgage files moving across your client book. Each Mission tracks its documents and deadlines; the broker reviews decisions that need judgment.