Learn the Desk screens, field choices, relationships and workflows through progressive examples and result checks.
People learning to use Workroomly Desk
Desk keeps a service request, its handling, conversation, supporting work and disposition together. A ticket is not finished merely because somebody wrote an answer or changed its state. This course follows a simple fictional request: a welcome guide tells a learner to bring “the usual materials,” and the requester needs the exact materials named before using the guide.
Open lesson →Desk configuration defines a shared service. Understand the fields before changing them: a department, agent, ticket type, topic and custom field each answer a different question. Ordinary handling should use the agreed definitions rather than redesign them for one request.
Open lesson →Triage establishes who needs to act next, why the request matters and which service target applies. Queue position, a department name and a clock are useful signals, but none alone establishes accountable handling.
Open lesson →A useful response tells the requester what was understood and what happens next. A useful internal contribution gives the handler or specialist enough information to act. Choose the correct audience and control before entering content.
Open lesson →Desk lifecycle controls record progress through a service process. The correct transition follows the request's evidence and the actor's authority. It should not be used to hide missing work or repair an unexplained clock display.
Open lesson →Service reporting helps decide what to improve, but a chart is useful only when its population and measure are understood. This chapter connects Overview to individual requests and finishes the course with a small end-to-end exercise.
Open lesson →Open Workroomly beside the lesson, build one connected motion, and leave the business running better than you found it.