What a ticket is, and where it comes from
The Helpdesk turns any support request into a ticket — a tracked record with a unique reference, a subject and description, a status, a priority, a category and an owning department. The reference is what everyone quotes ("about TKT-1042"), and the status is what makes the request trustworthy at a glance: nothing is "lost in an inbox" because every request is a row with a state, not a message someone may or may not have seen.
Requests arrive through three channels that all land in the same queues. A branded public portal lets customers and the public submit without an account and get a tracking reference to follow progress; inbound email becomes a ticket automatically; and staff with a login raise tickets in-app from My Tickets. The channel is just the front door — once inside, every ticket is worked the same way.
Because the desk shares AWRA's identity, roles, departments and records, a ticket is not an island. It can be tied back to the customer, project or asset it concerns, and the same permissions and approvals that govern the rest of the platform apply here too. That is the difference between a bolt-on helpdesk and one wired into how the business actually runs.
Key takeaways
- A ticket has a reference, subject, description, status, priority, category and department.
- Intake is multi-channel — public portal, email, and in-app My Tickets — all into the same queues.
- The public portal needs no account; the requester gets a tracking reference.
- Tickets share the platform's identity, roles, departments and records.