Skip to content
Help Center
Submit a request Sign in

Send a case to Trash and understand closure, ownership and purge consequences

Trash removes an unwanted case from normal active operations through a case lifecycle and queue action. It is not the same as resolving a valid customer issue, and it is not an immediate hard delete. The action can run closure processing and clears the current owner when moving the case to the Trash queue. Later, the account’s configured purge policy can permanently remove the case, including its history and attachments.

At a glance

For: agents and administrators authorized to transfer cases to Trash. Applies to: Supportbench Core.

Start here: Case List → the case Peek action or explicitly selected cases

Use Trash for the right reason  ·  Review the case and permission first  ·  Send one case to Trash  ·  Send a reviewed selection of cases to Trash  ·  Understand ownership and closure effects  ·  Check the actual account purge policy  ·  Example: remove an approved training case without hiding real work  ·  Troubleshoot Trash actions and missing cases

Use Trash for the right reason

SituationAppropriate starting point
The customer’s genuine issue has been resolvedUse the normal Resolve/Close workflow and preserve the service history.
Two cases represent the same issueReview the case merge procedure and the information to retain. Do not assume Trash is equivalent to merging.
A case is confirmed unwanted, such as an authorized test recordReview its identity and consequences before using Trash.
A case is difficult, overdue or assigned to the wrong teamCorrect ownership/routing or escalate through the operational workflow. Trash is not a workload or SLA-management shortcut.
A case was trashed accidentallyContact the authorized administrator/support process promptly with the case ID and time. Recovery is not guaranteed by this guide.

In a B2B relationship, a case may carry an engineering finding, attachment or customer commitment that matters beyond the original contact. Check the actual content and related work before deciding it is disposable.

Review the case and permission first

  1. Find the exact Case ID in Case List and inspect the subject, Company, Contact and relevant history.
  2. Confirm why it should leave active operations and whether merge, reassignment or normal closure is the appropriate alternative.
  3. Review current ownership, active customer commitments, attachments and related work that would be affected.
  4. Check your authority. The Case List Trash command uses the permission labeled Transfer Cases to the trash in bulk, including the inspected single-case action path.
  5. If permanent retention matters, ask the administrator to confirm the account’s purge policy before proceeding.

Do not assume that selecting a case or viewing its history grants permission to trash it. If the action is missing, check the relevant role rather than following obsolete Case View transfer-arrow instructions.

Send one case to Trash

  1. Open Case List, locate the verified case and open its Peek actions.
  2. Choose Trash Case.
  3. Read the confirmation Send this Case to Trash? Confirm only when the case and intended action are correct.
  4. After the action completes, verify the outcome. Ordinary case lists generally exclude Trash unless the selected queue/view explicitly includes it.
  5. Review any consequential closure/routing result through the authorized case/account process if needed. A missing row in the original view alone does not establish every effect.

Send a reviewed selection of cases to Trash

  1. Narrow Case List to the work being reviewed.
  2. Select the intended cases deliberately and inspect the selection before acting.
  3. Choose Trash to open the Trash Cases confirmation.
  4. Read Send every selected Case to Trash? Cancel if any selected case is uncertain.
  5. Confirm the reviewed action and inspect the result before attempting another bulk action.

A bulk action changes every selected case

A search result is not a deletion decision. Review customer context and record identity, especially when a shared view includes several Companies or Divisions. Do not use Trash to remove legitimate cases from a performance report.

Understand ownership and closure effects

The current lifecycle sets the case’s queue to Trash, clears its current owner and invokes the close-workflow/finalization path and associated cleanup. It is therefore more than a visual list filter. Configured closure behavior can be relevant, and the former owner should not be assumed to remain responsible for an item moved to Trash.

Ordinary Transfer is not documented here as an undo. A later routing action is not necessarily a restoration of the former owner, state or workflow effects. Use the authorized administrator/support process to assess an accidental action rather than attempting a guessed sequence of transfers.

For a legitimate completed issue, preserve the case in the normal resolved/closed lifecycle. That history can help colleagues investigate recurrence, understand customer impact and reuse the resolution in knowledge.

Check the actual account purge policy

Administrators review this at Settings → Account → Policies → Global Case Settings → Purge trashed cases. The page heading is Account Policies. It is separate from the Case Policies used to configure case forms.

The visible retention choices are 7, 14, 30, 60, 90 or 180 days. When the stored value is zero, the current behavior uses 60 days. Your account may have another configured value; do not rely on an old article’s blanket 30-day statement.

Purge removes the underlying case history

The policy describes removal from the database, including history and attachments. Do not treat Trash as an archive, a guaranteed recovery window or a substitute for an approved retention process. No user-facing recovery route after purge is established here.

Changing retention affects more than one case and belongs to the authorized account policy process. This procedure does not instruct agents to change the policy to recover an individual item. Report an accidental Trash action promptly rather than waiting until the end of a presumed retention period.

Example: remove an approved training case without hiding real work

A support lead identifies a training case that was intentionally created for an internal exercise. They verify the Case ID, customer context and lack of live service obligations, then inspect any closure behavior and applicable retention. The authorized agent uses Trash Case and records the outcome according to the team’s process.

A real customer case with the same subject is handled differently: the team resolves, merges or routes it based on its actual purpose. Keeping that distinction protects both the customer history and the meaning of workload reports.

Troubleshoot Trash actions and missing cases

ProblemWhat to check
Trash is not availableReview the role’s Transfer Cases to the trash in bulk permission and the current Case List action context.
An old guide says to use the Case View transfer arrowUse the verified Case List/Peek route in this guide. The old route has not been established in current Core.
The case disappeared from the normal listOrdinary lists exclude Trash unless explicitly scoped to it. Inspect the authorized queue/view and action result rather than repeating the action.
The owner was cleared or closure behavior occurredThese are consequences of the Trash lifecycle, not proof of a harmless visual move. Review the case action through the authorized process.
The case has already been purgedPurge includes history and attachments. Escalate through the authorized support process without promising user-facing recovery.
A case was trashed accidentallyProvide the exact Case ID, account, action time and observed outcome promptly to the administrator/support team. Avoid competing changes or assumptions about restoration.
The result of the action is ambiguousInspect the target record/outcome before retrying and retain the non-secret error details.

Was this article helpful?