Small-business outsourcing research

What share of waitlisted customers are offered a slot within two business days?

A protocol for measuring how many waitlisted customers receive a specific slot offer inside the two-business-day window the shop states.

What share of waitlisted customers are offered a slot within two business days?

Research question and scope

This protocol asks what share of waitlisted customers receive a slot offer within two business days of the request. The unit is one waitlist entry, not one customer and not one sale. The study measures the share offered inside the window, the share offered later, and the entries that never receive an offer. It does not judge whether the customer accepted or whether the item was a good fit.

Set the scope to one shop, one waitlist, and one offer rule. Record the product or service, the store location, and the date the rule took effect. If the shop changes the offer window during the study, keep the original rule for entries already on the list and analyze later entries separately. A new notification channel can change response speed without changing supply.

Define the population as every waitlist entry created during the window, including entries that were withdrawn or duplicated. State any exclusion, such as an internal staff hold, and apply it to every entry. Test the definition on ten closed entries before collection begins. The reader should be able to rebuild the population from the list and the order records.

Definitions that make the measure reproducible

Define a slot offer as the first message that names a specific item or appointment and states how long the hold lasts. A general note that the item is back in stock is not an offer. Define the clock start as the time the entry was recorded, not the time the customer first asked in passing. Record both times when the system supports it.

Define the two-business-day window in the shop's local time and state whether weekends and holidays count. Record the rule that determines offer order, because a list served first in first out will produce different results from one sorted by value. Treat a withdrawn entry as a separate outcome and keep it in the denominator. A definition that removes quiet customers will flatter the result.

Evidence standard and data dictionary

For each entry, capture the entry identifier, the request date, the product, the location, the contact channel, the offer date, and the offer deadline. Add the outcome, the order identifier when one exists, and the staff member who sent the offer. Keep the customer's original request linked to the entry. Record any duplicate request from the same customer.

Capture the reason for a delay when it is documented: no supply, an unassigned owner, a wrong contact number, or a hold that was never released. Do not infer a reason from an empty field. Mark unknown reasons as unknown and report the count. A guessed reason hides the step that actually needs repair.

Sampling and collection

Collect every entry in the window rather than a sample, because the offer rule applies to each one. If the shop runs several locations or product groups, collect each separately and record the group. A combined rate can hide one location that never calls its list. Report the number of entries behind every percentage.

Draw dates from the list and the message log, not from a spreadsheet maintained after the fact. If the message log is incomplete, say so and reduce the claim. Record the export date, the filters, and any entry that could not be matched to an offer. A missing log is itself a finding about the routine.

Analysis and reporting

Report the share offered inside two business days, the share offered later, and the share never offered. Show the median and range of days to the first offer. Present the results by location, product group, and offer channel. Use the same denominator for every rate.

Separate entries that waited because supply was missing from entries that waited because nobody sent the message. An empty shelf is a different finding from an unread list. Report both because they lead to different fixes. A shop may accept a supply delay but should not accept a silent queue.

Limits of the evidence

The list can show that an offer was sent, but it cannot show that the customer received it or understood the hold. A delivered message is not a read message. The protocol also cannot capture a counter conversation that was never logged. State that limitation before presenting the rate.

A small shop may have too few entries to support a stable trend. Describe the entry count and the product mix instead of ranking staff. Do not compare a shop that offers every returned item with one that holds items for the next season. Report the offer rule beside the rate.

What to change

Give the result to the owner and the counter lead and ask them to choose one observable change. The change might be a daily list check, a named offer owner, a confirmed phone number at intake, or a shorter hold window. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions.

If the on-time rate rises but declines also rise, the shop may be offering items that customers no longer want. If both fall but the list shrinks, the team may be removing entries without an offer. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.

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