By
Jen Butler
April 7, 2025
•
20 min read
Tutorials
Let’s be honest: ticket closure can be a huge mess in our MSPs.
You open a ticket and see open tasks, unlogged appointments, and missing resolution notes. But it’s marked “closed.” Now someone has to go figure out what really happened. Did those tasks get completed? Those HDMI cables delivered? Is the client still waiting for a response or an appointment?
If you're closing tickets without making sure everything’s actually done, you’re probably dealing with
This stuff adds up. And the bigger your ticket volume, the more it costs you in time and money.
To add insult to injury, often that “someone” who ends up doing the legwork to close the gap is usually someone from dispatch or billing, and it's usually not a good use of their time especially when the technician responsible is already off-site half-completing another batch of tickets.
After 11 years in the MSP world, I’ve seen this pattern over and over again. It’s not that technicians are lazy or trying to avoid work. It’s that the system allows this to happen, and no one’s taken the time to fix it.
So let’s use HaloPSA to keep people accountable, ensure tickets are worked to completion, and eliminate the need to play catch up when it’s time to bill for the great solutions we’ve provided for this client over the last term!
I have a video working through this solution that you can watch here.
Basically, we need to create a system that enforces good habits without relying on people to remember every little detail.
To achieve this goal, we’re going to use HaloPSA to:
In addition to the video, I also shared all the custom field setups, canned text, and SQL in this GitHub gist.
This isn’t about making life harder for your techs. It’s about:
It’s one small process change that takes a lot of pressure off your team, especially the people downstream from the techs who are closing tickets.
If you’re running an MSP, or trying to tighten up operations inside your PSA, this is for sure worth 15 minutes of your time.
🎥 Watch the full video here: Streamline Your MSP Ticket Closure Process with HaloPSA
📄 Get the code and setup details here: Ticket Review & Closure Process in HaloPSA – GitHub Gist
This discussion guide is part of Rising Tide’s Fall 2025 book club, where we’re reading The Go-Giver by Bob Burg and John David Mann.
If you’re just joining us, start with Chapter One – The Go-Getter for an introduction on how to use these Discussion Questions and you may also find our conversation on why we started a book club for a technical team here: Book Clubs, Conversations, and Curiosity.
In Chapter Two, Joe finally learns ‘The Secret’ from Pindar and it’s not what he expected, at all. The idea that success comes from giving sounds simple, but it seems Joe will need to put each principle into action to truly unlock the heart of the Secret of being a Go-Giver.
Use these open-ended prompts to guide reflection and conversation. Remember, there are no right answers!
Rising Tide helps MSPs and service-focused teams build better systems: the kind that align people with purpose.
Every Friday at 9:30 AM ET, we host Rising Tide Fridays as an open conversation for MSP owners, consultants, and service professionals who want to grow both professionally, technically, and emotionally. In Fall/Winter 2025, we’re walking through The Go-Giver, chapter by chapter.
If that sounds like your kind of crowd, reach out to partners@risingtidegroup.net for the Teams link.
Bring your coffee and curiosity…no prep required.
If you’ve already read Book Clubs, Conversations, and Curiosity, you know that at Rising Tide, we don’t host book clubs for the sake of reading. We use them as an excuse to talk, to listen, and to practice curiosity together.
The Go-Giver by Bob Burg and John David Mann is the first book that we've chosen to explore together in this way. Each week, we’re reading one short chapter together and using a few open-ended questions to spark real conversation: no lectures, no wrong answers, just reflection.
Below are our discussion prompts for Chapter One: “The Go-Getter.”
They’re written for teams like ours: busy, service-minded, sometimes too practical for their own good...who want to slow down long enough to notice what these stories have to teach.
How this guide is different from others you'll find online: We keep it chapter-focused. Every set of questions focuses only on the current chapter so there is no foreshadowing, no jumping ahead, no “we’ll get to that in Chapter 7.” The goal is to slow down and savor the smaller ideas that get lost when you rush to the big themes, and we're going to make sure that team members that are "behind" have enough data points to connect the dots and contribute even if they're not caught up to the current reading.
Use them however you like. Whether you’re reading along with us or just looking for a fresh team conversation starter, we hope these questions help you stretch a little, think differently, and see something new in yourself or your work.
If you tweak or add questions, tell us at partners@risingtidegroup.net. We’ll keep improving this tool for other MSP teams.
In this chapter, we meet Joe, a go-getter who doesn't seem to be getting what he's going for. We are also introduced to his coworkers: Melanie and Gus, who help connect him with Pindar, or the Chairman, who agrees to tell Joe the huge trade secret that will surely be his key to success.
Creatures of a day! What is anyone?
What is anyone not? A dream of a shadow
Is our mortal being. But when there comes to men
A gleam of splendour given of heaven,
Then rests on them a light of glory
And blessed are their days. (Pindar, Pythian 8)
Want to hang out in these conversations with the Rising Tide team? We meet Fridays at 9:30 AM ET to talk through important business, technological, and communal developments, and for the next 14ish weeks, The Go-Giver! If you’re an MSP owner, consultant, or service professional who wants to grow your team’s emotional intelligence alongside your technical skill, you’re welcome here.
Reach out to partners@risingtidegroup.net for the Rising Tide Fridays Teams link. Bring your coffee and curiosity: no prep required.
In By the [run]Book Episode 9, Connor and Robbie power through the rest of HaloPSA v2.2 — unpacking dozens of quality-of-life updates, automation improvements, and admin refinements that make daily operations smoother. From new calendar defaults and contract history tabs to long-requested rule enhancements and KB management upgrades, the pair keeps the banter light and the insights practical.
Perfect for MSPs, admins, and implementation teams who want to understand not just what’s new, but why it matters in real-world use.
Watch Now: By the [run]Book: Episode 9
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
This new Other Uses tab shows every place an email template is used — from rules to mailboxes to notifications.
A new system action logs each time qualification matching runs on a ticket.
CAB selection in approval processes can now reference a custom field.
Portal users can start a ticket and save progress as a draft.
A new trigger fires whenever a quote is revised.
Runbooks can authenticate via Halo API Bearer Token.
Simplifies calendar management for agents.
Administrators can update review dates for multiple KBs at once.
Add KB fields to approval forms for better context when reviewing changes.
Improves data visibility for developers working with email template records.
Sales emails can be attached as CRM notes to keep records complete.
Introduces SKU validation during stock receipt.
New tabs track every edit made to contracts.
Calls no longer end automatically when linked or logged to a ticket.
Quick Time entries now respect ticket-type charge rate rules.
Canned Text can include file attachments.
Control Quick Close visibility per ticket type.
PDF Templates now respect access controls.
The team demonstrates Renada’s custom “Log Site Visit” action as a cleaner alternative to Halo’s arrive/leave process.
Show the Main Contact directly in Site views.
The Team label is clickable and opens the team configuration.
A new system use allows receiving all POs from a ticket in one action.
Event management can map incoming data to the ticket Source field.
The Add Note to Parent option can now be combined with other system uses.
Custom SQL single select fields can now auto-populate with their first value.
A new User field is available for actions.
Rules can evaluate total time logged to trigger pop-ups or actions.
Backend optimizations enhance ServiceNow sync reliability and speed.
Mail campaigns can leverage dynamic distribution lists.
Large reports now load page-by-page to avoid browser timeouts.
Adds criteria-based indexing controls for AI and search.
Different holiday types can have their own allowances and carry-over rules.
Rules can now check if a checkbox is not selected.
You can insert dynamic values into recurring invoice notes and references.
Charge rate controls can now be applied at the top-level entity.
Lookup profiles can now trigger based on checkbox fields.
Choose which mailbox sends automated reports.
Dashboard filters support multiple selections at once.