When Projects get past Completion, the core Visibuild product does not allow external users (non Visibuild users) to create issues directly in to the project. Previously that has meant that project teams resort to email, spreadsheets and other highly manual processes to collect, manage and close out end user raised issues - that is where the Tickets Module comes in to create continuity between construction, completion and post completion.
Who uses the Tickets Module?
The Tickets module is primarily created to be used by Post Completion Management teams. Our key users in this space would have roles such as:
Post Completion Manager
Warranty Manager
Maintenance Manager
How does the Tickets Module Work?
The Tickets module allows non Visibuild users to create Tickets through a public URL which can then be triaged, managed and linked to defects within the project environment to manage the Post Completion phase of the project.
Key features of the Tickets module includes:
Public Tickets Portals with customisable locations
Company-wide Tickets Table which allows you to manage all of your company's Tickets from one spot
Filters and prioritisation tools to help manage tickets across your portfolio
Ticket triage workflows
Automated emails to notify and update Ticket creators
Ability to link defects to Tickets within existing Visibuild Projects
In-product communication with Ticket creators and partners required to complete works
Tickets vs Visis
Tickets - are designed to track and manage external requests post-completion (like maintenance or warranty items).
Visis - are used throughout construction to manage inspections, defects, and compliance between builders, subcontractors, and consultants.