Salem Skipper · Dispatch & City Console
Operations, reporting, and compliance for RFP 27-12-TAP
DEMO
One-way trips
433
Round trips
59
Unique passengers
20
New passengers
0
Shared vs private
154 / 279
54% with 2+ riders
Missed / declined / cancelled
13 / 10 / 58
Avg trip rating
4.77 ★
Revenue miles
583
431 non-revenue mi · 23h idling
Complaints
8
avg resolution 14.1h
Crashes
0
Avg call response
2.5 min
Avg email response
132 min

Trip-route heat map

Salem Harbor

Line weight = trip volume between stops during 2026-08.

Wait-time breakdown

  • 0–5 min
    36 (8%)
  • 6–10 min
    143 (33%)
  • 11–15 min
    133 (31%)
  • 16–20 min
    121 (28%)
  • 20+ min
    0 (0%)

Top origin → destination pairs

  1. Salem State University — North Campus → Highland Ave Shopping (Market Basket) · 5
  2. The Point (Congress St) → Highland Ave Retail (Walmart) · 5
  3. Salem Depot (MBTA Commuter Rail) → Highland Ave Shopping (Market Basket) · 4
  4. Highland Ave Retail (Walmart) → Salem Willows Park · 4
  5. Salem Common → Peabody Essex Museum · 4
  6. Shetland Park → North Street (Mason St) · 4

🎙️ "Talk to Skipper" AI assistant usage

Every assistant turn is documented (question, answer, topic). The rider always confirms bookings on a fare card; the assistant never books on its own.

No assistant conversations recorded yet.

This dashboard is the City's backend view (RFP Reporting & Data). All metrics export to CSV and accompany each monthly invoice; incident-specific detail is available on request. Origin/destination analysis, heat map, wait times, ratings, complaint SLAs, crash reports, and non-revenue miles/idle time are computed from raw trip records — the same records the City may audit under §5.4 Access to Records.