No handler yet
Check new tickets whose rules did not match or whose destination lacks a technician. They stay in triage with an explicit routing result, rather than disappearing behind an empty assignee.
Internal tickets with clear ownership
Report employee issues, assign a handler, and follow the work through waiting, resolution, and reopening.
Explore with sample data. Adapt fields, views, and workflows for your team.
Give each open issue a clear next action
Waiting for someone else
Separate a request for employee information from a vendor dependency. Record when the wait begins, what is missing, and who will follow up.
Resolved, awaiting confirmation
Keep the resolution explanation and ask whether the employee can work again. A resolution record is not the same as confirmed closure.
Reopened
Bring the issue back with a reason and another handling cycle. Preserve the earlier resolution and work history instead of creating a disconnected duplicate.
Keep the handling story with the ticket
Report the problem
“The meeting-room display has no signal” is actionable when it includes the room, affected work, impact, and what the employee already tried.
Assign and respond
The routing rule selects the team and handler where available. Record the first meaningful response separately from later progress notes.
Work, wait, or reassign
Each activity explains a decision. A reassignment records the new team, person, and reason; a work entry records actual minutes spent.
Resolve and confirm
Explain the fix, record resolution time, and confirm closure. If the fault returns, reopen the same issue with the new symptom.
Set priority from affected work
| Reported impact | Priority | Why it matters |
|---|---|---|
| One person; work can continue | Low | A non-blocking question can wait behind an outage. |
| One person; work partly blocked | Normal | Plan a response without treating a limited interruption as a widespread outage. |
| Work stopped, or a whole location affected | High | Give blocked work a clear owner and response target. |
| Whole location; work stopped | Urgent | Make widespread interruption visible immediately. |
Running an internal help desk
Is this intended for employee support or customer support?
This example is designed for internal employees and shared-service teams. It does not provide a packaged customer-support inbox, synchronized email conversation, or contact-center channel stack.
What if no routing rule matches?
The ticket remains in the triage queue and records an unmatched routing result. A support owner can assign it manually and add an appropriate rule for future tickets.
Can we handle confidential HR requests in the same app?
Do not put confidential employee matters into a broadly visible support queue. Use a separate app or carefully configured record and field permissions, with approved HR access, before collecting sensitive information.
Does waiting stop the service clock?
Only a waiting reason permitted by the ticket’s policy pauses resolution time. The sample policy permits waiting for employee information but not vendor waiting. First-response and resolution clocks are separate.
Can a closed issue be reopened?
Yes. Record why the problem returned. The earlier work remains in the ticket history, and the new resolution cycle adds working time without counting the closed interval as active handling.
Will incoming email automatically create tickets?
Not in this example. Employees use the Jodoo issue form. Email ingestion or other channels need a separately configured integration; choose a packaged help desk if a native shared inbox is the primary requirement.
Choose the next step for your team
Replace the “who is handling this?” conversation
Open the sample queues and adapt categories, ownership, and handling records for one internal support team.