⚡ MCR Dispatch Tool — Help

🆕 What's New

Map View

Tap 🗺️ Map View above the generated dispatches to see every tech's route plotted geographically, color-coded per tech, with a legend showing stop counts. Useful for spotting stops that are geographically close but assigned to different techs -- something that isn't always obvious from the text list alone, especially for anyone covering a state they don't know well.

Route Button Goes Straight to Maps

🗺️ Route on a tech's card now opens Google Maps directly with that tech's full route, no extra tap or popup in the way.

Cluster Tool

The 📍 pin icon next to Route lets you tag a tech's stops with a shared cluster name (e.g. "South Atlanta") for the corridor/preemptive-restock banner. A checklist lets you include or exclude specific stops -- useful when one stop is a genuine outlier (e.g. Sean has a Macon call mixed in with several South Atlanta stops).

Unmatched Sites -- SA Numbers & Map Lookup

The Admin Panel's Unmatched Sites tool now shows the Salesforce SA number(s) tied to each unresolved name, and a 📍 Locate via Maps button that geocodes the raw name and shows the nearest existing site with a real-world distance -- a much stronger signal than name-similarity alone for telling apart two differently-worded records of the same site, or two similarly-named but genuinely different sites.

Technician Numbering

Each tech's card now shows a small # number and a colored dot matching their route color on the Map View, making it easy to cross-reference a tech's stops between the list and the map at a glance.

Security Hardening

Login PINs are now unique per person (previously shared). The site-to-site and drive-time distance matrix builds -- both real, billed Google Maps API calls -- now require a separate admin password beyond the regular login, and are capped to one build per state per 24 hours to prevent runaway cost from a stray repeated click or a compromised login.

Inbound Dispatch via Email

Forward any dispatch list or trouble ticket email to dispatch@mcrdispatch.net and the app processes it automatically. A gold banner appears at the top when a new dispatch list arrives — tap Load to import it instantly.

Trouble Ticket SMS Alerts

When a trouble ticket is forwarded to dispatch@mcrdispatch.net, an SMS alert fires automatically to configured recipients (set per-state, per-person, with active-hours windows in Admin → Notifications) with the WO number, site name, issue, and SLA deadline.

Technician Availability Board

The availability panel shows all techs with real-time status. Comp days and Saturday on-call rules apply automatically. Tap Mark Out to manually mark a tech unavailable for unscheduled absences — the dispatch engine routes around them immediately.

Logging In

Navigate to mcrdispatch.net and tap Admin Panel at the bottom of the screen. Enter your username and PIN as provided to you directly -- credentials are not published here, since this page itself isn't login-protected.

Daily Dispatch — Standard (Next Day)

Dispatch Card Controls

Each tech's card shows a # number and a colored dot -- the same color used for that tech's route on Map View, so you can cross-reference between the list and the map at a glance. Each stop within a card is also numbered.

Stop Badges

Cluster / Corridor Banner

When a dispatched site carries a cluster tag (set via the 📍 tool above, or one of the built-in remote clusters like the Fayette/Clayton corridor), a blue banner appears suggesting you check the Restock Tracker for nearby sites that may benefit from a preemptive restock.

Map View

Tap 🗺️ Map View above the generated dispatches to plot every tech's stops geographically. Each tech gets a distinct color, matching the dot next to their name on their card. Tap any pin for that stop's site name, address, and distance from the previous stop.

The legend below the map lists each tech with their stop count and lets you toggle their route on/off. Stops without saved coordinates are listed separately under the map ("Not plotted") rather than silently dropped.

Distance figures use the real site-to-site driving-distance matrix where it's been built for that state (GA has the most complete coverage); elsewhere, or for specific pairs the matrix build didn't resolve, distances fall back to straight-line and are marked (est.).

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.

Urgent / Trouble Ticket Dispatch

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.

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.

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.

Technicians Tab

• Add, edit, or remove technicians for any state. Changes take effect immediately.
• Set each tech's carrier and SMS address here to enable the direct-Send feature on dispatch cards.

Backup Tab

• Download a JSON backup of all saved data for the selected state.
• Restore from a previous backup file if needed.

Notifications Tab

• Control who receives SMS alerts when trouble tickets arrive.
• Each recipient can be scoped to specific states (or all), with their own active-hours window and timezone -- outside that window, they're queued for a digest instead of texted immediately.

Distance Matrix Tab

• Builds real driving-distance data via the Google Maps API -- either tech-to-site (cheaper, ~$3-6/state) or the fuller site-to-site matrix (~$23-45 for a state GA's size), which also powers Map View's real distance labels and route sorting.
• Both driving-mode builds require a separate admin password beyond your regular login, and are limited to one build per state per 24 hours -- these are one-time-per-state builds in normal use, not something to re-run casually.
• A haversine (straight-line) mode is also available, free and instant, as a fallback for states without a real matrix yet.

Closed Tickets Tab

• Manually upload a Salesforce closed-ticket export, or trigger the automated sync on demand with Refresh Now.
• An automatic sync also runs every 20 minutes in the background when enabled.

Repeat Issues Tab

• Flags sites with 3+ trouble tickets for the same issue category within a rolling window (default 90 days) -- standard practice is to consider replacing hardware on the 3rd repeat, though it's worth confirming with the tech what they actually found on-site before deciding, since the same category can cover very different root causes.
• Adjustable scope (state or all), window, and minimum ticket count.

Unmatched Sites Tab

• Closed-ticket rows where the site name couldn't be confidently auto-matched, grouped by raw name so one fix updates every row sharing that name.
• Shows the Salesforce SA number(s) tied to each group for cross-referencing, plus a suggested match by name similarity.
• 📍 Locate via Maps geocodes the raw name and shows the nearest existing site with a real-world distance -- a stronger signal than name similarity alone, especially for telling apart two differently-named records of the same site versus two genuinely different similarly-named sites.

Restock Schedule Tab

• View and manage the on-call / Saturday coverage schedule.

Current Features

Planned Features & Future Upgrades

In Testing

• AI-assisted dispatch commands ("move stop 2 from Robert to Keontae") -- built, not yet live for general use while it's being tested.
• Standalone map/lookup page for quick reference (route map, ticket + closing-note history, RMA shipment status, repeat-issue flags) without the full dispatch-generation workflow.

Medium Term

• Closing-note visibility -- Neumo doesn't currently include these in the closed-ticket report; exploring both asking them to add the field and a browser-automation workaround.
• Automated UPS delivery/return confirmation, replacing manual "Mark Returned" tracking.
• Day-of-week restock volume reference, especially useful for someone covering an unfamiliar state.

Longer Term

• Per-dispatcher logins with individually configurable state coverage.
• Site-to-site distance matrix coverage for states beyond GA.
• Bundled/opportunistic restock suggestions when a tech is already near a site approaching its threshold.

Known Limitations

• 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.
• Undo is session-only — refreshing the page clears session action history (though the board itself now reloads correctly on refresh).
• Map View / route-sorting shows real driving distance only where the site-to-site matrix has been built (GA has the most complete coverage) -- other states, and any specific pairs the build didn't resolve, fall back to straight-line distance, marked "(est.)".
• On-call schedule is hardcoded through early 2027 in the app's code -- it will need extending (or migrating to an editable admin UI) before then.
• Closing notes from Neumo aren't currently available in the closed-ticket report, so full ticket history for a site still requires manually checking Salesforce.

Last updated: August 18, 2026  ·  v9.78