Create and Activate a Script

Summary

This guide walks through the full creation flow so a new script can be deployed without breaking existing monetization paths. 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

• Launch new campaign scripts safely.
• Prevent empty or broken scripts from going live.
• Standardize script onboarding.

Before you start

• Prepare script title and flow intent.
• Ensure required assets exist in Gallery.
• Pick low-risk window for first activation.

Step-by-step workflow

1. Open /dashboard/scripts.
2. Select bot and mode.
3. Enter script title and create script.
4. Add at least one complete step sequence.
5. Validate step content and pricing.
6. Set script active and monitor inbox behavior.

Key states and error handling

• Validation: 'Enter a title' when title is missing.
• Creation success should be followed by immediate step configuration.
• Active toggle before step validation increases risk.

Best practices

• Use deterministic titles (objective + audience).
• Keep first version short and testable.
• Activate only one new script at a time.

Troubleshooting

• If create fails, retry with simple title and stable network.
• If active script behaves oddly, deactivate and retest offline.
• If script is missing after create, refresh query state and verify mode.
• 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.