Small-business outsourcing research
What share of customer complaints wait more than two business days for an owner decision?
A protocol for measuring how long customer complaints wait for an owner decision and which case types account for the delay.

Research question and scope
This protocol asks what share of customer complaints wait more than two business days for an owner decision. The unit is one complaint that reached an owner-approval gate, identified by the case record and the first request for a decision. The study measures the wait, the case type, and the outcome of the decision. It does not judge whether the owner decided correctly or whether the customer was satisfied.
Set the scope to one business, one complaint channel, and one definition of an owner decision. Record the intake form, the escalation rule, and the owner's normal review times. If the business changes the approval limit during the window, analyze the cases before and after the change separately. A lower limit can shorten the wait without improving the queue.
Define the population as every complaint that required an owner decision during the window, including cases later withdrawn or resolved by the customer. Exclude complaints that never reached an approval gate and state that exclusion. Test the definition on two recent cases before collection begins. Record the test so a later reader can see how the boundary was applied.
Definitions that make the measure reproducible
Define the start as the time the case record first shows a request for an owner decision, not the time the customer first complained. Define the decision as a recorded outcome in the case: approved, declined, changed, or sent back for more evidence. A message that says the owner will look at it is not a decision. Record the time of the decision and the person who made it.
Measure business days using the business's published calendar and exclude weekends and stated holidays. Record the exact timestamps so a reader can recompute the interval. If a case crosses a holiday that was not published in advance, report the interval both ways. A definition that changes with the calendar is hard to compare across months.
Record the number of follow-ups sent while the case waited. A case that waited because nobody asked is different from one that waited after three reminders. Note the channel used for each follow-up and whether the owner acknowledged it. This detail separates a queue problem from a notification problem.
Evidence standard and data dictionary
For each complaint, capture the case number, the customer segment, the order or service, the complaint type, and the requested remedy. Add the amount at issue, the approval limit, and the owner role. Record the request time, the decision time, and the outcome. Keep the case notes and the decision message linked to the record.
Capture whether the case needed more evidence before a decision and who was asked to provide it. A case that waited on the customer is not the same as a case that waited on the owner. Record the date the evidence arrived and the date the owner reviewed it. Report the two waits separately so the fix lands in the right place.
Record the reason for the delay when it is documented: owner travel, missing evidence, a policy question, or a system outage. Do not guess a reason from the tone of the messages. If the reason is unknown, mark it unknown and keep it in the count. A guessed reason can make a staffing problem look like a customer problem.
Sampling and collection
Collect every complaint that reached an approval gate in the window, or a random sample drawn from the case system with the sampling method recorded. Do not select only the cases the team remembers, because the slow cases are the ones most likely to be forgotten. Record the export date, the filters, and the number of records excluded. Keep the sampling frame with the export so the denominator can be rebuilt.
If the business has several owners or queues, collect each separately and record the owner role. A combined rate can hide one queue that holds every case. Report the number of cases and the number of business days behind every percentage. A rate without its denominator is not a finding.
Ask the owner to identify the cases that were urgent under the written rule. Compare the urgent cases with the rest so the reader can see whether urgency changed the wait. Record the rule that was applied. A queue that is fast for routine cases and slow for urgent ones has a different problem from a uniformly slow queue.
Analysis and reporting
Report the median and range of the wait, the share above two business days, and the share above five. Show the results by complaint type, owner, and week. Present the number of cases still open at the end of the window separately. A case with no decision yet is not a fast case.
Compare the wait with the amount at issue and the approval limit. A small case above the limit may wait longer than a large case inside it, which suggests the limit is the problem rather than the owner's attention. Report the pattern without claiming causation. The reader should be able to see which lever would shorten the most waits.
Inspect the cases that waited more than five days and describe the dominant stage without naming the customer. A missing photo, an unclear policy, and an absent owner each point to a different repair. Report the follow-up count beside the wait. A long wait with no follow-up is a queue ownership problem.
Limits of the evidence
The record can show when a decision was entered, but it cannot show when the owner actually thought about the case. A decision entered late may reflect a conversation that happened earlier. The protocol also cannot capture a decision made in a hallway and never recorded, so a missing timestamp may not mean a missing decision. State that limitation before presenting the rate.
A small business may have too few complaints to support a stable rate. Describe the cases and the amounts instead of ranking owners. If the same owner handles every escalation, the result may reflect that person's availability more than the approval design. Do not use the rate as a performance score without the context of leave and case mix.
Do not compare a business that resolves complaints at first contact with one that routes every complaint to the owner. The two have different gates even when the wait looks similar. Report the share of cases that reached the owner and the share resolved before the gate. A target that can be met by never escalating is not a service target.
What to change
Give the result to the owner and the support lead and ask them to choose one observable change. The change might be a daily decision slot, a higher approval limit with a reason code, a named backup, or a required evidence checklist at intake. Record the owner, the effective date, and the measure that will show whether the change worked. Bring the case records to that review so the choice is based on evidence.
If the wait falls but reopenings rise, the cases may be decided too quickly. If the wait falls only for routine cases, the urgent path may still be broken. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.
Ask the owner which case was hardest to decide and what evidence was missing. A concrete answer is more useful than a satisfaction score. Update the intake checklist with the missing item and the owner. The next measurement should test whether that case type waits less.
Sources
- U.S. Small Business Administration, manage your business, U.S. Small Business Administration; checked 2026-11-10
- Federal Trade Commission, data security guidance, Federal Trade Commission; checked 2026-11-10
- U.S. Government Accountability Office, internal control standards, U.S. Government Accountability Office; checked 2026-11-10
- NIST Cybersecurity Framework, NIST Cybersecurity Framework; checked 2026-11-10
Frequently asked questions
Does a favorable sample prove the routine caused the result?
No. The design is observational and supports a bounded operating decision, not a universal causal claim.
What should an owner review first?
Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.
Related research
How often do payroll timesheets reach approval with a missing manager sign-off?
A protocol for measuring how many weekly timesheets reach the pay run without the manager approval the written policy requires.
How often do supplier statements disagree with the accounts payable ledger?
A protocol for counting supplier statement differences by type, amount, and age so the bookkeeping review can target the right fix.
How long does new-client document collection take after the sales handoff?
A protocol for measuring the time from sales handoff to a complete client document file, with stage times and the causes of delay.