DallasDubaiBaselHyderabadPune
Home/Case studies/Ticket IT: Enterprise Service Management

Case study · Employee experiences

Ticket IT: Enterprise Service Management

Structured ticketing with ownership, priority and escalation, on web and mobile.

IndustryEnterprise
ExperienceEmployee experiences
LensSystems · Data
ChannelsWeb portal, Mobile app, Dashboards
Connects toEmail and existing issue logs
Platforms behind itEmail and existing issue logs
→
What we builtTicket IT: Enterprise Service Management
→
ChannelsWeb portal, Mobile app, Dashboards
→
Who benefitsEmployee

IT requests raised by email and phone are hard to track and easy to lose. Ticket IT gives every request an owner, a priority and a status.

The challenge

Tickets arrived by email and phone with no consistent format. Support staff followed up to ask for screenshots. The issue log lived in an Excel sheet, so tracking was difficult, nothing had a priority and nobody could be held to a deadline. Escalations were high, because the only way to get attention was to complain.

Our solution

Ticket IT is a mobile and web-based enterprise service management solution. It keeps a single repository with a log of all issues, gives each ticket a status, an owner and a priority, and supports filters for assignees. Dashboards and reports are defined by role, so a service manager sees what a service manager needs.

The decision that mattered most was to make logging a ticket easy for the user. A structured form that takes thirty seconds yields better data than a free-text email that takes five minutes to interpret.

The impact

Data became structured. Tickets acquired owners, and escalations fell because people could see progress. Grievances were handled in the open, and answers to common problems became quicker.

Outcomes

Results delivered

  • Structured ticket data
  • Ownership of tickets and escalations
  • Easier handling of grievances
  • Registered progress
  • Quicker solutions
  • Ticket data at your fingertips

Discuss a similar requirement

Tell us who the users are and which applications they depend on. We will describe the approach we would take.