Every email the app sends on its own — what it looks like, what sets it off, and who receives it. The previews are built from the live templates, not screenshots, so they always match what actually goes out. Campaign emails you write and send yourself on the Emails page aren’t here.

Every line we run through CallRail, A–Z. Tap a number to copy it.

Every path a call or text can take — from the first ring to the column it lands in, and the reason why. Scroll inside the frame to explore; follow any one line from the top down to where it lands. This map is kept in step with the app's actual sorting rules.

The always-on wall dashboard (sidebar → Office Screen, or its own screen login) built to live fullscreen on a TV in the office. Everything on it sits still and just updates its numbers — the one moving piece is the bar along the bottom, which lights up for wins, alerts, and live activity so the room can glance up and know what's happening.

• Header — the GSDR Office wordmark, a live clock + date in the center, and the outside weather (with a short rain/heat heads-up when it's worth noting).
• Six KPI tiles — Calls today, Answer rate, Won today, Missed today, Leads to sort, and who's On dispatch. Answer rate is a gauge against an 80% goal and steps through four colours as it falls: green at or above goal, yellow just under, orange further down, red below 50%.
• Live map (left half) — your Houston service area with every truck shown as an arrow pointing the way it's heading, labeled with the driver's name. A strip across the top counts them up: moving / stopped / at yard / at landfill / idle. The map holds a steady view and only re-frames itself if a truck drives well outside the normal area.
• Right column — Follow-ups due, Callbacks needed (with the oldest-miss clock beneath it), and who's On dispatch plus who's On the clock right now, with photos and time-on-shift.
• Bottom bar — normally a running feed of the latest activity (newest on the left). This is the live zone; see below.

Under Callbacks needed, a big timer counts up from the moment the oldest un-returned missed call came in. It simply counts, with no overdue threshold, and disappears the instant that call is returned — a room-wide "call them back now."

Most of the time it's the activity feed. When something notable happens the whole bar turns into a headline for a moment, then goes back to the feed. If two things are true at once, this is the order of priority:

• Green — a win (about 22 seconds): Lead won today when a lead is moved to Won, or Online order when a new online booking lands. Same green flash, no name attached.
• Blue, steady (stays up while it's true): a nudge worth noticing — a truck sitting idle away from the yard for 2+ hours, or nobody set on dispatch. These only show during business hours (7am–6pm).
• Blue, brief (about 13 seconds): live activity as it happens — a new text comes in, a truck arrives at or leaves a place (geofence), or a call is coming in live.

Priority when more than one is true: a win takes over first; then any standing alerts share a single "Attention" band; then a brief activity flash; then the normal feed.

• The data refreshes every 10 seconds. The clock ticks every second, and the weather updates roughly every 10 minutes.
• If fresh data stops arriving (a network blip or a deploy), a "Reconnecting" pill appears and the numbers dim — so a frozen screen never shows stale info as if it were current. It clears itself the moment data comes back.
• When the TV wakes from sleep it snaps straight back to fresh data, and each panel only redraws when something actually changed — no flicker on a screen that's on 24/7.

Under the hood: public/js/screen.js?v=0.23.79 (the display) and routes/screen.js (the data feed, /api/screen/summary). Built across v0.9.18–0.9.76.

Two ways to see how well the AI sorts leads, both from the team's own moves on the Leads board. First, how often the office puts a lead somewhere other than where the AI suggested, month by month (moved here from Analytics). The rule gaps (cases where the AI read the call right but the rules still picked the wrong column) are listed in Settings → Data Cleanup.

Everything a driver does on their phone, on the left — joined by a line to exactly where it lands in the office, on the right. Blue boxes are their tabs, green boxes are office pages. The orange dashed lines are the things that feed their monthly bonus score, which their Bonus tab reads back but can never change.

Docket tells the app about new business by email, and each one lands on the Docket Alerts page with a push to your phone. Three kinds come through, on their own tabs:

Docket used to send these as texts to (713) 429-8973, which is why they were pulled out of the Texts tab. That was switched to email in September 2026 — the text carried a name and a phone number, the email carries the whole form. A small script on the office inbox passes each one to the app.

Everything the system records and analyzes for a single transcribed call — CallRail details, the AssemblyAI transcript, and the full Claude analysis. Filled with a realistic made-up example so you can see exactly what data is available to surface anywhere in the app.

What alerts exist and where each one shows up.

Phone numbers no Docket account has yet: wins, and callers who said they’re a client. Tap Link to tie each to its account (suggestions only appear with real proof), or dismiss it. An existing client stops counting as a new lead or win once linked.

Numbers a driver reported as spam. Listen if you need to, then mark Spam, Scammer, or Not spam.

Leads where the AI read the call right but the sorting rules still put it in the wrong column. Each one is a fix for me to make in the code; they clear on their own once it ships. Nothing for the office to do.