The New-Inquiry Handoff Test

1. Trace one inquiry, not the ideal process

Choose a recent inquiry that required more than one person to handle. It might be a website request that became a phone call, a quote that needed a manager's input, or a message received while the usual contact was away. Ask the people involved to reconstruct it together. This is a process review, not a test of individual effort.

Write down five events: arrival, first useful reply, assignment, next action, and final disposition. Use the actual timestamps when available. An automatic acknowledgment can confirm receipt, but record it separately from the first reply that answered a question or moved the work forward. Mark missing evidence as unknown instead of filling the gap with a plausible story.

For each event, note the channel and the record someone would open to understand the situation. Keep the exercise lean: use a reference to the original record rather than copying the customer's message everywhere. The FTC's guidance on protecting personal information recommends keeping only information needed for a legitimate business purpose.

2. Make the next owner visible

At each handoff, ask the receiving person three questions: What did you believe you owned? Where did you see that assignment? What told you when to act? If the answers differ from the sender's, you have a specific place to investigate. A shared inbox gives access to a message; your team still needs an agreement about who will act.

Try a minimal handoff record: inquiry reference, named owner, current status, next action, due time, and backup owner. Add only context necessary for that action. Define what acceptance means. For example, the recipient confirms the assignment in the shared record; until then, the sender remains responsible for arranging coverage.

Example to adapt: A quote request arrives Tuesday morning. Casey owns collecting the missing measurements by Wednesday at noon. Jordan is the backup. The request stays in the shared queue until Casey accepts it, and the next action is visible there rather than only in a private chat.

Check who needs access to that record. The FTC's Start with Security guide advises limiting access to sensitive information to people with a business need. This is not a reason to give everyone access to every customer file.

3. Test the follow-through

Agree on a response expectation that matches your actual staffing, opening hours, and customer promises. There is no universal target in this exercise. Distinguish a receipt acknowledgment, a useful first response, and a completed request. Do not quietly turn a business-hours promise into an around-the-clock commitment.

Then rehearse three exceptions using fictional details: the owner is absent, the customer replies in another channel, and the due time passes without an update. Ask someone other than the original handler to find the next action. If they must interrupt the owner to understand it, note exactly what information or permission is missing.

Choose one change for the next working week. You might add an explicit assignment, a backup rule, or a due-date view in a tool you already use. Review a small sample at the end of the week. Count inquiries with no owner, overdue actions, and repeat requests for the same context. Record the sample size and opening hours so comparisons mean something.

If a customer declines, is outside your service area, or stops replying, record that outcome and any agreed follow-up boundary. An honest closed status is more useful than leaving every unanswered inquiry permanently active. Respect a customer's request to stop contact.

The handoff checklist

• One inquiry can be located without searching private messages.
• A named person has accepted the next action.
• The action and due time are understandable to a teammate.
• A backup knows when and how to take over.
• The customer-facing expectation matches available coverage.
• The final outcome and any follow-up boundary are recorded.

What this test cannot tell you

One inquiry can reveal a gap, but it cannot establish your overall response rate, conversion rate, or financial impact. Repeat the review across different channels and shifts before generalizing. A clearer handoff also cannot create capacity you do not have. If the queue exceeds available staff time, record that constraint instead of assuming another reminder will solve it.

This is Mission Desk's operating exercise, not a certified security assessment or a guarantee of more bookings. For a broader starting point, use the existing 15-Minute Workflow Friction Check.

Primary sources

The linked FTC guides support the information-handling recommendations. The handoff method and example are Mission Desk's own practical guidance, reviewed November 3, 2026.

• FTC: Protecting Personal Information, a Guide for Business
• FTC: Start with Security