Agent and operator

Audienti is not just a sending tool and not just an analytics surface. It is an agent that co-works with an operator. The system finds, prepares, drafts, schedules, and keeps state. The operator reviews, approves, corrects, and engages the market where judgment matters.

The three operation types

  • Prospect operations: find and engage new prospects that fit the motion.
  • Visibility operations: join relevant market conversations, even outside the strict target ICP, to create awareness and near-term inbound motion.
  • Content operations: plan, draft, review, and promote recurring content that builds authority over time.

Every motion can lean harder toward one of those modes even if the system eventually supports more than one at once.

How the surfaces connect

Docs overview showing the public guides grouped by model, operation type, working surface, setup, and reference
Use the docs overview as the map. Public pages explain the model. Logged-in and admin guides explain the operating surfaces and setup controls.
  • Motions define the premise, owner, targeting, and channel path for the work.
  • Operator is where the human co-worker reviews work, clears blockers, and works live decisions.
  • Next actions explain why the system is recommending one move now instead of another.
  • Inbox takes over once a conversation is active.
  • Settings decide who owns the system, which senders are trusted, and whether automation is safe.

Operating rhythm

  1. Define one motion with a clear job.
  2. Let the system prepare work inside that boundary.
  3. Use Operator to review the highest-signal items first.
  4. Move live conversations into Inbox.
  5. Use dashboard and account maintenance to decide what to tighten next.

Common failure mode

The system gets noisy when setup is broad, ownership is vague, or the operator stops clearing truth. Start with one owner, one motion, one sender path, and one narrow workflow before expanding.

Agent contract

  • Use: explain the Audienti operating model and route users to the correct product surface.
  • Inputs: user question, current product area, operation type, motion context, operator role, and setup maturity.
  • Surfaces: Motions, Operator, Next Actions, Inbox, Settings, Dashboard, and the operation-type guides.
  • Verify: identify whether the question is about prospect operations, visibility operations, content operations, setup, or account maintenance.
  • Never: describe Audienti as only a sending tool, only a CRM, or only an analytics surface.