Sales value (last 12 months) and schedule status (next 30 days). Use case 2 & 3 readiness.
Schedule window: 2026-03-18 → 2026-04-17
Pod (BusinessPod) — use the chat button (bottom-right) for AI on this report. Rep scorecard → for per-rep metrics, shift compliance flags, and store-level drill-down for missed diary slots.
Populated by npm run repsly-run-top10-all (one POST per row: HTTP status + Repsly API Code). Ask Duncan to confirm tasks in Repsly.
New visit + order — no visit booked in the next 30 days Order on planned visit — rep already has a visit; we add the Order task
| Rank | Client | Sales value | What we do | Run status |
|---|
| Rank | Client | Sales value | Has schedule? |
|---|
Of the top 10 by sales value: if there’s no visit booked in the next 30 days, we book a new visit + Order. If a visit is already planned, we don’t add another — we put the Order on that existing visit.
Repsly schedules by rep and date. Compare with your Gmail Calendar in another tab; export to iCal could be added later to overlay. (Demo — static view for illustration.)
Each row is a schedule slot matched to a visit on the same client + calendar day. The effective date range is aligned with Repsly’s exported visits/forms (a blue banner appears when it differs from the default “last 30 days”). Run npm run repsly-advanced-report to refresh.
Counts forms submitted in the same effective window as the other blocks. If the window were only future dates, you’d see no rows — the report auto-aligns to exported data. Full Items live in tools/repsly-advanced-report.json.
dailyworkingtime (minutes summed in window) vs visit counts per rep. Visits/hour is touchpoints ÷ field hours when hours > 0.