Control surfaces

How you steer Vruum — the three approval queues, the match gate, and the eight-stage account lifecycle.

These are the levers between "the AI drafted something" and "it actually happened." They keep you in control while the motions run.

Web observes, agent acts

The web app is the read-only side of the split. Today (/today, the post-login landing) and the activity pages (/activity/outreach, /activity/deals, /activity/accounts, /activity/people, /activity/engagement) show what the motions are doing: queue counts, replies, deals, tasks, pipeline. Each card carries a copyable nudge prompt that hands the action to your agent. The levers below, and every other mutation, are pulled through your agent in the harness, never in the browser.

The three approval queues

Nothing AI-drafted leaves your account without your sign-off. There are three approval queues, one per drafting motion. Ask your agent to clear a queue, or have it read the queue directly:

Queue	Holds	Read with
Outreach	Drafted prospect messages	`get_outreach_review`
Engagement	Drafted LinkedIn reactions / comments	`get_engagement_review`
Content	Drafted demand-gen posts	`get_content_review`

The deals review is a triage read, not an approval gate — deals don't wait on approval the way drafts do.

The match gate

When prospects are imported into a campaign, a backend quality gate decides who actually enrolls: a match score of 70 or higher. Harness-side pre-filters narrow the candidate list first (cheaply, before research spend), but the backend gate is authoritative — it's what keeps a raw import from polluting a campaign. See Fill the pipeline.

Account lifecycle

Every account sits on one of eight stages. The stage determines which motion applies:

prospect → engaged → committed → onboarded → adopting → expansion_ready
                                                  (plus: dormant, churned)

Stage	Meaning
`prospect`	Not yet engaged. The default for new accounts.
`engaged`	Active conversation or open deal. Pre-commitment.
`committed`	Contract signed; first value event pending.
`onboarded`	First value delivered.
`adopting`	Recurring value; steady-state customer.
`expansion_ready`	Healthy plus an expansion signal (new buyer, dept, usage).
`dormant`	60+ days without a value event; health declining.
`churned`	Ended without renewal; eligible for win-back.

Early stages are outreach territory; expansion_ready triggers the expansion play and churned (with a recoverable loss reason) triggers win-back — both covered in Diagnose and expand. Tell your agent to move an account once the signal is real, or set the stage with manage_account.

With the model in hand, head to Workflows for the end-to-end recipes.