The platform is updated continuously. Here's what's shipped recently — features, improvements, and the occasional fix worth calling out.
SMS-first onboarding, multi-language messaging, automatic reminders, shift marketplace
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.
Cross-tenant driver portability, smarter route handling, hardened imports
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.
Want a feature you don't see here? Reach out via Support.