LeenOpsDocs
Platform

Assistants

Understand the live assistant inventory, capabilities, and why the total changes by workspace.

Assistants is the current console name for your digital team. Voice, phone, schedules, tools, and workflows are capabilities attached to an assistant—not separate people you have to locate elsewhere.

How many assistants are there?

There is no single customer-facing number that is correct for every workspace.

  • Your workspace total is the number shown in the live inventory at Assistants (/assistants).
  • The inventory is assembled from the assistants and products available to the active workspace.
  • Entitlements, enabled specialist teams, workspace configuration, and future product releases can change the total.
  • The backend also contains a larger internal registry of specialized agent implementations. That registry is not the same as the assistants assigned to your workspace and should not be used as your account total.

Use the console as the source of truth

Open Assistants and count or filter the visible inventory. Documentation deliberately does not publish a fixed catalog total because it would become stale and could expose assistants that are not available to your workspace.

Find your live inventory

  1. Open the LeenOps console.
  2. Select Assistants in the main navigation.
  3. Use capability filters to narrow the list, including voice-ready assistants.
  4. Open an assistant to review its overview and readiness.

Assistant detail areas

Each assistant can expose the following areas:

AreaWhat it answers
OverviewWhat is this assistant for and is it ready?
ActivityWhat has it done recently?
BehaviorWhich mission, instructions, and operating rules apply?
KnowledgeWhich sources ground its answers?
ToolsWhich systems can it read or change?
ChannelsWhere can people interact with it?
TestDoes the current configuration produce the expected result?
SettingsWho owns it and which advanced controls apply?

Before the first live run

  1. Confirm the mission is narrow and measurable.
  2. Attach the minimum knowledge and tools required.
  3. Document actions that need human approval.
  4. Run a controlled test with non-sensitive data.
  5. Review activity and output quality.
  6. Add a channel or schedule only after the test passes.

Legacy “Agents” references

Older URLs and documentation may use Agents. In the current console, start from Assistants. Internal services may still use agent in API names and database fields; that technical vocabulary does not change the customer navigation.