Skip to main content
A Plan is a set of steps you define once in the Agent Management Studio. When a user’s request matches the plan, your agent works through those steps in order, gathering what it needs and confirming as it goes. You get the same process every time, delivered in natural conversation. For the case on why you’d use Plans at all, see Why Plans.

What a Plan is

You build a Plan in the plan editor: give it a name, a description, and an ordered list of steps. Each step is a plain-language instruction the agent carries out, such as “confirm the customer’s details” or “draft the welcome message.” Once you publish a Plan, your agent can use it. A published Plan becomes one of the tools in your agent’s toolkit, sitting alongside its knowledge and other tools. The agent doesn’t see a Plan as a special case. It treats it like any other capability it can choose to use.

How the agent knows when to run a Plan

The agent matches the user’s request against each Plan’s description, the same way it decides which tool to reach for. If the description fits what the user is asking, the agent runs that Plan. This means the description does the work: a clear, specific description gives you reliable matching, while a vague one makes triggering unpredictable. You can also surface a Plan directly. Mark it to show as a welcome card at the start of a conversation, or let users pick it from the prompt menu.

Strict step order or flexible

You choose how closely the agent sticks to the steps, using the Strict step order setting on the Plan.
  • Strict step order on. The agent follows every step in order and doesn’t skip any. Use this when the process has to run the same way every time.
  • Strict step order off (flexible). The agent may skip a step when the information it needs was already covered earlier in the conversation, so it doesn’t ask the user to repeat themselves. Use this when some steps won’t always apply.

What your users see

Users can follow a Plan as it runs. As the agent works through the steps, a progress panel shows each step by name and ticks it off as it’s completed, so the user can follow along. On narrow screens the panel appears as a collapsible progress summary under the agent’s reply. When the Plan finishes, the progress display clears and the conversation carries on as normal.

Give a Plan extra knowledge with Skills

You can attach Skills to a Plan. A Skill is a reusable unit of knowledge, such as a framework, set of guidelines, or reference material, that the agent can draw on while it works through the Plan. The steps tell the agent what to do; the Skills give it the background to do each one well. Skills attach to a Plan as a whole. See the Skills overview for more.

Current limitations

  • Skills attach to a Plan as a whole, not to individual steps.
  • You can attach up to 20 Plans to an agent, and up to 20 Skills to a Plan.
Coming soon: tool-aware plans. App admins will be able to assign specific tools to individual plan steps, so a Plan can take actions at the steps where you want it to. Tools are assigned to a step explicitly, rather than the Plan drawing on whatever tools the agent happens to have.

Getting started

Plans are configured in the Agent Management Studio. To build your first one, follow Create a Plan.
Before you start
  • An agent set up in the Agent Management Studio.
  • Any Skills you want the agent to draw on while the Plan runs (optional).
Plans are rolling out gradually. If you don’t see Plans in your Agent Management Studio yet, talk to your Mindset AI contact.