The product team has decided to redo the ticket page in order to achieve better user experience.
• Suggest a layout for a ticket page.
• Demonstrate a flow of the service provider sending a guide to the end user – selecting a guide, adding notes and sending.
**No access to the current system**
Product Requirements
The ticket page consist of the following information:
Subject (the title of the ticket) | Area – storage, counter, storefront etc. | Item – surge protector, cashier etc. | Description – free text | Related tickets | Attachments | Reporter name | Time of submission | Assignee | Status – open/in progress/resolved | Category & sub-category | TTR (time to resolution) | Priority | Impact | Tags | SLA | Billable time | Feedback & Rating – when the ticket is resolved the reporter rates the service | Resolution actions – there are MANY ACTIONS that the service provider can take in order to resolve the ticket e.g.-
Send a message to the reporter, Take control of the reporters’ computer, Send a help guide, Order equipment, Set a meeting with the reporter, Start a video meeting with the reporter.