What 54,000 service calls taught me about running a 24/7 business.
Every call that came into my locksmith and roadside company since 2023 went through software I built, so I can see exactly when people get stuck, what they need, where they are, and what goes wrong.
1. "24/7" mostly means daytime
Everyone in this business sells the 2am rescue. The data says 71% of our jobs come in between 6am and 6pm, and only 3% between midnight and 6am. The busiest stretch is 11am to 1pm, Friday is the busiest day, and 27% of jobs land on weekends. You still answer at 2am, but you staff for lunch hour.
2. Lockouts are the volume. They aren't the business.
Car lockouts outnumber everything else combined, but they're the lowest ticket we sell. The jobs that actually move revenue are keys and batteries. If you only market the thing people search for most, you build a busy company, not a profitable one.
3. One in four jobs cancels
13,711 jobs were canceled after they were created, about 1 in 4 of every job that ended. Each one already cost an ad click and a dispatch. Cancels are a number to manage: answer fast, quote clearly, confirm the address, and charge a fee when a technician is already rolling.
4. Speed is the product
The median time from the call coming in to a technician standing at the car is 41 minutes. Someone locked out doesn't compare prices for long. The company that confirms first and shows up first wins the job, which is why I built auto-dispatch to the nearest technician and a 30-second callback on every web lead.
5. 464 cities, six metros
We've completed jobs in 464 cities, but six metro areas do almost all of the work. Coverage on a map isn't the same as a market. A city only pays when you have technicians close enough to win on speed.
Every city with 100+ completed jobs
| City | Completed jobs |
|---|---|
| Houston, TX | 6,984 |
| Austin, TX | 6,693 |
| San Antonio, TX | 5,486 |
| Las Vegas, NV | 3,482 |
| Dallas, TX | 2,332 |
| Phoenix, AZ | 1,570 |
| San Marcos, TX | 892 |
| Arlington, TX | 641 |
| Fort Worth, TX | 515 |
| Round Rock, TX | 503 |
| Henderson, NV | 443 |
| Kyle, TX | 434 |
| North Las Vegas, NV | 430 |
| Katy, TX | 396 |
| Irving, TX | 377 |
| Spring, TX | 369 |
| Pflugerville, TX | 317 |
| New Braunfels, TX | 308 |
| Corpus Christi, TX | 262 |
| Plano, TX | 250 |
| Humble, TX | 250 |
| Scottsdale, AZ | 222 |
| Cypress, TX | 222 |
| Buda, TX | 210 |
| Grand Prairie, TX | 195 |
| Glendale, AZ | 193 |
| Sugar Land, TX | 176 |
| Tempe, AZ | 174 |
| Cedar Park, TX | 174 |
| Mesa, AZ | 161 |
| Richmond, TX | 159 |
| Converse, TX | 137 |
| Richardson, TX | 126 |
| Missouri City, TX | 126 |
| Pearland, TX | 111 |
| Garland, TX | 105 |
Source: our own dispatch CRM (Phoenix), January 2023 to November 2026. Counts are completed jobs unless noted. Earlier years ran on other software and aren't included.
Want this kind of clarity?
I'll help you read your own numbers and decide what to change first, or build the system that tracks them.
Prefer to text? Same number. I answer my own phone.