Published November 4, 2026

A repeat-contact workflow that uses the existing case history, identifies what changed, and avoids making the customer explain the same problem twice. 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.

Open the history before the new ticket

A repeat contact is not a blank request. The customer may have called about the same order, replied to an email, or returned to chat after a promised follow-up. The agent should search the approved case record before creating a new ticket, using the customer's identity and the issue details. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

If a case exists, read the last verified facts, the current promise, and the next owner. Do not copy the old summary into a new ticket and close the old one. Link the new contact to the same case so the timeline remains intact. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

If the customer is contacting through a new channel, record that channel and the reason. A customer who moves from chat to phone may be escalating, or may simply find the phone easier. The record should show the change without treating it as a new problem. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Ask what changed

The agent should ask a short question about what has changed since the last contact. The answer may be a new deadline, a missing refund, a different address, or a response from another team. That one question separates a true repeat from a new requirement. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Do not ask the customer to repeat information that is already verified in the case. Confirm the key facts and ask only for the delta. If the record is incomplete, say which fact is missing and why it is needed. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

When the customer's request has changed materially, create a linked requirement or a new case according to the practice's rule. Preserve the original case and the new request. A changed requirement is not the same as a reopened defect. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Keep the promise consistent

A repeat contact often reveals that the earlier promise was unclear or missed. The agent should find the exact wording, the owner, and the window before making a new commitment. If the promise is still open, do not create a second one that conflicts with it. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

If the promise cannot be met, record the reason and the person who approved the change. Tell the customer before the original window closes. A silent extension makes the first promise look false and gives the next agent no way to explain the delay. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

If the customer asks for a supervisor, record the request and route it through the approved path. Do not promise that a supervisor will call unless the workflow confirms availability. The case should show what the customer asked for and who owns the response. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Separate a new issue from a reopened one

A repeat contact may raise a genuinely new issue, such as a second damaged item or a different billing charge. The agent should record the new issue with its own evidence and owner while linking it to the customer's history. Combining unrelated issues makes the case hard to resolve and easy to misreport. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Use a small status vocabulary: new, reopened, linked follow-up, waiting on customer, waiting on owner, resolved, and closed. The status should describe the next action. A case that is reopened for a new requirement should not be counted as a failed resolution of the original issue. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

If the customer is repeating the same request because the first answer was wrong, treat it as a quality signal. Preserve the first answer and the correction. The reviewer can then see whether the problem was the source, the script, or the handoff. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Review repeat contacts monthly

Sample repeat contacts and compare the first case with the later one. Look for missing evidence, unclear promises, handoffs without an owner, and customers who had to repeat themselves. The pattern may point to a form, a queue, or a training gap. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Report the number of repeat contacts, the share linked to an existing case, and the share that produced a new requirement. Pair the count with the total contacts and the observation window. A raw repeat count without the denominator is not a useful measure. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Choose one change and test it: a required case link, a clearer promise field, a shorter handoff note, or a weekly review of reopened cases. Assign the owner and the next sample date. The goal is continuity, not a lower contact count achieved by closing cases early. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Sources