Skip to content
GuideAgent setupIntermediate

Configuring your agents

The hub is one card per agent, and opening a card is not configuring it. What "configured" actually means, and the order that makes it go quickly.

RDRevTech DeliveryAgent delivery team 3 minUpdated

Product walkthrough

See it in RevTech

See the controls that define what each agent can do, the standards it must follow, and the usage RevOps can observe.

See the controls that define what each agent can do, the standards it must follow, and the usage RevOps can observe.
Part 1 of 4

One card per agent

AI Agents in the sidebar opens the hub: one card per agent available to you, each opening that agent's own page. The cards are RevPlays, AI Lead Management Agent, Campaigns, Sales Agent, AI Messaging and Analyst Agent, and Artifacts sits in the hub's header because every agent reads from it. The Analyst Agent page is where you choose which Analyst questions run on schedule.

The list only ever shows the agents your role can reach, so a card you expected and cannot see is an access question rather than a missing capability. An agent that is not available in your build yet keeps its card, marked Coming soon, rather than disappearing.

RevTech: The AI Agents workspace brings available agents and their configurations together.
The AI Agents workspace brings available agents and their configurations together. Captured from the current application with illustrative sample data. Screenshot of the RevTech application; sample data.
The AI Agents hub: one card per agent your role can reach, each opening that agent's own configuration page.
Part 2 of 4

Configured means work saved

An agent is configured when real work is saved on its page: a play, a lead flow, a campaign, a schedule for an analysis, an SLA rule, or a messaging sequence. Simply opening the page does not configure anything.

That is worth stating plainly because an agent with no rules, no plays and no flows has nothing to act on. It is not idle because it is broken; it is idle because nobody has told it what the business does. RevTech runs the agents, and your team decides what they work on. This page is where that decision is written down.

Part 3 of 4

Artifacts are the shared input

Every agent draws on the same governed artifacts — your ICP, product material, messaging context. That library is not per-agent, and it is not filled in for you. Whatever is in it is what all of them have to work from.

Which makes artifacts the highest-leverage thing on this page even though it is not one of the cards. An agent configured against a thin library produces thin output, and the instinct in that situation is to re-tune the agent, which is the wrong end of the problem.

Part 4 of 4

A workable order

A new workspace is set up through the setup rail: "Set up your account" first, then "Agent activation", then Get started. Your RevTech team works through it with you, and after that the hub is where configuration lives. You can configure the agents in any order, but some orders are less painful than others.

Get the artifact library to a usable state first, since everything reads from it. Then configure whichever agent supports the motion your team is already running: a lead flow if inbound is the priority, an SLA rule set in Sales Process if CRM hygiene is. Starting with the agent that supports a motion nobody runs yet produces a configuration nobody validates.

What to take away

  • Configured means real work saved — a play, a flow, a campaign, a scheduled analysis, an SLA rule, a sequence. Opening a page does not count.
  • The hub only shows agents your role has access to. A missing card is a permission, not a gap.
  • Agents work from the artifacts you maintain. An unconfigured artifact library caps what every agent can produce.
  • Start with the agent behind a motion your team already runs, so somebody validates what it does.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo