Small-business outsourcing research

Sampling customer follow-up promise completion

A protocol for measuring whether a small business kept the follow-up window it gave a customer and whether the record shows who owned the next step.

## Question and scope This study asks whether customer follow-up promises were completed inside the stated window and whether the record shows the owner and the next action. It examines the promise and the first documented contact, not customer satisfaction. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Question and scope Set the scope to one queue and one observation window. Record the channels, the promise language, and the staffing pattern in force. If a template changes, separate the periods. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Population and unit The unit is one promise made to one customer for one request. A customer with two separate requests produces two units. Record the promise time, the window, the owner, the channel, and the final state. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Population and unit Include promises still open at the cutoff. Exclude internal reminders that were never communicated to a customer, with a count. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Definitions and measures Define completion as the first documented contact inside the promised window. Separate a completed contact from a resolved issue. A callback can happen on time and still fail to answer the question. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Definitions and measures Measure the time to first attempt and the time to resolution separately. Record late, missed, and unowned promises as distinct outcomes. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Evidence standard Collect the customer message, the promise note, the contact log, and the case record. Mask contact details in the analysis table. If the promise was made by phone, use the call note and record the evidence type. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Evidence standard Do not reconstruct a missing attempt from memory. A blank field is a missing record, not proof that no call happened. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Sampling and collection Sample promises rather than messages. Review every attempt within the selected promise. Stratify by channel and request type if the queues differ. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Sampling and collection Use a random or systematic start and record the rule. Include at least one promise that crossed a weekend or a shift if the population allows. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Analysis and reporting Report the number of promises, the share completed inside the window, the share late, the share missed, and the share unowned. Show the median time to first attempt. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Analysis and reporting Inspect the missed cases. Was the promise unrealistic, the channel wrong, the owner absent, or the record incomplete? The pattern should lead to one change. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Limitations The record may miss a contact through another channel. State the unobserved evidence and avoid treating a missing note as a deliberate failure. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Limitations The study describes one queue during one window. It is not a customer-satisfaction score or a benchmark for another business. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Review and next action Choose one change: a clearer promise template, a shorter default window, a backup owner, or a weekly aging review. Assign the owner and the next sample date. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

## Review and next action Repeat the study after the change and compare the same measures. Close the review when the owner accepts the result and the next check is scheduled. Record the evidence and the next owner before the item leaves the queue. Keep the note factual enough for a later reviewer to continue.

Sources

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