Employee
Sees only their own tickets.
- Pages
- Home, My tickets, My devices, Help guides, Contact IT
- Can start
- Report a problem, New ticket
An IT help desk portal is where employees log laptop, access and software problems as tickets, the IT team triages and resolves them on a board, and each requester can see where their own ticket stands.
Pattern: RequestsDescribe it to Pory
“Our staff need one place to report IT problems. The IT team should triage tickets by priority and mark them resolved, and whoever raised a ticket should be able to see its status.”
My tickets
In plain English
Pory gives every employee and IT team a sign-in of their own. Each employee sees only their own tickets. It covers ticket submit & resolve. Tickets, IT to-dos, devices, IT schedule, help guides and IT team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
IT problems arrived by Slack, email, and whoever caught Luis at the coffee machine, so half of them were never written down. In Pory an employee picks the category and priority, describes what's happening and adds a screenshot. The ticket lands in IT's queue with the details already there, and nobody gets stopped in the corridor.
The IT queue was a shared inbox where urgent and trivial looked identical. The IT team sees every ticket as a card on a board, in New, In progress, Waiting on requester or Resolved, and drags each one along as the work happens. The payroll lockout gets picked up before the printer jam, as it should.
"Any update on my laptop?" was the message IT got most, usually about a ticket already being worked on. In Pory each employee sees their own tickets with a progress bar from New to Resolved, the latest note from IT, and a Waiting on requester step when IT needs something from them. The update is already there, so the follow-up never gets sent.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own tickets.
Sees every ticket in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited employees.