Skip to main content

What is a wizard?

Understand what wizards are, how they take real action inside your product, and when to use one instead of static guidance or a chatbot.

Written by David Carbajal

Candu Actions is currently available to select customers. If you're interested in wizards for your team, contact us.

A wizard is a multi-step AI workflow inside your product that asks the user for what it needs, takes real actions on their behalf, and confirms before anything risky. It's how a customer creates an invoice, troubleshoots a broken setup, or completes onboarding β€” without leaving your app.

New to Candu Actions? Wizards are part of Candu Actions, a new capability that runs alongside the Candu tools you already use for content, onboarding, and segmentation. Your existing content keeps working. Wizards add the ability for an AI to actually take action in your product, not just guide users to it.

Wizards vs. what you've tried before

Wizards sit between two things you've probably already considered:

  • A static walkthrough or product tour. Useful for showing where things are, but can't actually do anything for the user.

  • An open-ended chatbot. Can answer questions, but doesn't know when it's done and can't safely take action in your product.

A wizard combines the strengths of both. It has the structure of a guided flow and the intelligence of an AI assistant, plus the ability to actually run API calls in your product on the user's behalf.

A wizard combines the strengths of both. It has the structure of a guided flow and the intelligence of an AI assistant, plus the ability to actually run API calls in your product on the user's behalf.

How a wizard runs

Every wizard has steps. At each step, the wizard asks a focused question, gives the AI a clear instruction for what to do, exposes only a relevant subset of actions the AI can call, and advances when the goal of the step is met.

For example, a "create a segment" wizard might have two steps:

  1. Resolve the criteria. The AI looks up real user traits in your product, asks the user to confirm the criteria, then creates the segment.

  2. Test the segment. The AI asks the user for an email or ID, checks segment membership, and reports back.

The user sees a clean conversation. Behind the scenes, the wizard is making API calls to your product β€” but only the ones you've authorized, with the right confirmations, and with a full audit trail.

Governance: nothing happens without your permission

Wizards never invent actions. They can only call the API endpoints you've registered with Candu Actions. Writes β€” creating, modifying, or deleting data β€” can be set to require user confirmation before firing, so the user sees the full payload before anything changes in your product.

When to use a wizard

Wizards work best for tasks that:

  • Have multiple steps where context carries forward

  • Benefit from real-time lookups against your data

  • Should result in something happening in your product, not just an answer

Good fits: create a segment, send an invoice, configure an onboarding flow, troubleshoot why content isn't showing, complete a setup step.

Not a good fit: open-ended Q&A, single-click navigation, anything that doesn't have a clear "done" state.

Next

Ready to build one? Read Build your first wizard for a walkthrough of planning, configuring, and publishing your first wizard.

Did this answer your question?