Put a ticket on hold and resume it
Mark that a ticket depends on the requester, a vendor or a change, so the resolution SLA is paused in the meantime.
On this page
When you can't move forward because you are waiting for something from outside, put the ticket On hold with its reason. That way the team knows why it is stopped and, depending on the SLA policy, the resolution clock stops running in the meantime.
Before you start
You need Operate in Incidents and requests and a desk role other than Viewer.
The ticket must be In progress. If it is Assigned, press Start or Take first.
Put on hold
On the ticket page, in the Status section of the side panel, press Put on hold.
In the window, choose the Reason for hold:
Waiting for the requester: you asked them for information, a test or a confirmation.
Waiting for a vendor: it depends on a third party, for example a manufacturer's support.
Waiting for a change: the solution comes with a planned change.
Other reason.
If you want, write an Internal note (optional) with the details. Only the team sees it.
Press Put on hold.
If you are going to ask the requester a question, write it in Reply to requester and choose Send and wait for the requester: it sends the question and puts the ticket on hold in a single step (see Reply to the requester).
What happens to the SLA
The Resolution clock is paused if the ticket's SLA policy pauses for that reason. The built-in policies pause with Waiting for the requester and Waiting for a vendor, not with Waiting for a change or Other reason. Your company adjusts this in Settings → SLA.
In the SLA section of the ticket page, the paused clock says Paused and how much business time it has left, for example "Paused · 3 h business time left". In the list, its bar is gray.
The First response clock isn't paused. If you haven't replied to the requester yet, it keeps running.
More detail in Read a ticket's SLA.
What the requester sees
In the portal, a ticket Waiting for the requester appears as Waiting for your reply, so they know the next step is theirs. With the other reasons they see it as In review.
Resume
The ticket goes back to In progress in two ways:
Manually: in the Status section, press Resume.
Automatically: if the reason is Waiting for the requester and the requester replies, through the portal or by email, the ticket goes back to In progress automatically. In the conversation you see their reply and, in History, the status change.
When it resumes, the Resolution clock starts running again from where it stopped. The assignee gets the notification of the requester's reply.
With the other reasons the ticket doesn't resume by itself. When the vendor replies or the change is implemented, press Resume.
Resolve without resuming
If the problem is solved while you wait, you don't need to resume: from On hold you can press Resolve directly (see Resolve and close a ticket).