top of page

How To Delete a Ticket in Ticketing as a Service

Updated: Apr 27

Ticketing as a Service does not have a delete option for tickets. This is intentional. The system is designed to preserve a complete record of all tickets for data integrity, compliance, and audit purposes.


If you need to clean up your queue or handle a ticket that was created by mistake, there are two alternatives: cancelling a ticket or archiving a ticketing instance.



Why Can't I Delete Tickets?

Our system's architecture is rooted in safeguarding data integrity and aligning with standard business practices:

  • Data Preservation: Accidental deletions can be more than just a nuisance; they can lead to critical data loss. By disabling the delete option, we provide a safety net against such mishaps.

  • Dispute Avoidance: Removing the delete function also removes the potential for disputes over ticket ownership and creation, fostering a more transparent and accountable environment.

  • Compliance with Policies: Many organizations are bound by strict data retention policies that require them to keep records for a certain period. Our system supports these compliance efforts seamlessly.

  • Transparent Pricing: Our pricing model is based on the number of tickets created. This ensures a clear and straightforward billing process, reflecting the actual usage of our services.


We understand that these reasons resonate with the structure and policies of many businesses, and we hope this clarity enhances your trust in our system's reliability.


What You Can Do Instead


Cancel a Ticket

If a ticket was created by mistake or no longer needs to be actioned, you can close it using a "Cancelled" resolution. The ticket remains in the system for record-keeping purposes but is clearly marked as inactive, so your team knows it does not require any follow-up.


To do this, open the ticket and close it with "Cancelled" as the resolution reason. It will stay in your records without cluttering your active queue.


Archive a Ticketing Instance

If the issue goes beyond a single ticket and you want to remove an entire ticketing instance from your active view, archiving is the right approach. Archiving keeps all ticket data intact and retrievable, while clearing the instance from your day-to-day working environment.


This is useful when a project, department, or service desk instance has run its course and you no longer need it in your active workspace but still want the historical data available if needed. How to archive, restore, or move a Ticketing Instance.


If you have further questions or need help deciding which option fits your situation, feel free to reach out to the Teamswork support team.

TeamsWork is a Microsoft Partner Network member, and their expertise lies in developing Productivity Apps that harness the power of the Microsoft Teams platform and its dynamic ecosystem. Their SaaS products, including CRM as a Service, Ticketing as a Service and Checklist as a Service, are highly acclaimed by users. Users love the user-friendly interface, seamless integration with Microsoft Teams, and affordable pricing plans. They take pride in developing innovative software solutions that enhance company productivity while being affordable for any budget.

Comments


bottom of page