One support queue
Requests from different channels get a number, a state and a responsible team.
WiHelp
WiHelp receives the request, sets its priority, assigns an owner and records the resolution. Support sees the queue and the history, and the user knows what is going on.
Requests from different channels get a number, a state and a responsible team.
Criticality, service rules and time control help not to miss what matters.
History and standard answers feed the knowledge base instead of a repeated investigation.
01
Accepts a request from a user, an employee or a connected system.
02
Determines the topic, the priority, the queue and the person responsible.
03
Keeps the correspondence, the actions, the outcome and material worth reusing.
Employees send requests to IT, HR, facilities or other services.
The user sees the state of the request, and the team sees the customer history.
Requests are distributed between support lines and organisations.
Internal and customer requests, incidents and other enquiries arriving from connected channels.
Yes. Requests have a state, a priority, a queue and an owner.
WiNotes materials can serve as the knowledge base and as standard resolutions for support.