What's New in DailyDSP

Subscribe by December 1, 2026 with code DailyDSP4Peak and use DailyDSP free, with full access, until week 1 of 2027 (week of January 3, 2027). Starting that week you become a lifetime Charter member at $0.25 per route. Cancel anytime. If you cancel before week 1 of 2027, you will never be charged for DailyDSP use. Limited to the first 25 DSPs. Card required at signup; you won't be charged until week 1 of 2027, and then only for routes you run from that week on. A 100-route weekly minimum applies starting week 1 of 2027. Enter the code on the subscribe page. If the code is expired or the spots are full, signup shows that reason. Subscribe with this code →

Routes upload auto-detects Daily Dispatch — no format picker. Station and date come from the workbook, with a format banner; Cortex still uses the filename (enter them yourself if the name cannot be parsed). Vehicle matches Amazon Fleet ID. Blank Route rows are skipped. After Daily Dispatch, guided workflow skips Staging. Import Complete says whether station/date came from the filename, the workbook, or what you typed. See docs →

Toolbar Copy previous week (or right-click the Driver heading) copies last week’s assigned shifts as drafts. Right-click a day header or a driver name to copy just that day or that driver. Left-click the Driver heading to send portal links to every driver; right-click for copy / clear / send portal. See docs →

Generate Schedule is always available: preview/confirm, gap-fill, works after mass-clear. Empty repeating days show a faint calendar-plus (not a sync icon). Recurring is a modifier — heart+sync preferred weekly, ban+sync unavailable weekly, sync on a shift repeats that work shift. Preferred/unavailable paint forward without Generate; Generate only fills work shifts. Generate and Copy skip unavailable days and offer those as open shifts. Empty-cell top-right sync is gone: ban marks one-time unavailable, then sync on that cell for weekly. See docs →

Performance sits in the top nav after Schedule. Upload weekly Amazon scorecard PDFs (several files or a folder at once). Rounded ovals use Amazon’s printed standings (Fantastic, Great, Fair, Poor, Fantastic Plus, Coming Soon, Compliant, Non - Compliant) — never a generic “below Fantastic.” Safety includes Breach of Contract and Comprehensive Audit (CAS). Multi-station DSPs get a station pill per site; the week selector is independent of Schedule. DSB goal is 0. Drifted Safety/Delivery Quality metrics show TBD and open a support ticket with the PDF. See docs →

Drivers see three pills — always labeled Schedule, Reliability, and Scorecard. Reliability shows 14 / 30 / 90-day late-arrival, late load-out, call-out, and NCNS counts. Scorecard is that driver’s Current Week Performance from uploaded PDFs, matched by transporter ID only. BoC and CAS stay on the dispatcher Performance page. See docs →

Ask DailyDSP → Contact support opens a numbered ticket and a Slack #support thread. You get the Support ID and a permalink to add updates; DailyDSP emails the same when your account has an email. Attach 1–3 screenshots or a short recording (PNG, JPEG, WebP, GIF, MP4, WebM, MOV; 20 MB each). How-to stays in chat. See docs →

Turn Log Mode off for Conversations: one row per driver (no duplicate phones), full thread oldest to newest, and a pinned compose box. Enter inserts a newline; Send (or Ctrl/⌘+Enter) texts that driver. Replies appear live. Translation still shows the original plus English. Send stays disabled with a reason for unlinked numbers or opt-outs. See docs →

Right-click a day header, a driver name, or the Driver header to clear that day, that driver’s week, or the whole visible week (after a warning). Shifts can have a short label pill; presets and per-day template labels copy onto generated weeks. Drag a shift onto another empty cell this week to move it (no swap; past days blocked; recurring moves that instance only). See docs →

After registration, DailyDSP no longer texts a shared Slack join URL. If the account has an email, you get a text that a Guest invite is coming — check email. Ops invite teammates to #support; owners also get #dsp-owner-chat. Drivers are not invited. See docs →

Failed and undelivered texts show a short red pill (for example Opted out) instead of a generic Failed. Hover or tap for what to do next and the Twilio code — the detail no longer slides the Message Log sideways. Same labels on Dashboard and send results. See docs →

With Strict Service Type Match on, routes on Ignored Service Types get any available van instead of being refused. Auto-assign reports those ignored types by name rather than counting them as mismatches. See docs →

Login, Register, and the signed-in header say DailyDSP. The Drivers SMS Language dropdown includes Français, so editing a French-speaking driver no longer silently switches them to English or Spanish. See docs →

When a teammate finishes DailyDSP registration, they are invited to Slack #support (owners also #dsp-owner-chat). That first flow used a shared join link; September replaced it with a Guest invite by email. See docs →

After a DailyDSP deploy, operators see a short summary of what changed. View the full newest-first history, snooze (star icon stays in the header), or skip until the next update. See docs →

A comments button next to Help opens a chat that explains how to use DailyDSP from these docs. It cannot see your live board. Ask for a new capability and it is sent to DailyDSP — no ship date is promised. Owners, ops managers, dispatchers, and viewers share the same chat. See docs →

Dashboard, Drivers, Vehicles, and Schedule each walk you through the main controls the first time you open them. Turn tours off — or reset them so they run again — in Settings → General → Page tutorials. See docs →

The question-mark in the top nav opens this Support page at the section for whatever screen you are on — Dashboard, Drivers, Vehicles, Schedule, Affinity, Maintenance, Messaging, or Settings. See docs →

Add extra Type names — training, charter, nursery — from any Type dropdown or from Settings → Routes. Amazon types still come from Cortex and vehicle imports and are shared so a new DSP is not staring at an empty list. Custom names never appear at another location. See docs →

Settings → Routes now has three ignore lists: duplicate route numbers, duplicate staging slots, and route/van service-type mismatches. Custom types are added to the mismatch list automatically so they don’t warn until you want them to. See docs →

Affinity (from the Vehicles page) can prefer yesterday’s van, try it before or after affinity, and refuse any van whose Amazon service type doesn’t match the route. Only In Service vans are auto-assigned. See docs →

Templates are a full week of shifts — drag onto a driver’s name. Presets are a single shift — drag onto a specific day. The Schedule tour now covers both. See docs →

Invite owners, ops managers, dispatchers, viewers, and drivers with just a phone number and a role. DailyDSP texts a secure 48-character registration link that works in any mobile or desktop browser. Links expire after 7 days (30 days for an owner's first invite) and can be resent or revoked with one click. See docs →

Compose once in English — DailyDSP translates outbound SMS into each driver's preferred language using Google Cloud Translation. The AI agent auto-detects inbound language and replies in kind. Variables like {driver_name} are protected during translation so placeholders always resolve to live data. Supports English, Spanish, French, Portuguese, Haitian Creole and more. See docs →

Reminders now run themselves. Four configurable workers: schedule confirmation (un-confirmed upcoming shifts), late check-in alerts (sent to driver + ops users with alert_notify), giveup commitment follow-ups, and marketplace pickup reminders. Each respects quiet hours, messaging mode, and driver language preference. See docs →

Compose an SMS once, send it later. Pick a recipient (driver, ops user, or whoever ends up assigned to a route on a future date), pick a template or write ad-hoc text, and set the send time. Variables resolve at send time, so {driver_name} always means "whoever the recipient turns out to be." Maintenance Kanban cards can attach a scheduled message that auto-cancels if the card is deleted. See docs →

The AI agent now remembers the last 4 exchanges with each driver for 30 minutes, so follow-up texts make sense. Eight discrete tools the agent can call: get_todays_route, get_weekly_schedule, check_in, confirm_shift, request_giveup, set_availability, request_pickup, get_portal_link. Drivers text naturally; the agent does the right thing. Rate-limited to 20 messages/hour per driver. See docs →

Drivers give up shifts they can't work and pick up open shifts from the marketplace via the portal — without dispatch playing matchmaker. Configurable policies: auto-approve pickups, max giveups per week, minimum notice hours, auto-cancel windows. See docs →

Click any column header in the weekly schedule grid to open a quick-action menu. Three actions: Apply Template, Create Routes from Schedule (generates placeholder routes that the morning Cortex import upgrades automatically — no duplicates), and Send Shift Reminders (SMS every driver scheduled that day using your active "Shift Reminder" template). See docs →

Variance reports now show five distinct categories with click-through filtering: In Sync with Amazon, Time Mismatch, Amazon Rostered Not Scheduled (critical), DailyDSP Sched Only, and Amazon Sched Only. Fuzzy name matching (≥0.8 similarity) catches typos and capitalization differences without false-flagging.

Owners can now set per-tenant quiet hours (HH:MM, tenant TZ) — scheduled messages and reminders defer until the window closes. Check-in tolerance thresholds (checkin_ontime_minutes, checkin_warning_minutes, checkin_late_minutes) tune the on-time/warning/late status thresholds to your operation's tempo. See docs →

Plad's inbound SMS path silently failed for two weeks after a DNS change made the old plad.dd2.dailydsp.com subdomain NXDOMAIN — the Twilio Lambda was still pointed at it. Lambda env now points at the production webhook URL, and a smoke test was added to deploy verification so future DNS changes never cause silent SMS drops.

When a driver moves between DSPs at the same station, DailyDSP confirms the move with the driver via SMS YES/NO before re-routing their work messages. Pending transfers show a banner with a one-click resend; verification auto-expires after 7 days. The previous DSP's routing is unchanged until the driver replies.

Cortex-imported routes now stay selectable in the route-number dropdown even after admins rename them. Unassigned planned routes get a live warning badge on the dashboard with a one-click reassignment.

The Day-of-Ops file is canonical for staging slots and wave times. Renaming a route's number now snaps its staging info to whatever the file says for the new number — no re-upload needed. Manual edits persist until the next rename.

Service-type names (an Amazon-defined vocabulary) are now shared across all DailyDSP tenants. New tenants get the full catalog from day one — no waiting for the first import to populate dropdowns.

Driver and vehicle imports now handle blank cells, empty trailing rows, and pandas dtype quirks (numeric phones being read as floats) without producing ghost data. Per-row error reporting keeps a single bad row from nuking the batch. The "Preserve Local Values" picker lets you keep your edits to phone numbers, fuel PINs, or other fields when re-importing.

Reorder your message templates by dragging them — the order persists per template view (Today's Messages, Marketplace, etc.).

Invite new owners, dispatchers, or drivers with just a phone number and role — DailyDSP texts them a secure registration link. No email round-trip required.

Demo and sandbox tenants no longer interfere with production SMS routing. Inbound messages always route to the production DSP that actually owns the phone.