Modules / Support and Ticketing
Support and Ticketing
Inbound requests from staff or occupants, triaged in a queue, then converted into a real job on the site.
A leak reported at the front desk, a text to the duty manager, an email to facilities. None of those become a job with a site, a priority and an owner. By the next shift the request is gone.
-
Log the request against a site Create request
Capture title, priority, who raised it, and the site or location description. The record is pending until someone in the office acts.
-
Triage the inbound queue Filter by status
Office staff list open requests by company, site and status. Pending, accepted or converted, not a shared inbox.
-
Convert the request into a job Convert to job
One action creates a work order from the request, keeps the site and requester, and stores the new job number back on the request.
-
Requester view My requests
The person who raised it sees status on their own requests. They do not see the rest of the portfolio.
-
Notes stay on the request Update request
Clarifications and photos sit on the request so nothing is retyped when it becomes a job.
Requests
Pending → accepted → converted to a job
Cold room leaking
Request · North / Kitchen · duty manager
Room 214 air con
Harbour · converted
This module is the front door, not a helpdesk slogan. A request is a first-class record: site, priority, requester, status. When the office converts it, the platform opens a job in the work-order lifecycle and writes that job number back onto the request. The hallway conversation is over. The work has an ID.
Also used in Hospitality , Aged Care .
See this function in a walkthrough.
Request, job, field today, inspection, register.