Skip to main content
Dashboards and ticket work

Guide notes in HaloPSA and their action pages

The nine Guide Action screens are the small pop-up pages behind the private guide notes in a HaloPSA ticket: confirming a path, sending, modifying or skipping a step, creating a custom approach and getting help.

Last updated 25 days ago

The Interactive Guide does its work in small pop-up pages: confirming a path, sending a message, modifying or skipping a step, creating a custom approach and getting help. Agent Assist opens two of them, Create Custom Approach and the Qubit Guide Assistant. The private guide notes that QuantumOps can add to a HaloPSA ticket carry links to the guide's action pages. Technicians use them while they work a ticket.

Before you start: guide notes are added to HaloPSA only when Enable Halo Posting is on. It is off by default, and it also needs Enable Interactive Guide, which is on by default. Both are on the Guides tab of Q-Director Settings; see Q-Director: guides and the guide simulator. The path selection note is made from the ticket's resolution plan, so it also needs Autopilot to be on; see Autopilot settings. The action pages work only inside HaloPSA and in the pop-up windows that Agent Assist opens, and from the links in the guide notes themselves. Opened straight from a browser address bar they show Access Denied, and they do not ask you to sign in to QuantumOps. Each page opens in its own small window, and most close themselves when you finish. Interactive Guide is a module that is on unless an administrator turned it off.

Read the guide notes in HaloPSA

With guide posting on, QuantumOps adds three kinds of private note to the ticket. Private notes are hidden from the customer. They appear under the name of the ticket's assigned agent, or as Q-Director when the ticket has none. For everything QuantumOps writes into HaloPSA, see What QuantumOps writes into HaloPSA.

NoteWhat it contains
Path selectionThe heading Interactive Support Guide Available, then each path with its first two steps, at most the number set by Max Trajectories to Show. A path is marked as recommended when the AI's confidence in it reaches the Minimum Confidence Score. Each path has a Select This Path link, and every path except the recommended one has a Why not recommended? link. A Create Custom Approach link closes the note.
StepThe heading Next Step: with the step text, then Recommended Action:, then four links: Send, Modify, Skip and Get Help. The footer reads "Step n of m" with a short session code.
CompletionThe heading Support Guide Completed! with the number of steps completed, then Was this guide helpful? with two links, Yes, helpful and Not helpful.

Every link in a note is a complete address to QuantumOps, so it opens from HaloPSA in a new tab, with no need to be signed in to QuantumOps. Each link carries a signed code for that ticket and no other, and it stops working after seven days. A link that has expired, or that was edited, shows Access Denied with a line saying the link has expired or is not valid for this page; open the ticket in HaloPSA and use the Agent Assist tab, or use the link in the newest note. Yes, helpful and Not helpful open Give feedback on a guide for that guide, even though the guide is already complete.

The links in the notes lead to the guide's action pages, which the sections below describe: Send a message for a step, Modify a step, Skip a step, Get help while you work, Why a path is not recommended and Create a custom approach.

Confirm a path

The Confirm Trajectory Selection page shows the path you picked as Selected Path with its numbered steps, an Add Notes (Optional) box, Confirm Selection and Cancel.

The Confirm Trajectory Selection page: the numbered steps of the selected path, an optional notes box, and the Confirm Selection and Cancel buttons
Nothing is recorded until you select Confirm Selection, so the path can still be changed up to that point
  1. Read the steps.
  2. Add a note if you want one.
  3. Select Confirm Selection. The guide starts, the window closes and, with guide posting on, the first step is posted to the ticket as a step note.

This page opens from Select This Path in a path selection note, and from Select This Path Anyway on the page described in Why a path is not recommended. If the ticket already has a guide running, confirming completes it and starts the chosen path as the ticket's guide. The guide is recorded under the agent named in the link, or under the Default Agent Email when the link names none.

Send a message for a step

The Send Message page shows the Current Step, the Message to Send, a preview of it, a checkbox and a box for notes.

  1. Write or edit the Message to Send. The box is a message editor with eight buttons: Bold, Italic, bulleted and numbered lists, Outdent and Indent, a link and Clear Format. Enter starts a new paragraph and Shift+Enter a line break. It may start as the assistant's message for the step, or as a short greeting that restates it, and it carries no closing: leave out a closing and your name, because your e-mail system adds your signature. Preview (what will be posted) shows the note the way it will read. Pasted pictures are not accepted.
  2. Check Send as private note if the customer should not see the message. The full label adds that the note is not visible to the end user. The box is unchecked at first.
  3. Add Additional Notes (Optional) if you want to record something about the action.
  4. Select Send Message.

The step is marked complete and the next step is created. With guide posting on, the message is posted to the ticket as a note, visible to the customer unless you checked the private box, followed by the note for the next step, or the completion note after the last step. With guide posting off, the step is recorded as complete and nothing is posted to HaloPSA.

The page also offers Skip This Step and Cancel. Skip This Step marks the step skipped and closes the window. Unlike Skip This Step on the Skip Step page, it does not post the next step note, and it posts nothing to HaloPSA. To skip a step and move on, use Skip a step, which records a reason, or Skip in Agent Assist.

To e-mail the customer from a guide step, use Send Email in the Agent Assist reply panel, described in Agent Assist.

Modify a step

The Modify Step page lets you reword a step.

  1. Read the Original Step:.
  2. Rewrite it under Modified Step:. The box starts with the current text.
  3. Add a Reason for Modification (Optional):.
  4. Select Save Changes. It stays unavailable until the box has text.

The guide keeps the original wording and your reason with the step. With guide posting on, the updated step is posted to the ticket as a new step note. The window closes.

Skip a step

The Skip Step page lets you skip a step and record why.

  1. Read the Step to Skip:.
  2. Choose a Reason for Skipping:: Not applicable to this ticket, Already completed, Customer preference, Technical limitation or Other reason. If you choose Other reason, describe it under Please specify:.
  3. Select Skip This Step. It stays unavailable until you choose a reason.

The page warns that skipping steps may affect the resolution quality, and that you should skip only when you are certain the step is not needed. The step is recorded as skipped with your reason. With guide posting on, the next step note is posted, or the completion note after the last step.

Create a custom approach

The Create Custom Approach page opens from Create Custom Approach or Change Path in Agent Assist, and from the Create Custom Approach link in a path selection note.

  1. Describe your approach under Describe Your Approach.
  2. Add Additional Context (Optional) if it helps.
  3. Select Generate Custom Steps. While it works the page reads Generating custom approach....
  4. Read the Generated Steps. The AI writes three to five steps for this ticket from the approach you described and the context you added. If it cannot, the page says why, for example that AI responses are turned off or paused, and shows no steps. Your description is kept with the guide.
  5. Select Use This Approach to start it as the guide for the ticket, or Regenerate to clear the steps and generate again.

Use This Approach completes any guide the ticket already has running and starts this one in its place, in the name of the agent who opened the page. The window closes. With guide posting on, the first step is posted to the ticket as a step note. In Agent Assist, select Refresh to load the new guide. A guide started this way shows Path Type as Custom.

The Why This Path Isn't Recommended page lists the steps of a path and, under Analysis, two or three sentences from the AI on why it is a weaker choice for this ticket than the recommended path, and when it could still be the right one. If the AI cannot answer, the page says why instead. It has two buttons:

  • Select This Path Anyway opens Confirm a path for that path.
  • Close closes the window.

Agent Assist does not link to this page; the path selection note does.

Give feedback on a guide

The Guide Feedback page opens from Yes, helpful and Not helpful in the completion note. It asks How helpful was this interactive guide? with five faces from Very Helpful to Very Unhelpful; the link you used has already chosen Helpful or Not Helpful. Add Additional Comments (Optional): and select Submit Feedback, or Skip. Your rating and comment are recorded with the guide.

Get help while you work

Two assistants are available, and they differ in scope.

Quick Help Assistant. Its subtitle reads Get help with your current step or ticket. The top of the window shows the Current Step: and its Description:, or the Ticket: when no step is current. Type a question under Ask for help with your current step... and send it. The AI answers your question for this ticket and this step, using the ticket's summary and details and the steps already done. If it cannot answer, the chat says why in plain words: AI responses turned off, AI paused for your organization, or a provider fault. It never shows made-up help. Use Full Interactive Chat for a longer conversation about the ticket; it is not shown while AI responses are turned off. After an answer, Post to Ticket appears. With guide posting on, it posts your question and the answer to the ticket as a private note, marked as generated by the Quick Help Assistant, and the chat confirms it. If guide posting is off, or HaloPSA refuses the note, the chat says nothing was posted and why.

Qubit Guide Assistant. Help and Chat with Qubit in Agent Assist open it, and so does Full Interactive Chat. It is a full conversation about the ticket. The bar above the chat shows the ticket, the current step and the status of the guide. Type a question, or select a quick question under Quick questions:: What should I do next?, Explain this step, Risks of skipping or Similar tickets. While it works the window reads Guide Assistant is thinking.... Where file attachments are enabled for your organization, you can attach a file or paste a screenshot. It uses the same chat as Qubit elsewhere; see Chat with Qubit from a HaloPSA dashboard and Chat with Qubit.

Which actions post to HaloPSA

This table covers what happens with guide posting on. With it off, none of these actions post to HaloPSA.

ActionPosts to the HaloPSA ticket
Confirm SelectionThe first step note
Send MessageThe message, then the next step note or the completion note
Save Changes on the Modify Step pageThe updated step note
Skip This Step on the Skip Step pageThe next step note or the completion note
Skip This Step on the Send Message pageNothing
Use This ApproachThe first step note
Post to Ticket in Quick HelpA private note with the question and the answer

Send Email and Post Note in the Agent Assist reply panel do not depend on guide posting.