The Dispatch Desk

☆	Lane	Wave	Route	Name	Van	Park	Pkgs
☆	A1	10:20	CX101	M. Alvarez	RV-2184	C-14	187
	A1	10:20	CX102	J. Okafor	RV-2209	C-07	164
	A2	10:50	CX118	R. Nguyen	RV-2233	B-22	203
	B1	11:20	CX140	unassigned	—	—	152

Van	VIN	Status	Latest note	Charge
RV-2184	7PDSD…4192	Active	—	41%
RV-2209	7PDSD…4207	Active	Wiper blade	55%
RV-2251	7PDSD…4311	Grounded	DVIC — tire	—

Driver	Deliv.	Overall	DSB	CDF	POD	Belt
R. Nguyen	1,042	96	640	210	99.1%	0
J. Okafor	988	88	1,180	460	98.6%	0
D. Castillo	904	74	2,310	1,020	96.2%	2

Driver	Route	Van	Message	Status
M. Alvarez	CX101	RV-2184	Wave 10:20, van RV-2184, spot C-14	Sent
J. Okafor	CX102	RV-2209	Wave 10:20, van RV-2209, spot C-07	Sent
R. Nguyen	CX118	RV-2233	Wave 10:50, van RV-2233, spot B-22	Queued

Good morning

Operations Calendarⓘ

Fleet & People

The vans and the drivers — who and what is available to dispatch.

Performance

Amazon's scorecard and the coaching that follows from it.

Van Parkingⓘ

Auto-saved

Add a van not in the list:

Bulk Spot Update

↑ Upload .xlsx

or type below (one per line, format: EDV 1:150)

Scheduleⓘ

Driversⓘ

Auto-saved

Name (roster)ⓘ	Phoneⓘ	Preferred Nameⓘ	Preferred Van(s)ⓘ	Transporter IDⓘ	Emailⓘ

Scorecard

Coaching

Messagingⓘ

Message Templateⓘ

Preview

Length

Recipients

	Driver	Phone	Route	Van	Message	Status

Send

ℹ Texts send through your secure server function — no gateway password in the browser. Sending is enabled when you're signed in and the send function is reachable. If it isn't set up yet, use Copy or Export CSV.

Base delay between sends (ms, randomized ±40%):

Select a conversation on the left, or wait for a driver to text in. Incoming messages appear here live.

Southern Tire Mart is our mobile tire repair/replacement provider. Send them this info so they can dispatch a tech to the vehicle on site.

Van

VIN

Spot

Station location

Tire(s)

Front Driver Front Passenger Rear Driver Rear Passenger

Vehicle is currently out on the road (include current address)

Message Template

Tokens: {dsp} {vin} {tire} {spot} {location}
{address_line} adds a line with the current address when "out on the road" is checked, and stays blank otherwise.

Preview

Recipient

Generate DayList Upload today’s DSP-DayOfOpsPlan.xlsx (posted in Slack), plus an optional roster file — or use “⚡ Use Amazon Roster” below to pull it from Cortex instead.

Ops Plan *

📋

DSP-DayOfOpsPlan.xlsx

Roster (optional)

👥

Roster .xlsx or .csv

Fleet Log

Track vehicle issues, maintenance notes, and status for each van.

Auto-saved

	Van	VIN	Status	Charge	Latest Note	Last Updated	Notes

History

Delivery Notesⓘ

Auto-saved

Add / Update Note

Address *

Note Type

Route Code (optional)

Note *

DCR Exemption

Returns that count against Delivery Completion, from Amazon, with each package’s attempt time, business hours and addressⓘ

Week

Use an RTS Dashboard export instead

RTS Data File(s)

📂

Drop RTS file(s) here or click to browse

.xlsx, .xls or .csv — multiple files will be combined

Attempt time, business hours and address are joined from the saved day details by Tracking ID.

Payroll Complianceⓘ

Dispatch Desk Data

📅 Pay Period

Upload delivery data exportⓘ

📤

Drop scrape export here or click to browse

Accepts the amazon_*.csv from The Dispatch Desk or a .json export

Payroll Provider Data Upload the XLSX or CSV exported from your payroll provider (Paycom, ADP, etc.)

📂

Drop payroll file here or click to browse

Supports .xlsx, .xls, and .csv formats

Attendance

Occurrences in a rolling six-month window, per the attendance policy. This tracker records and surfaces standing — all disciplinary decisions remain at management's discretion.

OK 0–3 Coaching 4 Final coaching 7 Termination-eligible 10

Your Account

🙂 My Profile ›

Sets the name used in your Dashboard greeting (instead of your email handle). Only visible to you — everyone sets their own.

🔑 Change My Password ›

Organization

🏢 Organization ›

Your DSP and station details, and payroll defaults. These sync to your whole team.

DSP name / code

Matches the DSP column in the ops plan to pick your routes, and shows in the header.

Station code

Used in export filenames.

Standard clock-in time

Recommended time when a driver's In-Day punch is missing.

Salaried employees

Marked on the Drivers tab: 📅 under the name → Salaried. They're left out of Payroll Compliance and overtime.

Payroll system

Names it in Payroll and the Schedule, and which employee IDs are saved. Schedule import and the Paycom exports need Paycom for now.

Payroll rules

What Payroll Compliance measures against. Set these to your own pay policy.

Weekly overtime after (hrs) Daily overtime after (hrs, 0 = off) Workweek starts on Pay period A pay period starts on Payday, days after period ends Max days in a row (Schedule) Overtime "at risk" within (hrs) Unpaid lunch at 8+ hrs (min) Clock-in grace before app sign-in (min)

Approved overtime periods

When you offer 40+ hours (peak, for example). Overtime inside a period shows as approved, not flagged, on Payroll's Overtime card and the Schedule, up to the weekly cap (blank for none). Amazon's own limits (60 hrs in 7 days, 12-hr shifts) are still checked.

🗓️ Attendance Policy managers + admins ›

Thresholds, tiers and the rolling window used by the Attendance tab, and restated on the Coaching tab's Attendance framework. These sync to your whole team. Standing and flags stay advisory only — nothing here automates a disciplinary decision.

Policy name

Shown in the Attendance tab description.

Rolling window

Months.

Unexcused flag

Advisory at this many.

Tiers

Each tier starts at its occurrence threshold. A tier with a coaching level also drives a "… due" advisory flag. The 0 tier is the baseline and can't be removed.

👥 User Management admins only ›

Create and manage accounts for your team. Admins have full control; managers can use the app but can't manage users.

Add a user

The user gets a welcome email with a link to set their own password — there's no password to type here.

Current users

Loading…

Automated Posts

⏰ Post Times when the daily posts go out ›

These used to be set on each machine running the sync. They live here now, so there is one answer for the whole organization and a rebuilt machine cannot quietly revert to someone else's hours. A machine picks up a change the next time this site is open on it. The Morning Review time also drives its automatic email to every admin/manager — no machine needs to be on for that one.

Daily standup

Fleet status

Morning review

Timezone

An IANA name. The times above are read in this zone, so daylight saving is handled for you — a fixed offset would drift by an hour twice a year and the post would land at the wrong time with nothing in any log.

📣 Slack Posts run on demand ›

The three posts a scheduled machine sends each morning. Run one now and it posts immediately, with your own account doing the writing — no runner machine and no scheduled sync needed. The sync extension has to be installed in this browser.

Daily standup

Yesterday's numbers, today's fleet, and who needs a conversation.

Fleet status

Vans under 70% charge, and anything newly grounded.

Morning review

Yesterday's handoff, the fleet checks, and every CDF/DSB/Safety/Contact/DVIC occurrence by driver — not just the count, the exact kind. Emailed automatically each morning at the Post Times below (recipients set in Morning Review Recipients), and postable to Slack on demand here.

🖥️ Runner Machines admins only ›

A runner is a computer that stays on and does the routine work by itself: it syncs from Amazon Logistics and Rivian FleetOS every 30 minutes and sends the standup, fleet status and morning review at the Post Times above. To set one up, open this page on that computer, with the sync extension installed and signed in to Amazon Logistics (and Rivian FleetOS, if you run Rivian vans), and click Pair. No other account or password is needed. You don't need a runner at all if you're happy to sync and post by hand.

The sync extension is not detected on this page, so this computer can't be paired. Install it from the section below, then reload.

Loading…

📧 Morning Review Recipients who gets the emails ›

Who gets the Morning Review email — both the automatic morning send and "Email managers now" above — and the scorecard email when Amazon publishes a week. Leave this on the default and it goes to every admin/manager in your organization; nobody has to set this up for it to work.

Every admin/manager (default) Choose specific people

Email the scorecard when Amazon publishes a week
Once per week, to the same people. Turn off to stop it; turning it back on within 10 days of the week's end sends that week. Email the driver survey (Positive Environment) when Amazon updates it
Sent when the numbers change, at most once a day, to the same people.

Integrations

🔌 Integrations admins only ›

Credentials for Slack and SMS, stored for your whole organization. They are write-only: once saved, nobody — including you — can read them back out of here, so a lost token is replaced rather than recovered.

Slack

Connect Slack and this app will post a daily standup, a morning review, and a fleet charge/grounded alert into channels you choose. Set up once for your whole company — not on each computer.

Step-by-step: connecting Slack ~10 minutes, once

You'll create a small Slack app that belongs to your workspace, give it permission to post, and paste its token below. Nobody outside your company ever sees it, and you can revoke it from Slack at any time without touching this app.

1
Decide on your channels first. Create up to three channels in Slack — for example #daily-standup, #fleet-status and #morning-review. They can be private. Only the standup one is required; leave the others blank to turn those posts off.
2
Create the app. Go to api.slack.com/apps → Create New App → From scratch. Name it anything (“Dispatch Desk” works) and pick your workspace. You need to be able to install apps in that workspace; if you can't, a Slack admin does this part.
3
Give it permission to post. In the left sidebar choose OAuth & Permissions, scroll to Scopes → Bot Token Scopes → Add an OAuth Scope → pick chat:write. That one scope is all it needs. It cannot read your messages.
4
Install it. Scroll back to the top of that same page → Install to Workspace → Allow.
5
Copy the token. Still on OAuth & Permissions, copy the Bot User OAuth Token. It starts with xoxb-.
This is a password. Don't paste it into a chat message, an email or a spreadsheet — paste it straight into the Bot token box below. If it ever leaks, click Regenerate on that page and paste the new one here.
6
Invite the bot into each channel. Installing the app does not put it in your channels. Open each channel and type /invite @Dispatch Desk (use whatever you named it).
Skipping this is the most common reason posts never appear. Slack accepts the request and silently drops it, so there is no error to see anywhere.
7
Get each channel's ID. In Slack, click the channel name at the top → scroll to the bottom of About → Channel ID, and use the Copy button. It looks like C0BSGCU54GP.
The #name won't work here — channels get renamed, IDs don't.
8
Paste everything below and save. Token plus the channel IDs, then Save Slack Settings.

What happens next

The posts come from whichever computer runs scheduled sync — not from this page, and not from your browser. That computer picks up these settings on its own within about 30 minutes, so there is nothing to enter anywhere else and nothing to re-do when you change a channel later.

If nothing arrives

Is the bot actually in the channel? Step 6 is skipped more often than any other.
Is the channel ID the C… value rather than the #name?
Is a computer running scheduled sync, and is it switched on? Nothing posts from a machine that is asleep.
Was the token regenerated in Slack? The old one stops working immediately — paste the new one here.

Turning a post off

Clear that channel's box and save. Clearing the bot token stops all three.

Paste the Bot User OAuth Token (starts xoxb-) and the channel IDs from the steps above.

Posts are made by a machine running scheduled sync, not by this page. That machine picks these up on its own within 30 minutes — there is nothing to re-enter anywhere else.

SMS (SMS Gate)

Only needed if you use the Messaging tab. The webhook secret is in the SMS Gate app under Settings → Webhooks, and is what lets inbound replies be trusted.

🧩 The Dispatch Desk Extension browser extension ›

Scrapes delivery/ops data from Amazon Logistics for payroll compliance and daily assignments. Install once, then export data to upload on the Payroll tab.

1Unzip the download, go to chrome://extensions, enable Developer Mode, click Load Unpacked, and select the folder
2Open The Dispatch Desk extension, set your date range, and click Run
3When the scrape completes, download the export and upload it on the Payroll tab

Data

💾 Database Backup ›

Export a full snapshot of your Firebase database, or restore from one. Restore via Firebase Console → Realtime Database → ⋮ → Import JSON, or use the section restore below.

⬇

Export Database

Download a complete JSON snapshot of all app data — parking, fleet, preferences, delivery notes, DCR, and payroll.

⬆

Restore Database

Upload a previously exported JSON, then choose whether to restore everything or just specific sections.

📂

Drop backup JSON here or click to browse

ℹ️ About ›

The Dispatch Desk ·
Deployed on Netlify · Firebase Realtime Database

The tools your operation needs, in one place.

DayList

Fleet Log & Van Parking

Attendance & Coaching

Scorecard

Messaging

The standup writes itself

The Dispatch Bridge extension

Runs in the browser

Simple to roll out