Objects
The things Vruum tracks — people, accounts, deals, campaigns, outreach plans, touches, and the knowledge base.
These are the nouns the rest of the system operates on. You inspect and change them by asking your agent in plain language; under the hood it calls the MCP tools named here. (Tool names are examples — confirm the live set from your harness.)
Person
An individual contact — a prospect, a buyer, or a deal stakeholder. The person is
the unit of outreach: research, messages, and replies all attach here. Ask your
agent about someone, or have it pull the full picture with get_person_360
(profile, activity, research, plan state) in one call.
Account
The company a person belongs to. Accounts carry an account stage (see
Control surfaces) and are where company-level
decisions — expansion, win-back, owner assignment — are made. Read and update an
account with manage_account.
Deal
An opportunity tied to a person and account. A deal moves through pipeline stages
(new → … → negotiation → won / lost), and carries an estimated value,
stakeholders, and a next step. Ask for the full context with get_deal_360;
change it with manage_deal.
Deals are never hard-deleted — they retire to won/lost and revive via reopen, so the history stays intact.
Campaign
A targeted cohort of people plus its messaging plan — the unit you fill with
prospects and run outreach into. (Earlier builds called this a "segment".) List
campaigns with search type="campaigns" and read one with
fetch type="campaign".
Outreach plan
The per-person multi-touch sequence, enrolled under a campaign. A plan fires
due touches on schedule and watches for replies, pausing automatically when a
prospect responds. manage_outreach starts, pauses, and resumes it.
Touch
One action inside a plan: a specific message, on a specific channel (email or LinkedIn), at a specific time. Touches are what the outreach queue holds for your approval before they send.
Knowledge base
Your uploaded collateral plus connected sources (Google Drive, Notion, …), turned
into retrievable grounding context for the agent. Research-grounded messages draw
on it; manage_kb adds and searches it.
Next: Motions — what Vruum does with these objects.
Prefer the terminal? Every object is also reachable from the CLI reference for local setup, CI, and recovery.