Published November 4, 2026

A study protocol for checking whether repeat contacts are linked to the original case and resolved without making the customer repeat the story. The notes below keep the customer request, the approved source, and the next owner in one reviewable place. They are written for a support team that may hand the case to another shift. Use the routine to review one ordinary case and one exception before changing the workflow.

Question and scope

This study asks how often a repeat customer contact is linked to an existing case and whether the earlier promise or evidence was carried forward. It examines the case record, not the customer's satisfaction or the agent's effort. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Set the scope to one support queue and a fixed window. Record the channels, the case-linking rules, and the promise fields in force. If the team changes its case system during the period, separate the cohorts. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Population and unit

The unit is one repeat contact tied to one existing customer issue. A customer who contacts twice about two unrelated issues produces two units. Record the case key, the channel, the prior contact, and the new request. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Include contacts that created a new ticket, contacts linked to the old case, and contacts that were closed without resolution. Exclude first contacts with no prior case, with a count. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Definitions and measures

Define a repeat contact as a customer contact about an issue that already has a case record, regardless of whether the agent created a new ticket. Record whether the case was linked, the prior promise, and the first action after the repeat. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Separate a repeated request from a new requirement. A customer who asks for the same refund status is a repeat; a customer who adds a second damaged item is a linked new issue. Report both. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Evidence standard

Collect the case record, the contact log, the customer message, and the promise history. Mask personal details in the analysis table. Use the approved case system rather than a personal inbox. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

If the customer contacted by phone, record the call note and the evidence type. A missing note is a documentation gap, not proof that the customer did not contact the team. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Sampling and collection

Sample repeat contacts rather than all contacts, then review the linked case and the new interaction. Stratify by channel or issue type. Use a random or systematic start and record the rule. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Include a case that crossed a shift and a case that was reopened after a correction. Those cases show whether the handoff preserved the context. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Analysis and reporting

Report the number of repeat contacts, the share linked to an existing case, the share with a preserved promise, and the share that created a new requirement. Show the median time to the next action. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Inspect the unlinked cases. Was the customer using a new channel, the search too narrow, or the case closed prematurely? The pattern should lead to one linking or handoff change. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Limitations

The record may miss a contact through another channel or a conversation that was never logged. State the unobserved evidence and avoid treating every unlinked contact as a failure. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

The study describes one queue during one window. It does not establish a universal repeat-contact target or a customer-satisfaction result. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Review and next action

Choose one change: a required case search, a clearer promise field, a cross-channel link, or a weekly review. Assign the owner and the next sample date. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Repeat the study after the change and compare the same measures. Close the review when the owner accepts the result. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Sources