A repair shop sets up QodFlow. They put SLAs on every stage. Diagnostic: 1 day. Awaiting Parts: 3 days. In Repair: 2 days. Quality Check: 1 day. Ready for Pickup: 7 days.
Six weeks in, the dashboard says everything is green. Customer complaints are up 20%.
Where the clock actually starts
The customer's clock starts when they walk into the shop with their broken thing. Yours starts when someone moves the ticket into "Diagnostic." Those are often 4-8 hours apart, and sometimes a whole day.
The customer dropped off the laptop at 9am. The intake person was busy. They put a sticky note on the laptop. At 4pm somebody finally entered the ticket. The Diagnostic SLA clock starts at 4pm.
From the customer's perspective: they brought their laptop in seven hours ago. Nothing has happened. They're going to call tomorrow morning asking what's going on, and the dashboard will say "Diagnostic — 18 hours remaining, on track." The dashboard is lying.
The fix: an intake stage with a punishing SLA
Add a stage called Intake before Diagnostic. Give it a 15-minute or 1-hour SLA. The job of this stage is one thing: get the device entered into the system as a real ticket with a real owner. Nothing more.
When the intake SLA hits the 30-minute mark, somebody is going to do something about it. The sticky-note pile evaporates. The customer's mental clock and your system clock start within minutes of each other.
This sounds like overhead. It's actually the opposite — it's the cheapest customer-satisfaction win you'll ever ship. Customers who feel seen in the first 30 minutes don't call back to check in. The phone stops ringing.
The other clock mistake: not pausing when you should
The second-most-common mistake: clocks that run while you're waiting on the customer. The job is in Awaiting Parts, but actually it's in "waiting for the customer to authorize the $400 quote." The clock keeps ticking. The job goes red. Everyone's metrics look bad. Nobody's fault.
Every stage SLA needs a pause condition. When the ball is in the customer's court, the clock pauses. When they respond, it resumes. Your team's metrics reflect what your team actually controls.
What good SLAs look like
- Intake — <1 hour. The ticket exists, has an owner, customer has a tracking link.
- Diagnostic — 1 business day. Quote ready.
- Awaiting Customer Approval — paused clock, with a 3-day "follow up" reminder.
- Awaiting Parts — 2-5 days, paused if vendor delay is documented.
- In Repair — 1-3 business days depending on complexity.
- QC — same day. If a job has been in QC longer than 4 hours, something is wrong.
- Ready for Pickup — 7-14 days, then escalate to customer outreach.
The real KPI
Most shops measure "average turnaround time." The number that actually predicts customer satisfaction is time from drop-off to first ticket update visible to customer. Get that under 30 minutes and the rest of your SLAs barely matter.
The clock the customer is watching is not your clock. Until you fix that, no SLA setup will save you from the angry-callback problem.