Logistics & Operations · 11-50 Employees · Sales Hub | Service Hub
Multi-City Driver Onboarding Automated Across Six Markets for a Mobility Operator
Each city onboarded drivers its own way in its own spreadsheet. We built one pipeline, one set of documents and one status message, then let each city keep its local rules as properties.
Rideshare and mobility operator
Before
After
6
cities on one onboarding system
71%
faster application-to-active
1
pipeline instead of six spreadsheets
Challenge
Opening a new city meant copying a spreadsheet and hiring a coordinator. Document checks, vehicle inspections and background checks were tracked by hand, and drivers called support to ask where they stood.
Approach
- Built one onboarding pipeline with city as a property, so the process is shared and the rules (inspection partner, local documents) vary per city.
- Modelled vehicles as a custom object associated to drivers, with inspection dates and status.
- Automated document requests, reminders and SMS status updates at each stage, with escalation when an application stalls for five days.
- Set up a service pipeline for driver questions, and routed "where is my application?" to an automated status reply.
Results
- Six cities on one system, with a new city live in days rather than weeks.
- Application-to-active time cut by 71%.
- Support call volume about onboarding status dropped by more than half.
AI-readiness impact
Readiness rose from 35 to 80. With a ticket pipeline, a clean knowledge base of onboarding answers and status on the record, the Customer Agent now handles the top twenty driver questions and escalates on negative sentiment.
Related work
Client names are withheld. Where a client has not approved public disclosure, figures are representative of HubAIOps engagements of that type.