Dashboard Recent Sales Validation

Summary

Recent sales is a fast recency check. It helps distinguish delayed reporting concerns from actual sales slowdowns. 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

• Confirm latest sales timing and continuity.
• Validate that dashboard totals are still receiving new events.
• Support quick incident triage during revenue alerts.

Before you start

• Set the same date/bot filters used for KPI analysis.
• Know expected transaction frequency for the selected bot.
• Avoid making config changes before checking recent sales recency.

Step-by-step workflow

1. Open /dashboard and locate Recent Stars Sales.
2. Read the newest entries and compare timestamps with current time.
3. Check amount patterns for abrupt size changes.
4. Compare with Stars Earnings and Avg Stars / Sale.
5. If no entries exist, inspect broader period and bot scope.
6. Escalate to Fan Inbox and Scripts if recency stalls unexpectedly.

Key states and error handling

• Panel may show no acquisitions when there are no events in current scope.
• Short windows can hide older valid sales.
• Large one-off sales can distort average if volume is low.

Best practices

• Use recent sales as a heartbeat indicator in daily checks.
• Pair recency checks with inbox traffic signals.
• Document outlier transactions before changing pricing logic.

Troubleshooting

• If panel is empty, widen time window before escalating.
• If entries are stale, verify bot is still receiving live traffic.
• If sales exist but KPIs lag, refresh page and re-check active filters.
• 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.