Logging In
Navigate to mcr-dispatch-hub.netlify.app and tap Admin Panel at the bottom of the screen.
| Username | PIN | Access |
|---|---|---|
| gina | 2847 | Georgia / NC / SC dispatch |
| admin | 2847 | All states + admin functions |
Daily Dispatch — Standard (Next Day)
Step 1 — Check date and region.
Confirm the Region and Dispatch Date are correct at the top of the screen.
The date defaults to the next business day automatically. Friday defaults to Monday. Saturday defaults to today (urgent mode).
Confirm the Region and Dispatch Date are correct at the top of the screen.
The date defaults to the next business day automatically. Friday defaults to Monday. Saturday defaults to today (urgent mode).
Step 2 — Review technician availability.
The board auto-marks comp days from the on-call schedule.
Tap Mark Out to manually mark a tech unavailable. Tap again to restore.
The board auto-marks comp days from the on-call schedule.
Tap Mark Out to manually mark a tech unavailable. Tap again to restore.
Step 3 — Paste the dispatch email.
Copy the full dispatch email from your inbox and paste it into the Location Codes field.
Copy the full dispatch email from your inbox and paste it into the Location Codes field.
Step 4 — Generate.
Tap Generate Dispatches.
Tap Generate Dispatches.
Step 5 — Review and adjust.
Use the Reassign dropdown on any stop to move it to a different tech.
After reassigning, a prompt asks if you want to save the new tech as permanent primary for that location.
If a location has no fallback and the primary is out, a queue prompt cycles through each affected location asking who should cover.
Use the Reassign dropdown on any stop to move it to a different tech.
After reassigning, a prompt asks if you want to save the new tech as permanent primary for that location.
If a location has no fallback and the primary is out, a queue prompt cycles through each affected location asking who should cover.
Step 6 — Send messages.
Tap ✅ Messages to generate tech text messages, then Copy Message for each tech and send.
Tap ✅ Messages to generate tech text messages, then Copy Message for each tech and send.
Step 7 — Print or open Restock Tracker.
Tap Print Dispatch Summary at the top to open a printable summary in a new tab.
Tap 📊 Restock Tracker (desktop) or 📄 Report (mobile) next to the Messages button for quick access to the restock tracker or a mobile-friendly route report.
Tap Print Dispatch Summary at the top to open a printable summary in a new tab.
Tap 📊 Restock Tracker (desktop) or 📄 Report (mobile) next to the Messages button for quick access to the restock tracker or a mobile-friendly route report.
Dispatch Card Controls
Each stop on a technician's card has the following controls:
| Control | What it does |
|---|---|
| 🚦 Traffic | Opens Google Maps traffic view from the tech's home to their first stop. |
| 🗺️ Route | Opens a multi-stop Google Maps route for all of the tech's stops in order. |
| ▲ / ▼ | Reorder stops within a tech's list before generating messages or a route. |
| Reassign | Move a stop to a different tech. Prompts to save the change as permanent. |
| → Tomorrow | Pushes a same-day stop to the next day. Only appears on TODAY-flagged stops. |
| ✓ Done | Marks a stop completed and moves it to the Session Actions list below. |
| ✗ Cancel | Marks a stop canceled and moves it to the Session Actions list below. |
Stop Badges
| Badge | Meaning |
|---|---|
| TODAY | Must be completed today — SLA or same-day restock. |
| Right Forms | Right-side (previous year) registration forms requested. Confirm tech is carrying them. GA SK/BK only. |
| Reassigned | Stop was moved from its default tech this session. |
Cluster / Corridor Banner
When a dispatched site is in a known remote cluster (Augusta area, Charlotte NC, Fayette/Clayton corridor), a blue banner appears suggesting you check the Restock Tracker for nearby sites that may benefit from a preemptive restock.
Session Actions — Undo
When you mark a stop Done, Cancel, or push it to Tomorrow, it moves to a session log at the bottom of the results. Each entry has an ↩ Undo button that fully restores the stop to its original position in the queue with all badges and flags intact.
Two separate sections appear when populated:
- → Pushed to Tomorrow This Session — stops that were pushed from today to tomorrow. Undo reverts the date and urgency.
- ✓ Completed / Removed This Session — stops marked Done or Canceled. Undo re-inserts them at their original queue position.
Note: Undo is session-only. Refreshing the page clears all session actions and undo history.
Urgent / Trouble Ticket Dispatch
Step 1. Select ⚡ URGENT (Same Day) from the Paste Mode dropdown. On Saturdays this is selected automatically.
Step 2. Paste the full trouble ticket email into the Location Codes field.
Step 3. Tap Generate Dispatches. The SLA end time is calculated automatically from the ticket's Earliest Start Permitted field.
Step 4. Tap ✅ Messages. The tech message reads:
⚡ URGENT - Hey Nyzier, a trouble ticket for
Cobb County Kroger Whitlock #455 just came in:
1. Printer Jam (SLA ends Sat 1:27 PM)
Please acknowledge receipt.
Unknown Location Codes
If a site code in the dispatch list isn't in the database, an amber banner appears listing each unknown code with an + Add to database button.
Tap it to enter:
- Location name — e.g. Hillsborough County Gunn Hwy Publix
- Full address
- Primary tech (optional)
- Machine type — SK (Small Kahuna), SB (Surfboard), or BK (Big Kahuna). This affects form count thresholds and restock rules. Defaults to SK if unsure.
The new location saves to the database immediately and the dispatch re-runs automatically with it included.
Note: If some codes are known and some aren't, the board generates for the known ones while the amber banner lists the unknowns above the results.
Saturday On-Call
On Saturdays the availability board automatically marks everyone Not on call except the two scheduled on-call techs. Dispatch assignments only go to on-call techs.
| Saturdays | On-Call Techs | Comp Day |
|---|---|---|
| Odd (05/09, 05/23…) | Nyzier Moore + Sean Reich | Monday before |
| Even (05/16, 05/30…) | Omari Williams + Robert Medley | Thu before (Robert M.) / Mon before (Omari) |
Note: Robert Whitehead covers Savannah only and is not in the on-call rotation. He does not take a comp day.
Admin Panel
Access via the Admin Panel button at the bottom of the main screen.
Locations Tab
- Search by site code, name, or address.
- Edit any location to set Primary Tech, Fallback Tech, and Machine Type (SK/SB/BK).
- Add new locations manually.
- Delete locations — hardcoded locations will reappear on next load; edit them to create a Blob override instead.
Technicians Tab
- Add, edit, or remove technicians for any state. Changes take effect immediately.
Backup / Restore
- Download a JSON backup of all saved data for the selected state.
- Restore from a previous backup file if needed.
Current Features
📋 Dispatch
- Auto date defaulting (Fri→Mon, Sat→today)
- Technician availability board
- Comp day auto-flagging
- Saturday on-call auto-mark
- Primary + fallback tech per location
- No-fallback queue prompt
- Reassignment with permanent save option
- Unknown code detection + add flow with machine type
- URGENT mode with automatic SLA calculation
- Done / Cancel / Tomorrow controls with ↩ Undo
- Traffic + Route buttons
- Print dispatch summary
- Desktop responsive layout
🔧 Machine Type Rules
- SK / BK (Small / Big Kahuna) — 800 form max count
- SB (Surfboard) — 700 form max count, all states
- Right Forms badge + confirmation — GA SK/BK only
- Partial restock SWAP warning — GA SK/BK only
- Color/decal rules — GA only
- Cluster/corridor banners — GA only
- NC all-surfboard auto-detected
- SC auto-assigns to Michael Newboult
⚙️ Admin
- State-scoped location management
- Location search bar
- Primary + fallback + machine type per location
- Blob-based persistent storage
- Backup and restore per state
🔔 Watchdog
- Email monitoring (dispatch + RMA)
- SMS alert on trouble tickets
- PC Name, WO number, issue category + detail parsed into alerts
- Duplicate reply filtering
Planned Features & Future Upgrades
Short Term
- Watchdog subject classifier fix
- Watchdog
--testmode — process a local sample email without touching live mailbox - Watchdog → Mailgun inbound webhook migration (event-driven, replaces polling)
- On-call schedule to Blobs with admin edit UI
- DCO toggle for right/left form selection
- FL location database reconciliation (33 sites pending code verification)
Medium Term
- Salesforce API integration — live WO data feed to dispatch tool
- Remote location cluster flag on dispatch cards (Columbus, Albany, Augusta, south of Macon)
- FL on-call schedule support
- Supabase parts tracking (via Watchdog)
- PWA share target — share dispatch email directly from any email app
Longer Term
- Distance matrix for automatic proximity-based tech assignment
- Two-tech travel comparison — compare drive time and mileage before assigning
- Supabase migration — replace Netlify Blobs as primary state store
- Full dynamic location loading from Blobs
Known Limitations
- Hardcoded locations cannot be permanently deleted from admin — edit them to create a Blob override, or request removal in the next code update.
- FL technician list is currently hardcoded — Dynamic TECHS from Blobs will fix this.
- On-call schedule is hardcoded through early 2027 — Blobs migration will make it editable without a code deploy.
- SLA calculation requires the Earliest Start Permitted field to be present in the ticket email.
- NC and SC share the GA location database in admin — separate NC/SC databases not yet implemented.
- FL location codes are partially unreconciled — 33 sites are pending correct PC code verification. Unknown codes will prompt for manual entry at dispatch time.
- Undo is session-only — refreshing the page clears all session action history.
Last updated: May 14, 2026 · Deploy 80 / blobs-51