Support Center

Logging In

Understanding the Navigation

After logging in, the main navigation is across the top of the page:

Affinity, Maint. Board, and Vendors are reached from the Vehicles page (buttons in the header). The first time you open Dashboard, Drivers, Vehicles, Schedule, or Performance, a short guided tour highlights the main controls. Turn tours on or off in Settings → General → Page tutorials.

After DailyDSP is deployed, a What's New prompt lists what changed. View opens a newest-first history. Snooze keeps a star icon in the header. Skip hides it until the next update.

Setting Up Your Profile

Proper profile setup ensures you receive notifications and the app displays times correctly.

Changing Your Password

For security, change your password periodically:

1. Click your name in the top-right header
2. Scroll to the Change Password section
3. Enter your Current Password
4. Enter your New Password (must meet requirements)
5. Confirm your New Password
6. Click Change Password

Workflow Overview

Step 1: Upload Routes

The Routes stepper accepts Amazon Cortex files and Amazon Daily Dispatch workbooks. DailyDSP detects which one you dropped — there is no format picker.

Step 2: Upload Staging Information

Staging data tells drivers where their packages are located in the warehouse. Staging is already in Daily Dispatch — after a successful Daily Dispatch import, the guided workflow skips this step. You can still upload a separate Day-of-Ops staging file if you used Cortex instead.

Step 3: Assign Vehicles

Vehicles can be assigned automatically (based on affinity) or manually.

Step 4: Send Driver Messages

Notify drivers of their assignments via SMS.

Step 5: Monitor Check-Ins

Daily Checklist

Dashboard Overview

The Dashboard is your central hub for daily operations. It displays:

• Routes for the selected date
• Driver and vehicle assignments
• Check-in status
• Message delivery status
• Quick action buttons

Quick Statistics

A red unassigned badge on the Routes header means Cortex-planned route numbers for this date are not currently on any row (for example after a rename or deleting a row). Put those numbers back on a row, or re-import Cortex. Deleting every row for the day still leaves that reminder until the planned numbers are assigned again.

Orange mismatch warnings on a Type cell mean the route’s service type does not match the assigned van. Suppress those (and duplicate route/staging warnings) in Settings → Routes ignore lists. Custom service types are added to the ignore list automatically. Ignored types also skip the Strict Service Type Match gate during auto-assign.

Routes Table Columns

Keyboard Shortcuts

Overview

DailyDSP's Schedule module gives you complete control over weekly planning:

• Visual weekly grid — click a cell to add a shift, or drag templates and presets
• Generate Schedule — always available; fills empty days from repeating work shifts after a preview. Empty repeating days show a faint calendar-plus (not a sync icon)
• Copy previous week — toolbar, or right-click a day, a driver, or the Driver heading
• Recurring — a modifier: sync on a shift, heart, or ban to repeat weekly. Preferred and unavailable already show on future weeks without Generate
• Templates — a full week of shifts (multiple days). Drag onto a driver's name to apply the whole week. Each enabled day can have its own Label
• Presets — a single shift (start, end, service type). Drag onto a specific day for a driver; the preset name becomes the shift label
• Drag to move — drag an existing shift onto another empty cell in the same week
• Mass-clear — right-click a day, a driver, or the Driver header to clear many shifts at once (after a warning)
• Driver heading — left-click sends the portal link to every driver on the grid
• Publish Week — drafts stay private until you publish; drivers then see shifts in their portal
• Amazon variance — compare your schedule to Amazon’s rostered work blocks

Templates vs Presets

Both live in the bars just under the Schedule title.

Building a Weekly Schedule

1. Select the week using the arrows or week picker
2. Click Generate Schedule any time to fill empty days from repeating work shifts (it asks first with a count; already-filled days stay). After you mass-clear a week, Generate still works
3. Or click Copy previous week to copy last week’s assigned shifts onto this week as drafts
4. Your active drivers appear as rows
5. Click an empty cell to add a shift, drag a preset onto a day, or drag a template onto a driver name
6. Optionally add a short label (up to 36 characters) when creating or editing a shift — occupied cells show it as a pill next to the time
7. Click an existing shift to edit or remove it, or drag it onto another empty cell in this week to move it
8. When drafts look right, click Publish Week so drivers can confirm in the portal

Generate Schedule

Generate Schedule is always available. It fills empty days from repeating work shifts (the sync icon on a scheduled shift). It asks first with a count, never replaces a day that already has a shift, and can be clicked again — including after you mass-clear a week.

• Empty days that will fill show a faint calendar-plus icon, not a sync icon
• Preferred (heart) and unavailable (ban) already show on future weeks without Generate — Generate does not create those
• Generate and Copy previous week will not assign a shift onto a day the driver is unavailable (set by the driver or a scheduler). If any were skipped, DailyDSP asks: create those as open shifts (no driver) or drop them

Copy Previous Week

The toolbar Copy previous week copies last week’s assigned shifts onto the week you are viewing as drafts. Days that already have a shift are skipped. Open and unassigned marketplace posts are not copied. You still Publish Week so drivers can see the drafts.

• Toolbar or right-click the Driver heading — whole week, all drivers (same action)
• Right-click a day header — Copy previous [day] (that weekday from last week, all drivers)
• Right-click a driver name — only that driver’s assigned shifts from last week

Recurring, Preferred, and Unavailable

Recurring is a modifier on whatever the cell already is — not a separate shift type.

• Heart + sync — preferred every week on that weekday
• Ban + sync — unavailable every week on that weekday
• Sync on a shift — that work shift repeats weekly
• Preferred and unavailable paint forward without Generate. Generate only fills work shifts. A generated shift on a preferred day still shows the heart
• On an empty day, the ban icon marks one-time unavailable (PTO) and the heart marks preferred
• The empty-cell top-right sync is gone. Sync is only on a preferred, unavailable, or scheduled cell — never a one-click “create unavailable” from a blank day. To repeat weekly, hover that cell and click its top-right sync icon

Drag a Shift to Another Driver or Day

On the weekly grid, drag an existing shift onto another empty cell in the same week to move it.

• Past days cannot be dragged from or dropped onto. Today is allowed both ways
• Dropping on a day that already has a shift does nothing — DailyDSP does not swap two shifts
• A moved shift goes back to draft, so publish again if drivers should see it
• Recurring: only that day’s instance moves. The weekly pattern stays on the original driver and day for future weeks
• Same-cell drop is a no-op. Clicking a shift (without dragging) still opens the editor
• Preset drag onto a cell and template drag onto a driver name still work as before

Shift Labels

Each shift can have an optional short label (up to 36 characters). Occupied cells show it as a compact pill next to the time; hover to see the full name if it is cut off. Leave it blank and no pill appears.

• Set or clear the label in the Create/Edit Shift modal
• Applying a preset (click or drag) uses the preset name as the shift label
• Weekly templates can set a different Label on each enabled day (New/Edit Template). Applying the template puts that day’s label on the shift. The template name is not used as the shift label
• When you Generate a week from repeating shifts, each new day keeps the same label. A blank label stays blank
• Moving or editing a shift without changing the label leaves the label in place. Editing the label on a still-recurring instance updates later generated weeks

Click, Right-Click, and Mass-Clear

Clear many shifts at once after a warning confirmation that names the scope. Cancel leaves the schedule unchanged. Weekly templates, presets, and repeating-shift blueprints (the sync icon on a scheduled shift) are not removed — Clear only deletes this week’s shifts.

Reliability Cues on Driver Names

Each driver name in the left column is pastel-shaded from that driver’s last 90 days of attendance: late arrival warnings, late load-outs, call-outs, and NCNS combined. A note under the name shows N events · 90d.

• 0 events — green; 1–2 — yellow; 3–4 — orange; 5+ — stronger red
• Left-click the name to open the same four reliability cards the driver sees in the portal (14 / 30 / 90-day chips)
• Right-click the driver name to Copy previous week (that driver only) or Clear driver week

Schedule Column Actions (Per-Day Quick Actions)

Click any day's column header in the weekly grid to open a quick-action menu. The menu adapts to the day's state (template available, routes already created, etc.):

Reusing Templates

Keep named templates (for example “Full Time AM”) and drop them onto drivers whenever you build a new week. You can also use the column-header Apply Template action for a single day.

Amazon Variance Tracking

Compare your DailyDSP schedule against Amazon's expected roster to catch mismatches before they become problems.

Overview

Performance is in the top nav after Schedule. Upload the weekly Amazon DSP scorecard PDF(s) for your delivery station(s). The page is independent of Schedule’s week picker and does not change the driver portal’s week.

• Scorecard history at the top counts every uploaded week: Fantastic Plus (green), Fantastic (yellow), and Good and below (red), using Amazon’s printed Overall Standing line
• This week’s scorecard follows Amazon’s sections: Safety and Compliance, Delivery Quality, Pickup Quality (when Amazon prints it), and Team and Fleet
• Sections start collapsed — you see the section name and its overall rating. Tap the header (or the chevron) to show metric ovals; tap again to hide them
• The first time you open Performance, a short guided tour highlights the main controls (same Page tutorials toggle as the other screens)

Uploading Scorecard PDFs

1. Go to Performance
2. Upload one or more Amazon scorecard PDFs — pick several files, or drop a folder of weeks. DailyDSP saves them one after another and lists which files saved
3. Multi-station DSPs keep one scorecard per delivery station for the same week. DailyDSP reads the page-1 header (for example ABCD at DDC4) so uploading DDC4 does not overwrite ABE2

Station Pills & Week Selector

Station pills sit to the left of prev / week / next / This Week. Tap a station to see that site’s metrics for the selected week. One station still shows its code.

• Prev / next / This Week step through uploaded scorecard weeks only. This Week is the latest upload
• Changing week keeps the last station if that week has it; otherwise it opens the first station available
• This cursor is not Schedule’s week and does not change Schedule or the driver portal

Scorecard load history at the bottom lists each upload’s week, station, status, and date/time.

Sectional Ovals & Amazon Standings

Each metric is a rounded oval, not a stop-light. The heading is Amazon’s printed standing — never a generic “below Fantastic”:

Fantastic, Great, Fair, Poor, Fantastic Plus, Coming Soon, Compliant, and Week 9 BoC Non - Compliant (Amazon’s spacing around the hyphen).

Tap the i on a metric and the Appendix A explanation renders above the page (not inside the oval), so the full text stays visible.

• DSB goal is 0 — any event is yellow when Amazon still printed Fantastic, red if the standing is not Fantastic. DSB covers six DA-controllable behaviors: simultaneous deliveries, delivered >50 meters, inaccurate scan (unattended), inaccurate scan (attended), No-POD, and scanned-not-delivered-not-returned
• Safe Driving is station-wide on Performance only. Coming Soon is a clean green oval. It is not on the driver Scorecard

Breach of Contract & Comprehensive Audit (CAS)

Safety and Compliance includes Breach of Contract (BoC) and Comprehensive Audit (CAS) ovals. Headings use Amazon’s printed wording.

• Compliant is green. Non-Compliant is red
• Tap i for the Appendix A explanation: a BoC notice makes Compliance and Overall Standing Poor; Non-Compliant CAS blocks Fantastic / Fantastic Plus overall
• BoC and CAS are station-wide on Performance only — they do not appear on the driver Scorecard pill

Driver Scorecard (portal)

The driver portal’s Scorecard pill uses that driver’s Current Week Performance row, matched only by Amazon transporter ID (never by name). Ovals stay compact and already expanded. Coaching colors follow that driver’s numbers. See Driver Portal.

Upload Baseline

The fastest way to load a roster is Amazon’s driver baseline file. On the Drivers page, click Upload Baseline, then use Preserve Local Values so curated phones and fuel PINs survive a re-import. See Smart Imports.

Adding a New Driver

1. Navigate to Drivers
2. Click Add Driver
3. Fill in the required fields:
   • First Name and Last Name
   • Phone Number (with country code)
   • Email (optional)
   • Transporter ID — Amazon’s TID (unique per location)
   • SMS Language — English, Español, or Français
   • Certifications — CDV, DOT, Electric (used when auto-assigning vans)
4. Set the driver's Status (Active / Inactive / Terminated)
5. Click Add Driver

Transporter ID (TID)

Amazon assigns each driver a Transporter ID. DailyDSP matches Cortex routes, Amazon schedule files, baseline imports, and Performance scorecard rows on TID first; names are only a fallback (Scorecard never matches by name).

• Keep the ID exactly as Amazon has it. A mismatch is the usual reason a Cortex row shows as unmatched
• Amazon sometimes re-issues a TID (account reset, rehire). You can update it on the driver so the unique ID stays in sync
• TIDs must be unique within your location

SMS Language

On each driver’s profile, set SMS Language to English, Español, or Français. Dispatch, reminders, scheduled messages, and AI replies go out in that language. Dispatchers still see the original plus an English translation in Messaging. See Multi-Language.

Driver Status

Phone Number Format

For SMS to work correctly, phone numbers must:

• Include country code (e.g., +1 for US)
• Contain only digits after the country code
• Be a mobile number capable of receiving SMS

Upload Baseline

Click Upload Baseline on the Vehicles page to import Amazon’s vehicle file (fleet IDs, VINs, service types). Re-imports can preserve local edits. See Smart Imports.

Adding a Vehicle

1. Navigate to Vehicles
2. Click Add Vehicle
3. Enter the VIN — DailyDSP auto-fills Year, Make, and Model via NHTSA VIN decoding
4. Fill in remaining details:
   • Vehicle ID — your internal identifier (e.g., VAN-001)
   • Service Type — Amazon or custom type (must match the route for auto-assign)
   • License Plate
   • Certification Class — optional CDV / DOT / Electric restriction
   • Service Status — In Service, Out of Service, or Maintenance
5. Click Save

Service Types

Amazon service types (for example “Standard Parcel - Large Van”) are discovered from Cortex and vehicle baseline imports. Every location on DailyDSP shares that Amazon list so a new DSP is not staring at an empty dropdown. You cannot invent Amazon types — they only appear when an import sees them.

Custom types are extra names for your location only (training, charter, nursery, and so on). They never show up in another DSP’s dropdown.

• Create one from a Type dropdown (Add custom type…) on Dashboard, Vehicles, or Schedule, or from Settings → Routes → Custom service types
• Remove a custom type from that Settings list (×). Historical routes keep the old name; it just leaves the dropdown
• Amazon types cannot be deleted

Custom types are added to the Ignored Service Types list by default so they do not fire the dashboard route/vehicle mismatch warning. Remove a name from that ignore list if you want the warning. Assign the same custom type on both the route and the van if you want auto-assign to match them.

Vehicle Status vs Service Status

Each van has two independent flags:

Auto-assign only considers vans that are Active and In Service.

Overview

The Maintenance Kanban board gives your team a visual way to track vehicle maintenance tasks through their lifecycle. Each task is a card that moves through columns as work progresses.

Kanban Columns

Cards flow from left to right as maintenance tasks progress:

Creating a Maintenance Card

1. Click Add Card in any column
2. Fill in the card details:
   • Title — e.g., "Oil Change - VAN-012"
   • Vehicle — select from your fleet
   • Type — Oil Change, Tire Rotation, Inspection, Repair, etc.
   • Description — additional details or notes
   • Due Date — when it needs to be completed
3. Click Create

Moving Cards

As maintenance progresses, drag cards between columns:

• Drag and drop a card from one column to another
• Cards maintain their position within columns
• All team members see card movements in real time

Card Comments

Add comments to cards for team collaboration:

1. Click on a card to open its detail view
2. Type your comment in the comment box
3. Click Add Comment
4. Comments show the author name and timestamp

What is Affinity?

Driver-Vehicle Affinity allows you to set preferred vehicle assignments for each driver. When you use Auto-Assign Vehicles, the system uses these preferences to make intelligent assignments.

Affinity Levels

Setting Up Affinity

1. From Vehicles, click Affinity
2. Each van has primary, secondary, and tertiary driver dropdowns — save as you go
3. Optional toggles at the top:
   • Prior Day Affinity — prefer yesterday’s van when affinity is empty
   • Prior Day Precedence — try yesterday’s van before affinity
   • Strict Service Type Match — auto-assign refuses any van whose Amazon service type does not match the route (manual assignment is unaffected). Types on Ignored Service Types skip this gate so affinity or any available van can still be assigned

Auto-Assignment Logic

When you click In-Service Vans (auto-assign) on the Dashboard:

1. Only vans that are operational and In Service are eligible
2. Driver certification must match the van’s class (CDV / DOT / Electric) when a class is set
3. Affinity (and optional prior-day van) is tried first, then a service-type match, then any remaining eligible van
4. With Strict Service Type Match on, every pick must match the route’s service type or the route is skipped — except routes whose type is on Ignored Service Types (Settings → Routes), which get any available van
5. Routes with no service type (backup rows) are not auto-assigned a van

Overview

The Driver Portal is a mobile-friendly web app that drivers open from a unique link (SMS or dispatcher send). No App Store, no Google Play, no DailyDSP login, and no Help Chat. Drivers bookmark the link and they're ready to go.

• No app required — works in Safari, Chrome, or any mobile browser
• Three pills at the top: Schedule, Reliability, and Scorecard (the Scorecard pill always says Scorecard)
• Schedule — live week, confirm shifts, availability, marketplace, today’s route
• Reliability — 14 / 30 / 90-day attendance counts
• Scorecard — that driver’s Current Week Performance from uploaded Amazon PDFs, matched by transporter ID only
• Works on any device — iPhones, Android phones, even older models

Driver Access

Each driver gets a unique portal link for your location (for example a /my-schedule/… token in an SMS). They tap it, bookmark the page, and return with one tap. On Schedule, left-click the Driver heading to send the portal link to every driver on the grid (it asks first with a count). Right-click that heading for copy / clear / send portal.

Three-Pill Carousel

A three-pill control sits under the greeting. The center pill is the current view; tap the left or right pill to rotate to that neighbor. The cycle wraps: Schedule ↔ Reliability ↔ Scorecard.

• The top pills always read Schedule, Reliability, and Scorecard — the Scorecard label never becomes “Scorecard Performance”
• Prev / next / Today on Schedule or Scorecard change the week only and stay on the same view. Only the pills switch between Schedule, Reliability, and Scorecard
• Reliability has no week controls — it always uses rolling 14 / 30 / 90-day windows

Schedule

Drivers see their upcoming shifts in a clean, mobile-optimized view:

• Current week displayed with shift times and types
• Color-coded by shift preset (Morning, Mid, Evening)
• Prev / next / Today to view other weeks
• Off days shown clearly so drivers know their full schedule
• Confirm shifts, set availability, and use the marketplace (give up / pick up)

Reliability

Four cards, each with 14-day, 30-day, and 90-day counts from the driver’s real route attendance (tenant timezone, rolling calendar days):

Call-out and NCNS days are not also counted as tardy. Count chips share one heat scale on every card: 0 green, 1–2 amber, 3–4 orange, 5+ red.

Scorecard

The Scorecard pill shows that driver’s Current Week Performance numbers from the Amazon DSP scorecard PDFs you uploaded on Performance.

• Matched only by Amazon transporter ID — never by name. If the driver has no TID, Scorecard stays TBD rather than guessing another DA
• If that TID is not on any station’s table for the week, DailyDSP uses the first station alphabetically
• Safety and Delivery Quality ovals only — already expanded. Breach of Contract, Comprehensive Audit (CAS), Safe Driving, Team, and Pickup stay on the dispatcher Performance page
• Oval headings use Amazon’s printed standing when the PDF has it. Coaching colors follow that driver’s rates, not station totals
• Weeks with no upload, or a week where that TID is not in the table, show TBD / empty

Shift Marketplace

The marketplace lets drivers manage their availability from the Schedule view:

Today's Route Info

On dispatch day, drivers can see their assignment details on Schedule:

• Route number — Amazon route code
• Vehicle — assigned vehicle ID
• Wave time — scheduled departure
• Staging location — where packages are staged

What Is the AI SMS Agent?

The AI SMS Agent is an intelligent assistant (powered by Google Gemini via LiteLLM) that responds to inbound driver text messages. Instead of rigid keyword-based check-ins, drivers can text naturally and get accurate, conversational responses — in their own language.

• No app required — drivers use their normal SMS
• Multi-language — auto-detects the driver's language and replies in kind (English, Spanish, and more via Google Cloud Translation)
• Context-aware — knows the driver's schedule, route, vehicle assignment, availability, and shift marketplace state
• Multi-turn memory — remembers the last 4 exchanges with each driver for 30 minutes, so follow-up texts make sense
• Check-in automation — recognizes arrival confirmations ("here", "arrived", "aquí") and logs them automatically
• Rate-limited — 20 messages/hour per driver to prevent abuse or runaway loops

What the Agent Can Do

The AI Agent uses a structured tool-calling pattern. Each tool is a specific capability backed by live DailyDSP data:

Example Conversations

Viewing Conversations

All AI conversations are logged and visible to dispatchers:

1. Navigate to Messaging and turn Log Mode off for Conversations
2. Each driver who has SMS appears once — click them to see the full thread, oldest to newest
3. Inbound messages (from driver) and outbound messages (from AI or dispatcher) are shown in a chat view, with the original-language transcript and an English translation side-by-side
4. Compose in the box under the thread and click Send to take over from the AI — the agent automatically steps back for the rest of the thread

How It Works

• When a driver texts your DailyDSP number, the inbound webhook routes to the AI agent
• The agent looks up the driver's identity, language preference, and live data (schedule, route, vehicle)
• It selects the appropriate tool (or chain of tools, up to 5 turns) and generates a natural reply
• The reply is translated into the driver's language if needed, then sent via SMS
• If the AI can't answer or detects an out-of-scope request, the message is flagged for dispatcher review
• The agent respects tenant messaging_mode — test-mode tenants don't engage real drivers

SMS Configuration

DailyDSP uses Twilio for SMS messaging. Your administrator will configure:

• Twilio Account SID
• Twilio Auth Token
• Sending phone number

Log Mode vs Conversations

Messaging has a Log Mode toggle.

In Conversations:

• Type in the box under the thread. Enter starts a new line. Click Send (or Ctrl/⌘+Enter) to text that driver
• Replies show up in the same thread without leaving the page (the list and thread refresh about every 5 seconds)
• The compose box stays on screen while a conversation is open. Send is disabled with a reason if the number is not linked to a driver, or if they opted out of SMS
• Threads still show the original-language text plus an English translation, same as Log Mode

Message Templates

Customize the messages sent to drivers. Variables use single curly braces and are substituted at send time with the driver's live data. The Send Message dialog also includes a clickable pill list so you can insert any variable without remembering its exact name.

Example Template

Multi-Language Auto-Translation

DailyDSP can automatically translate outbound SMS into a driver's preferred language. The translator protects template variables — so {driver_name} and other placeholders survive translation untouched and still resolve to live data at send time.

• Compose once in English — DailyDSP translates per-driver based on their language preference (Spanish is the most common; other languages supported via Google Cloud Translation)
• Variable-safe — placeholders are wrapped in notranslate markers, so they're never mangled
• Auto-detect inbound — when a driver texts in Spanish, the AI SMS Agent replies in Spanish automatically; the dispatcher always sees an English transcript alongside
• Fail-open — if the translation service is unavailable, the original English message is delivered (drivers never get a blank text)

Quiet Hours

Configure quiet hours on a per-tenant basis to suppress non-urgent SMS during specific windows. Scheduled messages and reminder workers respect these hours; any message due during quiet hours is deferred until the window closes.

1. Go to Settings → Messaging
2. Set Quiet Hours Start and Quiet Hours End (24-hour HH:MM, tenant timezone)
3. Leave blank to disable quiet hours entirely

Test vs. Production Messaging Mode

Every tenant has a messaging_mode setting that controls where outbound SMS actually goes:

Sending Messages

1. From the Dashboard, select routes (or select all)
2. Click Send Messages
3. Review the message preview
4. Click Send
5. Monitor delivery status in the Status column

Troubleshooting Messages

You’ll see the same red failure labels on Messaging, Message Log, Dashboard route SMS status, and send results.

The Four Reminder Workers

Configuring the Workers

1. Go to Settings → Reminders
2. Toggle each worker on/off (schedule_confirm_reminder_enabled, late_checkin_alert_enabled, giveup_commit_reminder_enabled, pickup_reminder_enabled)
3. Set the interval (in hours) for each — clamped to 1–168 hours
4. Set the late check-in threshold (checkin_warning_minutes) — default 10 minutes before wave

What Reminders Respect

• Quiet hours — messages due during quiet hours are deferred until the window closes
• Messaging mode — test-mode tenants route all reminder SMS to your configured test_phone_number, never to real drivers
• Driver language — reminders are auto-translated if the driver's profile specifies a non-English language
• Custom templates — if you have a "Shift Reminder" message template, the workers use it; otherwise a sensible default is sent

Creating a Scheduled Message

1. Go to Messaging → Scheduled
2. Click New Scheduled Message
3. Pick a recipient:
   • Driver — single driver lookup
   • User — internal ops user (e.g., yourself)
   • Day-of-Driver — whoever is assigned the route on the send date (great for "see you tomorrow!" templates)
4. Pick a template (or compose ad-hoc text). Variables substitute live at send time, not at create time, so {driver_name} always resolves to whoever the recipient turns out to be.
5. Set Send At (date + time, in tenant timezone)
6. Click Schedule

Maintenance Card Notifications

When you create or edit a maintenance Kanban card, you can attach a scheduled SMS to it. The card becomes the "source of truth" for the message — moving the card's due date or canceling the card updates the linked scheduled message automatically.

1. Open a Kanban card
2. Click Notify Driver/Vendor
3. Pick recipient type, write the message (with optional {timing}, {vehicle}, {driver_name} variables), set the send time
4. Save the card — the linked scheduled message is created

Monitoring Scheduled Messages

The Scheduled Messages page lists every pending and recently-sent message with status (pending, sent, failed, cancelled). Edit any pending message before it goes out, or cancel one outright.

How It Works

• Outbound: Every driver has SMS Language on their profile (English, Español, or Français). When DailyDSP sends them an SMS — dispatch, reminder, scheduled message, AI agent reply — the message is translated into that language before delivery.
• Inbound: The AI SMS Agent auto-detects the language of inbound texts and replies in kind. Spanish in, Spanish out. English in, English out.
• Translation provider: Google Cloud Translation API v2. Languages supported include English, Spanish, French, Portuguese, Haitian Creole, Vietnamese, and dozens more.
• Variable-safe: Template placeholders like {driver_name} are wrapped in notranslate markers before translation, so they survive untouched and resolve to live data after.
• Fail-open: If translation fails or the API is unavailable, the original English message is delivered. Drivers never see a blank text.

Setting a Driver's Language

1. Go to Drivers and open the driver's profile
2. Set SMS Language (English, Español, or Français)
3. Save — every future message to this driver is auto-translated

Why It Matters

Driver phone numbers are unique across the platform. Without driver-confirmed transfers, anyone could "steal" a driver by typing their phone into a new DSP's roster. DailyDSP closes that hole — the driver must say YES before any messages route to the new DSP.

The Flow

1. New DSP adds the driver by phone number
2. DailyDSP detects the phone belongs to an existing driver at another DSP at the same station — and creates a pending transfer
3. The driver gets an SMS: "Do you want your DailyDSP messages to go to [NewDSP] or stay at [CurrentDSP]? Reply YES or NO."
4. The driver's reply is parsed for YES/NO/unclear
5. YES → driver is re-homed to the new DSP. NO → no change. Unclear → counted; after 3 unclear replies, the transfer is abandoned.
6. Until the driver replies, all SMS keep routing to the original DSP — no surprise re-routing.

Managing Pending Transfers

• The dashboard shows a pending transfer banner with the driver's name and time since SMS was sent
• One-click Resend SMS if the driver didn't get the first one
• One-click Cancel Transfer if you no longer want to claim the driver
• Transfers auto-expire after 14 days of inactivity

Overview

• DSP-Posted Open Shifts — shifts you publish to the marketplace, available to any qualified driver
• Giveup Shifts — shifts assigned to a driver who released them; appear in the marketplace once approved
• Driver Self-Service — drivers see the marketplace in their portal and request pickups with one tap
• Manager Approval (optional) — set whether pickups need ops approval or auto-approve

Giveup Flow

1. Driver opens their portal and taps Give Up Shift
2. (Optional) Add a reason
3. If your tenant requires approval, the request lands in Schedule → Giveups for review
4. Once approved, the shift moves to the marketplace as a giveup shift
5. Other drivers receive a pickup-reminder SMS (if the reminder worker is on)
6. The giving-up driver is reminded to confirm via the Giveup Commitment Reminder until the shift is picked up or auto-cancelled

Pickup Flow

1. Driver opens Available Shifts in their portal
2. Browses open and giveup shifts with times and service types
3. Taps Pick Up
4. Pickup is auto-approved or routes to ops for review based on tenant policy
5. Approved pickup is added to the driver's schedule and removed from the marketplace

Policies & Limits

Supported File Types

Amazon Daily Dispatch

On Dashboard → Routes, DailyDSP auto-detects Daily Dispatch vs Cortex. There is no format picker.

• Station and date come from the workbook (Summary + station sheet). Upload routes shows a Daily Dispatch banner. Cortex still uses the filename; if that name cannot be parsed you enter them yourself
• Import Complete labels whether station/date came from the filename, the workbook, or what you typed
• Vehicle matches Amazon Fleet ID. Blank Route rows are skipped. Staging is already in the file — guided workflow skips Staging after a successful Daily Dispatch import

Preserve Local Values

Re-imports never silently overwrite your edits. DailyDSP shows a "Preserve Local Values" picker before committing — you choose, field by field, whether to keep the local version or accept the incoming version.

• Most common use: keep your hand-curated phone numbers and fuel PINs across re-imports
• You can also choose "preserve all" or "overwrite all" with one click
• Notices in the import results call out exactly which fields were preserved per row

Per-Row Error Reporting

Bad rows are reported individually — they don't nuke the whole batch. Common issues DailyDSP handles gracefully:

• Blank Route rows on Daily Dispatch — skipped so they do not create empty routes
• Blank cells in required columns
• Empty trailing rows in spreadsheets
• Numeric phone numbers parsed as floats (Excel's favorite trick)
• Missing driver matches — shown as "unmatched" with a one-click resolution
• Driver Transporter ID re-issues — DailyDSP matches by name fallback so the same driver gets re-linked even with a new TID

Service Types on Import

Amazon service-type names discovered from Cortex and vehicle baselines are shared across every location, so a new DSP is not staring at an empty Type dropdown. Custom types you add in Settings or from a dropdown stay on your location only and never leak to another DSP. See Vehicle Management.

NHTSA VIN Decoding

When importing or adding vehicles, paste the 17-character VIN and DailyDSP auto-fills Year, Make, and Model from the NHTSA database. No manual entry needed.

Role Hierarchy

Inviting a User

1. Go to Settings → Users
2. Click Invite User
3. Enter a phone number (10+ digits, normalized automatically) and pick a role
4. Click Send Invite — DailyDSP texts the registration link immediately

Slack community

After someone finishes registration — or you approve a pending account — DailyDSP does not text a shared Slack join link. If the account has an email, DailyDSP texts that a Guest invite is coming — check email for the invite. Registration still succeeds if there is no email (the Slack path is skipped).

• DailyDSP does not auto-join anyone. Ops send a Slack Guest invite from Slack.
• Ops managers, dispatchers, and viewers are invited to #support only.
• Owners are invited to #support and #dsp-owner-chat.
• Drivers are not invited this way. They keep using SMS and the driver portal.
• Existing operators may get a one-time text the same way. DailyDSP does not keep re-notifying after that.

Resending or Revoking Invites

• Resend — if the original SMS didn't arrive or expired, click Resend to issue a new link
• Revoke — cancel a pending invite at any time; the token becomes invalid immediately
• Inviting the same phone twice automatically revokes the previous pending invite, so there's never a duplicate-link ambiguity

Safety Rails

• You can't deactivate the last active owner — there must always be one
• Ops managers can't elevate themselves or other ops managers to owner
• Deactivation is soft (account hidden) — audit logs preserve the user's history

General (per user)

Messaging Settings

Check-In Thresholds

Reminder Workers

Each worker has an enabled flag and an interval setting. See the Automatic Reminders section for details.

• schedule_confirm_reminder_enabled / _hours
• late_checkin_alert_enabled
• giveup_commit_reminder_enabled / _hours
• pickup_reminder_enabled / _hours

Amazon Reconciliation

Routes — Custom Types & Ignore Lists

In Settings → Routes you manage names that only exist at your location, and which dashboard warnings to skip.

Click Save Changes after editing an ignore list. Removing a custom type only drops it from dropdowns — existing routes, vans, and shifts keep the old name.

Portal URL

If your tenant has a custom subdomain (e.g., plad.dailydsp.com), set portal_base_url to the full URL — DailyDSP uses it to generate invite links and SMS portal links for that tenant. Without it, links fall back to the platform default.

Where it is

In the header, next to the question-mark Help icon, click the comments button (Ask DailyDSP). The question-mark still opens this Support page for the current screen. Help Chat does not replace it.

Owners, ops managers, dispatchers, and viewers all get the same chat, including feature requests and Contact support. Drivers use SMS and the driver portal instead.

What it answers

• How-to questions grounded in these Support docs and What’s New
• It knows which screen you are on (Dashboard, Schedule, Performance, Vehicles, …)
• Links back to the matching section on this page

It cannot see your routes, drivers, vehicles, or live board. Questions like “why is this route red?” belong on the Dashboard, not in chat.

Contact support

For something that is broken or needs a human, use Contact support (header button or chip in Ask DailyDSP). This is separate from how-to answers and from feature requests.

• DailyDSP creates a numbered ticket (YYYYMMDD-NN on the America/New_York calendar day — for example 20260915-01 is the first request that ET day)
• It posts one parent message in Slack #support and shows you the Support ID plus a clickable permalink to that thread so you can add updates there
• If your account has an email, DailyDSP also emails you the same ID and link
• Attach 1–3 screenshots (PNG, JPEG, WebP, GIF) or a short recording (MP4, WebM, MOV), 20 MB each. Preview and remove files before Send. Those files appear as links on the Slack thread

How-to stays in chat. Contact support is the human path. About 5 support requests per calendar day, per person.

Feature requests

Ask for something DailyDSP does not do today, or tap the “Send a feature request” chip. We review every request. There is no ship date — sending a request is not a promise it will be built.

About 20 chat messages per hour and 5 feature requests per calendar day, per person. English only.