Resolution and Reopening

Service Agent records resolution evidence as an event on the assigned ticket. The message should explain what addressed the customer’s problem and give the reviewer enough context to evaluate the outcome. Service Supervisor and the agreed customer policy then determine whether the evidence supports resolution and the subsequent closure of the work.

Resolved and Closed identify different points in that handoff. Reopened brings a valid returning problem back to the same ticket identity while retaining the earlier event history. The team can therefore review what was attempted before assigning the next response, rather than starting the conversation again without its context.

• Resolution evidence. The assigned Service Agent records the proposed outcome against the ticket. The source identity, current revision and actor scope must remain consistent with the customer problem being resolved.
• Outcome review. Service Supervisor checks the evidence under the customer policy agreed during setup. An eligible resolution records its date, while the policy determines when the ticket may proceed to Closed.
• Returning problems. A new valid customer problem can reopen the same ticket through the agreed process. The prior events remain available so the assigned agent and reviewer can understand the earlier intervention.

Define what evidence supports a resolution for the pilot’s customer problems. Agree how the reviewer and customer policy establish acceptance, and distinguish that decision from the later closure rule. Name the person responsible for reviewing cases whose evidence does not support the proposed outcome.

Choose how the team identifies a valid reopening and the source states from which it may occur. Confirm the ownership and due-date policy for returning work, then test it against the actual operating process. Reopening should preserve the ticket identity and earlier history while making the new customer problem clear to the agent who continues the work.

Return to the ticket about account access after the agent has completed the agreed support action. Service Agent records a Resolution event explaining the result and the supporting evidence. Service Supervisor reviews the same ticket revision and applies the customer policy before the work becomes Resolved.

Follow the closure policy and check that the resulting state and resolution date correspond to the accepted outcome. Later, introduce a valid report that the problem has returned. Reopen the same ticket through the agreed path, then inspect its identity and event history. The next agent should see both the original resolution and the new problem requiring attention.

Also rehearse a resolution attempt with an outdated revision or a different organizational context. That request must not be allowed to overwrite the current outcome. Finish by reading the ticket as Auditor to confirm that the earlier response and resolution evidence remain understandable within the permitted scope.

• Resolved and Closed Tickets — Customer problems at the resolution or closure stage, with the recorded resolution date.
• Reopened Tickets — Returning problems attached to their existing ticket and owner.
• Ticket Evidence — Supporting attachments with their type, uploader and visibility.

Use Resolution to reopening after Response and waiting evidence, and review discrepancies through Correction and receipt reconciliation.