Ogero / Web / 2023
Ogero Ticketing System
The problem
Support teams had no clear, shared way to create, assign and follow a ticket through to resolution.
What I built
I built a responsive React interface on top of an Oracle back-end: authentication, role-based access and a clean flow for opening, assigning and tracking tickets. Agents get exactly the view their role allows, and nothing falls through the cracks.
Technical highlights
- 01
Track to resolution
A clear lifecycle for every ticket — created, assigned, tracked and closed — so requests never get lost.
- 02
Role-aware access
Authentication and role-based permissions on an Oracle back-end keep the right data with the right people.
- 03
Responsive by design
A React interface that behaves the same on a support desk or a phone.
Interface Showcase
Product experience
Inspect the product through guided chapters — main experience, key feature flows, and the full ecosystem.
The Ogero admin platform — centralized user management with role-based access.
- Users
- Roles
- Access
A ticketing system is invisible when it works — the whole goal was to get out of the support team’s way.
Next system →
