Insights / Keep it working

Measure the response that actually helps.

Measure how long a customer waits for a response that addresses their request. Keep automatic acknowledgements, working-hour rules and missing records separate.

By JetSynapse AI · Practical guide · Illustrations are fictional

Define “response” before timing it

An acknowledgement says a request arrived. A meaningful response answers the request or asks for the information needed to move it forward. A completed resolution is another milestone again.

Choose the event you want to improve before comparing times. A faster acknowledgement does not necessarily mean a faster useful answer. Document whether your measure counts elapsed time or only staffed business hours.

Work through one example

Fictional example: an inquiry arrives Friday at 4:50 p.m. An automatic acknowledgement goes out at 4:51 p.m. The office closes at 5 p.m., opens Monday at 9 a.m., and a team member gives a useful reply at 9:20 a.m.

The acknowledgement took one minute. The meaningful reply took 64 hours and 30 minutes of elapsed time, or 30 staffed minutes under that schedule. Both measures can be correct; they answer different questions. State the schedule, time zone and any excluded holidays beside the result.

Calculate a single staffed interval

This small calculator is for two times on the same staffed day. It does not exclude breaks, holidays or overnight hours. It calculates the interval from the two times you enter.

Example: 09:10 to 09:42 is 32 minutes.

Describe the missing records

If you can time only eight of ten inquiries, report “eight timed records; two missing response evidence.” Do not assign zero minutes to missing data or silently remove unanswered requests. Identify duplicates and use the same counting rule across periods.

For a small set, show the individual intervals and the count. A median can describe a typical recorded wait; it does not describe the requests you could not measure. Compare like periods and the same definition before interpreting a change.

Review the response evidence.

A quick median can hide the inquiries still waiting. This educational worksheet keeps recorded response times, known unanswered inquiries and unresolved evidence together.

Use one review period, one cutoff and one definition of a meaningful response. Count each eligible inquiry once. An automatic acknowledgment is not a meaningful response.

Enter minutes and counts only; keep customer information in your approved workspace. This worksheet does not check your records or connect to your customer account.

A worked example, with or without the calculator

Fictional review: 10 eligible inquiries. Eight recorded elapsed intervals: 1, 3, 5, 8, 12, 20, 40 and 90 minutes. One inquiry is known to be awaiting a meaningful response; one has unresolved response evidence.

Coverage is 8 of 10. The sorted middle pair is 8 and 12 minutes, so the recorded median is (8 + 12) ÷ 2 = 10 minutes.

That median excludes two inquiries without a timed response. It does not describe their waiting time or prove that the process improved.

Method reference: NIST’s explanation of the median. The worksheet’s evidence categories are JetSynapse’s educational approach, not a service-quality score.

Turn the result into a decision

Look for a specific reason a request waited: coverage, unclear ownership, missing information or capacity. Choose one change you can test, then use the same measurement rules next time.

There is no universal response-time promise in this worksheet. Set a realistic service expectation for your business, explain availability accurately and keep the underlying records available to the people reviewing the result.