Final verdict from the two threads Reported unsupervised Robotaxi rides: ~172+ Reported remote support interventions: ~12 Of those 12, only 2 were clearly necessary (one trip that wouldn’t start, one routing/drop-off issue). The other ~10 came from a single user who estimated ~20% of his 50+ rides involved “some form of support conversation.” He also noted that support sometimes dialed in unsolicited. That puts the raw intervention rate at roughly 7%. Given that the bulk of the calls came from one person and some were proactive check-ins rather than true interventions, a more realistic figure from this sample is closer to ~5% (or lower). What this implies for scaling Assumptions (deliberately conservative): - Average remote support session lasts ~5 minutes - At maturity, a well-run Robotaxi averages 25–30 rides per vehicle per day At 5% intervention rate and 30 rides/vehicle/day: - 1000 vehicles → ~1500 interventions/day → ~125 hours of remote staff time - Fully manageable with a small, centralized team. Roughly 30 people would be enough. Most rides happen during the day, so the night shift can stay light. Even at the higher 7% raw rate, the workload remains operationally trivial relative to the fleet size. Conclusion The “convenience issues” Elon has referenced are not the limiting factor for wider deployment. The current intervention rate is already low enough that Tesla could scale the fleet significantly without remote operations becoming unmanageable. They are simply choosing not to. They are taking the time to drive that last few percent toward near-zero before expanding aggressively. Having a thousand vehicles instead of a hundred offers them almost no strategic advantage right now. They are not aiming for a thousand. They are aiming for a million, or more...