Skip to main content
Wizards and all four placement modes are implemented in the current product build. A wizard must be published before Production can resolve it.

​
One assistant, one placement

A wizard combines customer-facing copy, instructions, capabilities, knowledge scope, model settings, and one placement. Duplicate the wizard when the same behavior needs a different placement or targeting rule.
A current Dubot wizard rendered as a bubble

The Bubble placement gives customers a focused assistant without taking over the page.

This demonstrates the implemented bubble and conversation states. Published copy, colors, capabilities, and page context determine the customer experience.

​
Configure the behavior

The wizard editor covers:
  • a required contextual instruction for the assistant;
  • model and reasoning settings;
  • a goal description and optional opening message;
  • launcher label, input placeholder, and quick prompts;
  • file-upload availability;
  • attached capabilities;
  • direct knowledge scope;
  • one placement and its page rules.
Capabilities are reusable. Put cross-wizard security, brand voice, product-domain context, or skills there rather than copying the same instruction into every wizard.

​
Choose a placement

Page rules can include or exclude exact paths or path prefixes. Placement matching runs against the current page, including client-side navigation.

​
Make tools available

A wizard can use actions only through its attached Skill capabilities. At runtime, Dubot narrows that published list again:
  • Session API actions must be published and enabled.
  • Client-side callbacks must also be registered by the host application for the current page.
  • Confirm-gated actions pause before execution.
  • Unpublished references are omitted from the Production runtime.

​
Test and publish

1

Save the draft

The latest saved version is available to Test.
2

Check dependencies

Review capabilities, actions, knowledge, placement targeting, and brand settings.
3

Run a test conversation

Exercise expected requests, unavailable tools, confirmation, errors, and completion.
4

Publish

Publishing makes the selected version eligible for Production. Saving alone does not.
5

Inspect Activity

Review conversations and related Guidance or action outcomes before widening exposure.
Follow Build and publish a Wizard for the dashboard workflow. See SDK surfaces for programmatic rendering and Publishing for the lifecycle rules.