Scripts Overview (Modes and Priority)

Summary

Scripts run per bot and mode. Priority and active state decide which script path is used first in monetization conversations. 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

• Select correct script mode for objective.
• Control execution order with priorities.
• Avoid mode mismatches.

Before you start

• Confirm bot selection.
• Know whether you are selling media or links.
• Prepare fallback script if changing priority in production.

Step-by-step workflow

1. Open /dashboard/scripts.
2. Select bot and script mode.
3. Review existing scripts and active statuses.
4. Adjust priority ordering carefully.
5. Activate only validated scripts.
6. Re-check execution in Fan Inbox.

Key states and error handling

• Changing mode resets visible script context.
• Only active scripts can drive live behavior.
• Priority conflicts can create unexpected execution ordering.

Best practices

• Keep naming explicit by offer type.
• Review priority after every major script addition.
• Avoid simultaneous priority edits by multiple operators.

Troubleshooting

• If wrong script fires, inspect active mode first.
• If ordering is unexpected, re-check priority values.
• If no script appears, verify selected bot and 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.