Dashboard Date Range and Bot Scope

Summary

Dashboard numbers are only meaningful when your date and bot scope are intentional. This guide shows safe filtering routines for reporting and diagnostics. 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

• Switch quickly between All bots and single bot diagnostics.
• Compare periods without accidental filter drift.
• Build repeatable reporting workflows.

Before you start

• Know whether you are doing incident debug or periodic reporting.
• Align timezone expectations with your organization operations.
• Capture baseline values before changing filters.

Step-by-step workflow

1. Open the calendar control in the dashboard header.
2. Pick from/to dates and confirm the label updates.
3. Select bot scope from the bot selector (All bots or one bot).
4. Read KPI and chart again after each filter change.
5. Record the chosen scope in your report notes.
6. Reset to All bots only after finishing single-bot diagnosis.

Key states and error handling

• Empty recent sales with broad date range may indicate inactivity, not UI failure.
• Single-bot mode can expose hidden underperformance masked in All bots.
• Filter switching changes every metric block simultaneously.

Best practices

• Use fixed weekly windows for recurring reports.
• When debugging incidents, isolate one bot first then widen scope.
• Share screenshots with visible date/bot selectors for team clarity.

Troubleshooting

• If data seems inconsistent, confirm selected bot still exists and is active.
• If chart appears empty, expand date range and verify traffic exists.
• If results differ between teammates, compare exact date labels and bot scope.
• 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.