Follow-the-Sun Support: How inDrive Cut Incident SLA from 72 Hours to 2 Hours
Real SLA numbers, the legal quirks of hiring in Brazil, and a follow-the-sun rotation that actually works for 24/7 incident support.
TL;DR
- Problem: A 3-person incident support team on a 5/2 schedule in Kazakhstan had a 72-hour SLA — anything filed after hours or on weekends waited until Monday.
- Solution: A three-country follow-the-sun rotation (Kazakhstan → Brazil → Malaysia), built without any night shifts.
- Result: SLA dropped to 2 hours for normal-priority tickets and 1 hour for critical incidents, with full 24/7 coverage.
- Bonus: What Brazilian labor law (CLT) requires you to know before you build a shift schedule there.
The Problem: A 72-Hour SLA and No Night Coverage
Friday, 18:00. The workday ends, the team heads home — and that’s exactly when the app breaks. Users hit a “Failed to load” error when accepting an order. First-line support runs 24/7 and keeps receiving tickets, but the technical escalation team...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE