Build Steps (Free and Paid)

Summary

Step quality determines conversion flow quality. This article explains how to structure steps that are clear, monetizable, and stable. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Build coherent conversation progression.
• Use free and paid steps intentionally.
• Map media assets correctly.

Before you start

• Prepare each step objective.
• Select media assets in Gallery first.
• Define one pricing strategy before writing text.

Step-by-step workflow

1. Open target script.
2. Create free introductory steps first.
3. Add paid step with stars price.
4. Set ai_step_context for response guidance.
5. Attach correct media asset id.
6. Save and test full flow in real thread.

Key states and error handling

• Step mutations can fail with generic fallback errors.
• Missing media mapping can break paid delivery flow.
• Overly long or vague context reduces conversion consistency.

Best practices

• Use concise hardcoded text with one call-to-action.
• Keep AI context explicit about negotiation intent.
• Validate every paid step with a live dry run.

Troubleshooting

• If step save fails, check required fields and media id.
• If paid offer does not trigger, verify step type is paid and active script state.
• If copy feels inconsistent, simplify ai_step_context and retry.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Scripts are scoped by selected bot and selected mode (paid media or sell link).
• Script active state controls whether it can drive live offer behavior.
• Priority ordering changes execution order and can alter conversion outcomes immediately.
• Step type (free vs paid) determines monetization behavior in the flow.
• Paid steps rely on stars price and optional minimum boundaries.
• ai_step_context influences generated transition quality and negotiation framing.
• media_asset_id mapping is required for robust paid-media delivery paths.
• Mutation toasts are primary indicators for create/update/delete failures.

Operator checklist (before shipping changes)

• Confirm bot and mode before creating or editing scripts.
• Build complete steps before activating new scripts in production.
• Test one changed script at a time in live conversations.
• Use conservative pricing increments and track each revision.
• Re-check priority after adding or deleting scripts.
• Keep fallback script ready before major rewrites.

Real-world scenario

A new paid script underperforms after launch. The operator verifies mode selection, checks step mapping and media ids, rolls back the latest pricing jump, and restores stable conversion before retesting incremental changes.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.