Scenario Templates

TL;DR:

• Scenario templates are reusable starter flows you can preview and install into a bot.
• Installing a template creates a new scenario draft and materializes any required resources.
• Always review the generated command, assets, integrations, and AI settings before publishing.

Who this is for

• Builders who want to start from a proven flow instead of a blank canvas.
• Teams standardizing repeatable bot patterns across multiple bots.
• Workspace admins preparing templates that depend on shared fields, tags, assets, AI presets, or integrations.

What you will learn

• What the template gallery includes.
• What happens during preview and install.
• Which parts you should customize before publishing the generated scenario.

Overview

A Scenario Template is a reusable starter package for the scenario editor. Instead of manually building every node, link, and dependency from scratch, you install a template into a bot and then adapt the generated draft to your exact use case.

Templates can carry more than nodes alone. They may also define supporting resources such as fields, tags, globals, assets, AI presets, and external integration placeholders.

Key concepts

• Gallery - The list of enabled templates available to normal workspace users.
• Preview - A read-only view of the template flow and dependency summary before install.
• Install report - The preflight and post-install summary of resources the platform creates, copies, reuses, or leaves as placeholders.
• Feature requirements - Plan-dependent capabilities a template may require before it can be installed.

How it works

1. Open the template gallery and filter or search for a suitable template.
2. Open a template to preview the flow, tags, fields, globals, assets, AI presets, and integration dependencies.
3. Click Install to bot, choose the target bot, and set the new scenario name and command.
4. Review the generated scenario draft, replace placeholders, and publish only after the flow matches your bot.

TIP

Treat templates as accelerators, not final production content. They should reduce setup time, not remove the need for review.

WARNING

Installing a template and publishing immediately without checking command names, integrations, or placeholder assets is a common pitfall.

In the UI

The template workflow is built around a gallery view, a detail preview, and an install modal.

• Location: Templates or Scenario Templates library in the app.
• Main controls:
  • Search and category filters - Narrow the gallery to a use case.
  • Pre-Install Preview - Review the flow and dependency summary.
  • Install to bot - Choose the target bot and create a scenario from the template.
  • Name / Command / In menu - Set the initial scenario identity during install.

What gets installed

Depending on the template, the installer may create, copy, reuse, restore, or leave placeholders for:

• Tags
• Fields
• Globals
• Assets
• AI presets
• Integrations

The installer also runs feature and quality checks before creating the scenario draft. If the template requires plan features that are currently locked, install is blocked until the workspace has access.

Public vs internal templates

Normal builders work with enabled templates from the public gallery. Internal or work-in-progress templates may still exist for admins, but those are not the standard end-user entry point.

Permissions

According to the current workspace permissions model:

• Owners, admins, and editors can view the template library.
• Owners, admins, and editors can apply templates.
• Viewers can browse the library, but they do not apply templates.

What to customize after install

Before you publish the new scenario, review:

1. The scenario name and command.
2. Placeholder messages, media, and buttons.
3. Any created or reused fields, globals, and tags.
4. AI presets, prompt instructions, and memory settings.
5. Integration endpoints, recipient emails, or webhook URLs.

If the install report includes manual tasks or notes, finish those first so the generated draft behaves as expected.

Examples

Example 1 - Launch a lead capture bot faster

Goal: Create a new Telegram funnel without drawing every node from scratch.
Setup: Install a lead-generation template, set the command and scenario name, then replace placeholder copy with your own offer.
Result: The team starts from a working draft and spends time on customization instead of boilerplate setup.

Example 2 - Reuse a proven AI support flow

Goal: Roll out a similar AI-assisted support scenario for another bot in the workspace.
Setup: Install an AI template, review its AI preset and integration dependencies, then update the knowledge base and answers for the new bot.
Result: The new scenario reaches a usable state much faster and stays closer to the original standard.

Troubleshooting

Symptom: Install is blocked before the scenario is created

Cause: The template requires locked plan features or has unresolved dependency issues.
Fix: Review the pre-install report, unlock the required features, or choose a simpler template.
Prevention: Check feature requirements before promising a template to the team.

Symptom: The generated scenario works partially

Cause: The template created placeholders or manual follow-up tasks that were not finished yet.
Fix: Review the install report, replace placeholders, and complete any listed manual tasks before publishing.
Prevention: Always treat template install as the beginning of setup, not the last step.

Symptom: The scenario command is wrong after install

Cause: The install modal generated a starting command, but it still needs project-specific naming.
Fix: Rename the command in the generated scenario before publishing.
Prevention: Set a clear scenario name and command during install and double-check them in the editor.

FAQ

• Q: Does installing a template overwrite my existing scenarios?
  A: No. Installing a template creates a new scenario draft for the selected bot.

• Q: Can templates include AI presets and integrations?
  A: Yes. Templates may carry dependencies for AI presets, integrations, assets, fields, tags, and globals.

• Q: Can I publish immediately after install?
  A: You can, but it is safer to review the generated draft, install report, and any placeholders first.

Related pages

• Scenarios Overview
• Assets
• Roles & Permissions