Before you solve
Enterprise feature (new in 1.20.5,
helpdesk). See the Helpdesk overview.
Some details are only worth having if every ticket has them: a resolution code for the monthly report, the root cause, the device the fault was on. A requirement set says what a ticket needs before it can be solved. When an agent presses Solve on a ticket that is missing something, the Before you solve dialog opens with what is missing. They fill it in and solve in one step.
Until you add a set, solving works exactly as it always has.
Requirement sets
Section titled “Requirement sets”Desk settings → Forms and fields → Before you solve lists the sets. It needs the desk capability Helpdesk settings (Admins, out of the box).
Each row shows the set’s name, whether it is On or Off, what it applies to, how much it asks for (“2 ticket fields · 3 closing fields”) and how many tickets hold an answer to it.
New requirement set asks for a name, creates the set switched off and opens its page, so nothing changes for agents until it is ready. The page has four cards and one Save requirement set:
- Set: the Name, and the On switch. A set can only be switched on once it asks for something.
- Applies to: All tickets, or Chosen teams and request types. Pick teams, request types or both. With both picked, a ticket must match both. Every set that is on and matches a ticket applies to it, so a set for all tickets and a set for IT both apply to an IT ticket.
- On the ticket: the ticket fields that must be set (see below).
- Closing fields: what the agent fills in (see below).
Delete set… is in the danger zone at the bottom.
Ticket fields that must be set
Section titled “Ticket fields that must be set”| Field | Met when |
|---|---|
| An owner | Someone owns the ticket. |
| A team | The ticket belongs to a team. |
| A category | The ticket has a category. |
| A sub-category | From 1.20.6: the ticket has a sub-category. A ticket whose category has no sub-categories passes. |
| At least one tag | The ticket has one tag or more. |
| A linked asset | An asset is linked to the ticket. Offered only while an asset source is connected; if the source is disconnected later, this stops being asked. |
| Time logged | Someone has logged time on the ticket. A running timer doesn’t count until it is stopped. |
| A reply sent to the requester | An agent’s public reply was sent. A newbie’s reply waiting for review counts once a lead approves it. With Send and set Solved, the reply being sent counts. |
A ticket always has a priority and a status, and an agent can’t change a ticket’s request type, so those aren’t offered.
Closing fields
Section titled “Closing fields”Closing fields are built like a request type’s form: Add field, give it a name, choose its Kind of answer (short answer, long answer, pick one as cards or as a list, yes / no, date, number, a person), add a help line if it needs one, and tick Required or leave it optional. A set holds up to 20.
Each field has a key, made from its name when you add it and kept when you rename it. The API uses the key.
Solving a ticket
Section titled “Solving a ticket”From 1.20.6 the dialog also opens, with no set at all, for a ticket whose event setup isn’t marked complete. It then has a Setup complete tick box.
When a set applies and something is missing, Solve, the e key, the
status menu’s Solved, Send and set Solved and a macro that solves
all open the same dialog, Before you solve #1047:
- On the ticket lists the ticket fields that are missing, each with a way to set it there: pick an Owner, a Team or a Category (and Sub-category, from the admin’s list), type a Tag, pick a device under Linked asset (the requester’s devices come first), or type the Time spent (“30m”, “1h 15m”) and press Log time. A reply can’t be written in the dialog: cancel, write it, and use Send and set Solved.
- Then each set’s closing fields, under the set’s name.
Solve (or Send and solve) saves everything and solves the ticket in one request. If the solve is refused for any other reason, nothing from the dialog is saved. Two things are saved as soon as you press their button, as they are in the side panel: Link on an asset and Log time.
Cancel changes nothing. A reply you had typed stays in the composer.
With nothing missing, there is no dialog and Solve is one click, as before. The dialog also opens when a set has optional closing fields that are still empty, so agents get the chance to fill them in; they can press Solve straight away.
On a team that asks for time on solve, “Log your time before solving?” comes first, so the time logged there counts. Required checklist items come before both: the desk shows the open items and asks nothing else.
Solve details
Section titled “Solve details”The answers stay on the ticket. The side panel shows them, read-only, in a Solve details card, with who filled them in. They are also printed with the ticket’s details when you print it or save it as a PDF.
Reopening a ticket keeps its answers. When it is solved again the dialog asks only for what is missing, with the earlier answers filled in.
What blocks solving
Section titled “What blocks solving”The rule is checked on the server, whatever solves the ticket. The refusal names up to four things: “Before you solve, this ticket needs: an owner, a linked asset, Resolution code and Root cause.”
| Path | What happens |
|---|---|
Solve in the desk, the e key, the status menu |
The dialog opens. Nothing is changed until it is submitted. |
| Send and set Solved | The dialog opens before anything is posted. A public reply counts as the reply a set asks for. |
| A macro that solves, applied by an agent | The dialog opens when the reply is sent. Through the API it is refused whole and nothing is posted. |
| Bulk edit | That ticket fails with the reason, and none of its other changes apply. The other tickets are changed. |
| The REST API and the Claude connector | Refused with the sentence, unless the answers come with the change (see below). |
| An automation, or a macro an automation sends | Only the status change is dropped. Its other changes still apply and its reply is still sent. |
| An alert that would resolve its ticket | The ticket stays open, and the failure is logged. |
| A major incident’s Solve all | That linked ticket stays open, with the reason. |
| A workflow’s Finish step | The run ends, but the request stays open with an internal note, and its owner is told (else the team’s leads, else its members). |
What is never asked:
| Path | Why |
|---|---|
| Closing a ticket that is already solved, including closing solved tickets automatically | It was already solved. |
| Merging | The merged ticket is closed, not solved. Answers it already had stay on it. The kept ticket is asked when it is solved. |
| The recycle bin | Deleting isn’t solving. |
| Workflow task tickets | A task’s hand-off is its closing step. |
| A newbie’s reply that waits for review | It changes no status. A newbie who may change the status is asked like anyone else. |
| Tickets solved before a set existed | They stay as they are. Reopened and solved again, they are asked. |
There is no role that can skip a set. To let a ticket through, set what it asks for, or switch the set off.
Changing a set later
Section titled “Changing a set later”- Editing or deleting a set never changes a solved ticket. Each answer is kept with the words it was asked in, so Solve details still reads the same.
- A closing field you remove is no longer asked. Tickets that answered it keep the answer.
- A new required field is asked the next time a ticket is solved. A reopened ticket is asked only for that field.
- An option you remove from a “pick one” field: tickets that chose it still show it, and are asked again if they are reopened and solved.
The API, webhooks and the Claude connector
Section titled “The API, webhooks and the Claude connector”- REST API:
PATCH /tickets/{number}andPOST /tickets/{number}/repliestakesolve_answerswith a status that solves the ticket. See API tokens and webhooks. - Webhooks:
ticket.solvedcarriessolve_details. - Claude connector:
hd_read_ticketlists the answers kept (solve_details) and, on an open ticket a set applies to, what a solve still needs (before_you_solve, with each closing field’s key, kind and options).hd_update_tickettakessolve_answerswithstatus: "solved". - Claude in the desk proposes a solve as a card; Apply runs the desk’s own solve, so the dialog opens.
Who sees the answers
Section titled “Who sees the answers”Only agents who work the ticket. Requesters, CCs and customer portal customers never see them, and the timeline line (“Ana filled in the solve details: Resolution code, Root cause”) is internal. They are not part of a person’s personal data export, which holds what the requester wrote and was sent.
Anonymizing a ticket removes the answers that are free text or name a person (short answer, long answer, a person). Choices, numbers, dates and ticks stay, so reports on resolution codes still add up.
Limits
Section titled “Limits”| What | Limit |
|---|---|
| Requirement sets | 50 |
| Closing fields in one set | 20 |
| Teams, and request types, one set names | 50 each |
| A set’s name | 80 characters |
A change to a set takes effect at once on the server that saved it, and within 30 seconds on any other.
In the audit log
Section titled “In the audit log”| Action | Shown as |
|---|---|
helpdesk.solve_requirements.created |
Created a Before you solve requirement set |
helpdesk.solve_requirements.updated |
Changed a Before you solve requirement set (records what changed, including switching it on or off) |
helpdesk.solve_requirements.deleted |
Deleted a Before you solve requirement set |
