Dashboard Stars Pulse Chart

Summary

The Stars Pulse chart is the fastest way to detect momentum changes. This guide explains how to read trend quality and when to escalate. 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

• Identify growth, decay, and volatility patterns.
• Separate one-off spikes from stable performance changes.
• Spot dead zones requiring operational checks.

Before you start

• Set a period long enough to include multiple activity cycles.
• Know recent campaigns, script changes, or bot updates in that window.
• Prepare one follow-up check in Fan Inbox or Scripts if anomalies appear.

Step-by-step workflow

1. Open /dashboard and scroll to Telegram Stars Pulse.
2. Read total period value in the chart header.
3. Observe line shape: stable, staircase, spike, or flatline.
4. Correlate major points with recent operational changes.
5. Open recent sales panel to validate monetization recency.
6. Escalate to script or inbox audit if pattern is abnormal.

Key states and error handling

• Sharp isolated peaks often represent campaign or high-ticket events.
• Flat chart with normal conversations can indicate pricing/script issues.
• Frequent sawtooth patterns may indicate unstable conversion cadence.

Best practices

• Annotate timeline events (launches, plan changes, outages).
• Use same zoom window when comparing weeks.
• Combine chart interpretation with KPI card context before deciding.

Troubleshooting

• If chart is blank, verify date window includes activity.
• If chart conflicts with sales memory, check recent sales list and filters.
• If trend collapses after script edits, rollback last script priority change first.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Date range picker controls all KPI cards, the pulse chart, and recent sales together.
• Bot scope selector switches from aggregated view (All bots) to single-bot diagnostics.
• Stars Earnings card displays stars and an approximate USD conversion in the selected range.
• Avg Stars / Sale is a per-transaction quality metric, not a traffic metric.
• Chat Conversion is shown as AI replies vs sales ratio and must be read with volume context.
• AI Conversations card uses a rolling window, so it can move independently from revenue cards.
• Telegram Stars Pulse chart reflects timeline dynamics and should be read before tactical changes.
• Recent Stars Sales panel is your recency heartbeat for monetization continuity.

Operator checklist (before shipping changes)

• Confirm date range and bot scope are documented before sharing conclusions.
• Cross-check KPI movement with chart shape and recent sales recency.
• Avoid changing scripts or pricing from one isolated spike.
• Capture a screenshot with visible filters for auditability.
• Validate one downstream signal in Fan Inbox before closing analysis.
• If data is ambiguous, widen period before escalating operational changes.

Real-world scenario

A team sees Stars drop in 24h. They verify date and bot scope, then confirm whether recent sales are truly stale or only filtered out. They compare conversion and AI conversation volume before deciding if the issue is traffic, script quality, or offer pricing.

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.