A Mission keeps one client outcome moving across people, documents and connected tools. You provide the goal, context and limits. InVice acts within the authority you enable, records what happened, and asks when a decision needs 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.
Every mission is one of four moves. Name the one you need and brief it in a sentence, and the agent builds the rest over the tools you have connected. It can stand on its own, or an operation can launch one for every client in your book.
Point it at a signal: a rate decision, a filing, an account going quiet. It watches in the background and sends a plain summary the moment something changes, as your cue to act.
Ask it to look across your contacts and your connected tools at once. Every lead idle past 40 days, with a summary of your last exchange and a ranked re-opener for each.
Hand it a job that needs someone else. It reaches a vendor, requests quotes and availability, books the visit, and confirms the timing back with your client.
Give it a date or a promise that must not slip. It keeps the standing reminder, nudges you before it passes, and drafts the follow-up so it is ready to send.
A goal, written in plain language. Include the constraints, the budget, the deadline, the parties to contact. No prompt-writing, no setup. The agent builds the steps across whatever you have connected: email, calendar, vault, docs. If you can brief a person, you can deploy a mission.
The agent retrieves the specific facts it needs from your encrypted documents. Your real rates, your real client list, your last six negotiations. Every figure it cites is one you can point to.
Per-mission permissions. What documents can be shared. What information can be revealed. When to ask, when to act, when to escalate. The triggers that pause the mission until you decide.
Outbound email from your address. Replies parsed and routed. Documents collected, fields extracted, statuses tracked. It reads public web pages when there is no API, and interactive computer use is on the roadmap. All audited, all attributable.
Genuine ambiguity. A risk that crosses your threshold. A decision the rules cannot make. The agent acts only when the dates and logic are unambiguous and routes the judgment calls back to you. Otherwise it works in the background and tells you only what is done.
When the outcome is reached, the Mission records the result and leaves its documents and action history available. Useful instructions remain in the knowledge and retention scope you control.
A mission is the unit. An operation is the pipeline. When you have a large book of clients to manage at once: one operation, one sub-mission per file, one professional approving the decisions that count.