Scripts Pricing (Stars and Minimums)

Summary

Pricing fields drive monetization behavior directly. This guide covers safe tuning strategy for stars_price and minimum constraints. 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

• Tune revenue without collapsing conversion.
• Use minimums as guardrails.
• Avoid abrupt pricing swings.

Before you start

• Know baseline conversion and average order value.
• Segment high-intent vs low-intent conversation patterns.
• Coordinate price changes with dashboard monitoring windows.

Step-by-step workflow

1. Open script paid steps.
2. Set initial stars_price conservatively.
3. If needed, set min_price_stars boundary.
4. Save step updates.
5. Observe conversion in dashboard and inbox.
6. Iterate in small increments only.

Key states and error handling

• High price jumps can reduce conversion quickly.
• No minimum can increase discount variability depending on flow.
• Low volume windows can distort pricing conclusions.

Best practices

• Change one pricing variable at a time.
• Wait for sufficient sample size before next adjustment.
• Track each price revision with timestamp.

Troubleshooting

• If conversions collapse, rollback latest pricing change.
• If revenue stays flat with high traffic, test alternative paid step framing.
• If outcomes are noisy, widen monitoring period before deciding.
• 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.