MCR Dispatch — Help

Quick start

Want a different view of the same day? Compact Summary (next to Messages) lists the stops in a short form you can work from while dragging work orders onto the Salesforce console. 📍 State Console shows any state and date without running a dispatch. Print this page from the button at the top if you want paper. The rest of this file is the longer reference.

⚡ Quick Reference

The short version. Every row below links to the full section if you need more.

🆕 What's New

Updated 10 October 2026. Print this page (button top right) if you want a paper copy.

Site history is the same everywhere

Tapping a site name now opens the same history popup on the dispatch board, the State Console and Saturday On-Call. It shows past visits with their closing notes, the emails behind tickets, shipments with tracking links, and has ✅ Mark Restocked, Load more and Print. See Site History.

Visit history cleanup

Hundreds of past visits that had been filed under the wrong store were moved to the right one (Palm Beach, Broward and Lee County in Florida; several Michigan, Indiana, Colorado, Georgia, Minnesota and Nevada stores). A few site names were corrected so look-alike stores no longer get mixed up. If a store's history still looks wrong, tell an admin which site and visit.

Blue Folder is closed

OTC / testing-station close-outs and those calendar entries now live in the app. Use ⏱ Service responses for ITI times and miles (default filter: Michigan testing). Click any column header to sort; Arrival defaults to newest first. Ordinary kiosk restocks and trouble tickets were never Blue Folder — still planned here, still dropped in Salesforce.

Tomorrow / Monday date button

Next to Dispatch Date. Weekdays it is Tomorrow. Saturday or Sunday it is Monday. After you tap it, the label becomes the weekday of the date now on the board (Wed, Thu…). Set the date back to today and it returns to Tomorrow / Monday.

Carrier sheet on Text this stop

If a tech has no carrier, the sheet asks for their cell and a dropdown: Verizon, T-Mobile, AT&T, Sprint, or type the full gateway. Picking a listed carrier builds number@vtext.com (etc.) and always saves it on their technician card. Email only is still there if you only need this one message.

Text this stop (trouble tickets)

Each assigned trouble WO on the board has 📱 Text this stop under Done / Cancel. Restocks stay on the big Messages list. The draft names the site, WO, issue, and SLA. If the site was already a restock, the wording is that a trouble ticket was added to that restock — same truck, now timed. There is no “please acknowledge”; replies to the carrier gateway do not come back into the app.

The text includes a short link mcrdispatch.net/ack?t=…. When the technician taps it they see a one-line confirmation page. The stop card gets a green ✓ confirmed receipt line. The first tap can ping the on-call dispatcher; a second tap does not.

If that technician has no carrier on file, the sheet above appears. Fill Carrier once and both Text this stop and Watchdog use it.

Same site, restock plus trouble

The board still shows one stop per site. If a morning restock was completed and an afternoon trouble WO lands, the board now prefers the open ticket over the completed restock so the WO does not vanish. The restock details stay on the card; the red SLA / Due line is added underneath. A second unrelated WO the same day is the amber ⚠ Another ticket today — tap for WO / notes chip (opens site history). Do not assign a second technician — they are already going.

Watchdog uses the technician card

Notifications still control who is on, which states, and active hours. The actual SMS address now comes from the matching technician card (or the dispatcher login’s linked technician) when that gateway is valid. Office-only logins with no technician row still use the number typed on Notifications.

Mileage log (technicians)

Technicians with the tech role land on the mileage page only — not the dispatch board. Dispatchers can open it from the sidebar. Drafts survive a refresh. Export matches the company mileage spreadsheet. The spreadsheet remains the backup.

Board login and home state

Opening the dispatch board now asks for the same username and PIN as Admin. The region list is limited to that person's territories (admins see every state). The board opens on the last state they used, or their first territory if they have no last-used state. Switch user is at the top for a shared tablet. The splash stays up until the board has actually loaded, so the empty map/cards should not flash on a fresh start.

Saturday On-Call page

A dedicated Saturday console (/saturday-oncall, also linked from the board) shows only trouble tickets due that Saturday across coverage states. Closest on-call house is a suggestion until you tap Assign. Reassign defaults to that day's on-call list; Show all techs is the escape hatch. Message sends a short SMS ("details in email") plus a full email. After a real assignment, the text includes a tap-to-confirm link; when the tech taps it the card shows ✓ Received and today's on-call dispatcher gets a ping. There is no Sunday coverage -- the date picker skips Sunday. Add ?preview=1 for demo tickets; demo texts are stamped TEST — DO NOT DISPATCH and do not write assignments.

User management in Admin

Admins get a Users tab to add logins, change PINs, edit territories/role, and deactivate people who leave. Show unmasks a PIN when someone calls. Anyone can use Change my PIN on the Admin login screen if they still know the old one. On the Technicians tab, This employee is also a dispatcher creates the login and links it to that employee profile so Saturday alerts use the same phone/carrier.

Quick Add for the Distance Matrix

Saving a new technician or location (or editing one's address) on the Admin Panel now offers to add it to that state's distance matrix right then -- a small popup with an Add to matrix button, no need to know the Distance Matrix tab exists. It shows the real price before anything runs (typically a dollar or less for one tech or one site, since it only prices that one new item against everything already built), asks for the admin password, then handles geocoding, drive-time, and -- for a new location -- site-to-site distances automatically. The same guided flow is also available any time from the Distance Matrix tab itself under ➕ Quick Add, without needing to have just saved something. See Admin Panel for the full rundown, including how this differs from the state-wide build tools.

Armored Truck Meet Tracking (cash-side tickets)

A "Big Kahuna" (cash-side) trouble ticket that needs an armored-carrier technician on site no longer runs against the standard 4-hour SLA clock -- the app now tracks the real back-and-forth negotiation with the carrier's regional branch instead. See Armored Truck Meets below for the full explanation.

State Console

A separate at-a-glance page for one state at a time -- 📍 State Console from the dispatch board, or navigate to state.html directly. Shows who's out today, a map of any saved date's routes (independent of whatever date the dispatch board has open), recent trouble/maintenance tickets, and closed-ticket sync status, without needing to run a full dispatch. Remembers the last state you viewed there. See State Console below for the full rundown.

AI Dispatch Assistant is live

The command bar (dispatch board and State Console) now takes typed or dictated natural-language commands -- "move stop 2 from Robert to Sean" -- and applies them directly to the board. The dedicated 🧭 Analyze Routes button scans the current day's board and suggests specific one-stop swaps between techs, each with the net mileage it would save and its own Apply/Revert button. See AI Assistant below.

Watchdog Log

A per-state page listing every open trouble, install, and site-survey ticket -- including ones that never got a matching site code, which previously were only visible via SMS alert with no way to track or revisit them. Sorted by urgency; anything more than 4 days past its own deadline drops off as stale rather than cluttering the list indefinitely.

Trouble-ticket SLA is now calculated, not read from the email

The app now computes the real SLA itself, rather than relying on the ticket's stated priority -- 4 business hours, 8am-5pm, in the site's own local timezone, honoring Saturday coverage where it applies and excluding it where it doesn't. Email-stated deadlines still apply for same-day restock requests and scheduled site-survey meet times.

More states online

Idaho, Mississippi, Oregon, Nevada, Ohio, Indiana, and California have all been added since the last update, alongside the existing GA/FL/CO/MI/SC/NC/MN/IL/WV coverage. California in particular is a large territory -- 290 locations and 15 technicians -- so if you're covering it for the first time, the State Console is the fastest way to get oriented before touching the full dispatch workflow.

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

Individual logins have been added per person.

Inbound Dispatch via Email

Forward any dispatch list or trouble/maintenance ticket email to dispatch@mcrdispatch.net. What happens next depends on the type:

• Trouble, maintenance, install, and site-survey tickets are added to that site's board entry automatically -- no action needed.
• The daily bulk restock dispatch list is not auto-processed onto the board. It's received and cached for the app to pick up. A gold banner appears at the top of the dispatch board saying a new list has been received -- tap Load, then Generate Dispatches to actually create the day's stops.

Trouble Ticket SMS Alerts

When a trouble ticket is forwarded to dispatch@mcrdispatch.net, an alert is sent 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. Text alerts to Verizon phones are currently blocked by the carrier, so check the Watchdog page for new troubles until that is restored.

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

The dispatch board requires a username and PIN (same credentials as Admin). After sign-in, the board opens on your home state. The session lasts for that browser tab; use Switch user when handing off a shared tablet.

Admin Panel uses the same login. Forgot PIN: an admin can Show or Change PIN on the Users tab. If you remember the current PIN, Change my PIN on the Admin login screen is enough — no email reset.

Technicians with a mileage-only login skip the board and land on the mileage page. Dispatchers should not use those accounts.

Credentials are not published on this page. Ask an admin if you were pointed at the site without a PIN.

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.

Show all service locations (off by default) adds the rest of the state's sites as dots: green on track, amber due soon, red overdue for forms. Testing / OTC (T-codes) stay gray — they are not form-restock sites. Zoom and pan survive a refresh and survive toggling that checkbox. The AI command bar stays available in the expanded map.

On a gray/red/amber site popup you can jump to Restock Tracker notes for the last visit, and see driving distance to the nearest stop already on today's board (not the straight line on the map).

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; elsewhere, or for specific pairs the matrix build didn't resolve, distances fall back to straight-line and are marked (est.).

State Console

A single-state overview page, separate from the main dispatch workflow -- useful for a quick check-in, or for getting oriented in a state you don't normally cover. Access it via 📍 State Console on the dispatch board (carries over your currently selected state and date automatically) or by navigating to state.html directly.

• Map View -- plots any saved date's routes for the selected state. This has its own date field, separate from the dispatch board's Dispatch Date -- set both if you want them to match.
• AI command bar + Analyze Routes -- same assistant as the dispatch board. See AI Assistant.
• Restock Status -- current restock schedule for the state.
• Recent Trouble/Maintenance Tickets -- last 3 days by when a ticket was added to the system (not by due date), with a Trouble tickets only filter and a Hide closed tickets toggle.
• Site names are tappable -- opens the same Site History popup as the dispatch board.
• Update Closed-Ticket Data -- trigger the Salesforce closed-ticket sync on demand, or upload a manual export, without going through Admin Panel.

Site History

Tap a site name on a stop card to open that site's history. The popup is the same on the dispatch board, the State Console and Saturday On-Call.

• Visits -- newest first, with the date, technician and what was done. Restocks and preventative maintenance show in green, trouble calls in red. Load more goes further back.
• View Note -- opens the technician's closing note for that visit. Visits that came in by email (testing-station / OTC close-outs) show the note from the email.
• View ticket email -- opens the Neumo email behind a ticket. From there you can forward it.
• Shipments -- parts and consumables sent to the site, with a tracking link when there is one.
• ✅ Mark Restocked -- records that someone restocked the site (for example, while already there for another reason). It adds a record to the history and takes an optional note. It does not change the restock schedule or the overdue calculation.
• Print -- a printable copy of the history. Press Esc to close the popup.

AI Assistant

Available on both the dispatch board and the State Console, once a board is generated for a real date.

Typed or spoken commands

Type or tap the mic and speak a plain-language instruction -- e.g. "move stop 2 from Robert to Sean" -- and tap Run. The assistant applies the change directly to the board and repaints the map. Voice input runs entirely in the browser; nothing is recorded or sent as audio.

🧭 Analyze Routes

Scans the currently generated board and suggests specific single-stop swaps between two technicians where doing so would reduce total fleet mileage, or meaningfully even out a lopsided day (one tech nearly idle while another is overloaded) even when the mileage math alone is close to neutral. Each suggestion shows the site, which tech it would move from/to, and the net mileage change, with its own Apply button -- apply just the ones that make sense, and tap again to revert (the button relabels itself). It won't suggest moving a stop onto someone marked unavailable that day, won't suggest a swap that would push the receiving tech into likely overtime for the day, and won't hand more than a couple of stops to the same tech in a single pass.

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.

📱 Text this stop

Urgent / Trouble Ticket Dispatch

Armored Truck Meets (Cash-Side Tickets)

A "Big Kahuna" (cash-handling) kiosk has a locked cash vault behind a separate door from the printer/consumables side. An MCR tech can work on the cash side, but a carrier technician (Loomis in Michigan and Oregon; Brinks in Indiana -- the carrier varies by state) must be present whenever that side is opened. So whenever a ticket needs the vault opened, MCR has to schedule a "meet" -- a time both an MCR tech and a carrier tech will be on site together -- over an email back-and-forth with that carrier's regional branch.

Why this ticket type is handled differently

A normal trouble ticket's deadline is the app's standard 4-business-hour SLA. That doesn't make sense for an Armored Truck Meet ticket -- the real deadline is whatever date/time both sides actually land on, which can take anywhere from same-day to a couple of weeks depending on the carrier's own route capacity. Holding these to a 4-hour clock would just mark them "overdue" almost immediately for no real reason.

What the app does automatically (live now)

What's planned, not live yet

• A visible badge/status on the dispatch board itself, in place of the SLA countdown, showing where a given ticket's negotiation stands.
• A toast alert when a new Armored Truck Meet ticket comes in, with a button to send the initial scheduling request straight from the app.
• A per-state/branch carrier contact directory (regional office, contact name, phone, email) so the app knows who to address -- built for Michigan (Detroit and Grand Rapids branches) and Oregon (Portland) so far; other states get added as their contacts are gathered.

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 main board still auto-marks everyone Not on call except the scheduled on-call techs. Day-to-day Saturday work now lives on 📞 Saturday On-Call (saturday-oncall.html).

What the Saturday page shows

• Trouble tickets due that Saturday for coverage states (GA, IN, MI, NV, …). Restock lists stay off this page.
• Map pins for on-call houses and tickets, with SLA and a review badge when a site may already have a ticket today.
• Who is the on-call dispatcher for that calendar Saturday -- Change if you are covering for someone else before enabling text alerts.

Assigning

Closest on-call house is only a suggestion. Nothing is written until you tap Assign suggested or pick someone in the dropdown. The dropdown is that state's Saturday on-call list (usually one or two people). Show all techs is for the occasional cover-from-next-door case. Primary/secondary from the weekday board is not used here, because those people are often the same ones already on call.

Messaging

💬 Message sends a short SMS telling the tech the details are in email, plus a full email (WO, site, address, issue, SLA, closed-Saturday warning). After the stop is actually assigned, the SMS also includes a tap-to-confirm link. Tapping it stamps the assignment received, shows ✓ Received on the card (refreshes about every 20 seconds), and texts today's on-call dispatcher. Tapping twice does not ping again.

Demo mode

Add ?preview=1 to see sample placards without writing to the database. Demo SMS/email are labeled TEST — DO NOT DISPATCH. Confirm-receipt links are not created in demo, so testers cannot accidentally ping the live Saturday dispatcher.

Georgia weekday rotation (still used by the main board)

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.
• Saving a new location, or editing one's address, prompts to add it to that state's distance matrix right there -- see Quick Add under the Distance Matrix Tab below.

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.
• Check This employee is also a dispatcher to create a board/Saturday login linked to that employee (phone/carrier already on the profile is reused).
• Saving a new technician, or editing their home address, prompts to add them to their home state's distance matrix right there -- see Quick Add below.

Users Tab (admin role only)

• Add a login (username, 4–8 digit PIN, dispatcher vs admin, territories).
• Edit role and territories, Change PIN, or Show the current PIN when someone calls having forgotten it.
• Deactivate instead of delete when someone leaves -- they cannot sign in; history stays. You cannot deactivate or demote your own admin login.
• The Saturday dispatcher dropdown is this same list (active dispatcher and admin logins; the generic shared admin account is hidden).

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. Two kinds of data get built: tech-to-site (each technician's drive time to every location -- powers nearest-tech suggestions) and site-to-site (every location's drive time to every other location -- powers Map View's real distance labels and route-order suggestions). Both are one-time builds per state in normal use, not something to re-run casually.

➕ Quick Add -- the fast, safe way to add ONE new technician or ONE new location to a state that's already built out. Shows the real price before anything runs (typically well under a dollar, since it only prices that one new item against everything already on file), asks for the admin password, then handles geocoding and drive-time automatically -- plus site-to-site for a new location. No Full Rebuild, Force re-geocode, or other options to get wrong. This is the same flow offered automatically after saving a technician or location on their respective tabs (see above) -- Quick Add here is for running it again later, or for anyone who dismissed that prompt.

The rest of the tab is the advanced, state-wide toolset -- Geocode Locations/Techs/All, Build (Straight-Line, Free) and Build (Drive-Time) for the full tech-to-site matrix, Build Site-to-Site Matrix for the full state, and Fill Missing Pairs Only to top up a state's site-to-site coverage if it's ever incomplete (cheaper than a full rebuild -- only queries pairs that don't already exist). These carry real cost for anything beyond a single state's worth of new sites/techs, so Quick Add above is the better choice for routine one-at-a-time additions.

Both driving-mode builds (advanced and Quick Add alike) require a separate admin password beyond your regular login.

A haversine (straight-line) mode is also available, free and instant, as a fallback or a first pass before paying for real drive-time.

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.
• Each row can open the same site-history overlay used on the board (clickable SA / WO numbers and notes). Problem-type filters (journal printer, registration printer, print quality, connectivity, and other frequent categories) can be left on one state or set to all states to see whether a problem is local or multi-state.
• Print PDF is available, same idea as the dispatch-summary print on the board.

Issue Trends Tab

• Looks across closed tickets (and closing notes where we have them) to show whether a problem type is getting better or worse over time -- not just which site has had three of the same thing.
• Use it for questions like “are Florida registration-form tickets cooling off” or “is a journal-printer / ribbon pattern showing up in more than one state.” Leave the state filter on All to surface multi-state spikes.
• Same problem-type families as Repeat Issues (journal, registration, print quality, connectivity / offline / power, plus other frequent buckets). Print PDF is on this tab as well.
• This is a trend view, not a work order. Confirm with the field before treating a spike as a parts or driver campaign.

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.

Service responses

• Also linked from the dispatch sidebar between Mileage log and Admin.
• Times and miles parsed from ITI “Technician Service Response” emails — the testing-station / OTC close-outs that used to be typed into Blue Folder.
• Default filter is Michigan testing stations (what gets billed). Change state or uncheck Testing to see more.
• Click a column header to sort. Arrival starts newest first. CSV and Excel are for marking what actually goes on an invoice.

Inventory

• Who has mailed inventory@mcrtechservice.com this period. Placeholder “Unassigned (New Site)” cards are hidden.
• One email credits one technician. The tech’s name needs to be in the subject (or they send from their own address). A forward from the office with only “GA, inventory” will not land on the right person.
• Spreadsheet counts and shipment emails are the next step — not live as a stock check yet. Nothing is forwarded to Neumo from this page.

Current Features

Planned Features & Future Upgrades

In Testing

• Toast alert when a new trouble ticket arrives while a dispatcher has that state's board open (periodic check, not auto-refresh, so it won't interrupt an in-progress reassignment).
• Toggle to show trouble tickets only on the dispatch board, auto-enabled on Saturdays -- avoids restock tickets generating false "no coverage" prompts against Saturday's on-call-only roster.

Medium Term

• Parse inventory spreadsheets and warehouse shipment emails so Monday counts can be checked before they go to Neumo.
• Days-of-supply warning from that tech’s own restock pace, not a company-wide “under 10 rolls” line.
• Automated UPS delivery/return confirmation, replacing manual "Mark Returned" tracking.

Longer Term

• Full site-to-site and tech-to-site distance matrix coverage for the remaining smaller states.
• Who nearby can spare a roll or a card reader when someone is short.

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 for that state -- a handful of smaller states are still pending; elsewhere, and for any specific pairs a build didn't resolve, distances fall back to straight-line, 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 are captured from roughly mid-August 2026 forward. Older visits show no note even if one exists in Salesforce; look it up there if the notes box says none are on file (the SA number is copied for that search).
• Brand-new locations, and testing-station / OTC stores that have not had a ticket yet, may not appear in Site History until their first ticket creates the site.
• Mail to @mcrtechservice.com from the app is accepted by the host; if someone does not see it, check Junk before assuming it never sent.

Last updated: October 10, 2026