By
El Copeland
August 21, 2024
•
20 min read
Business
Tutorials
Choosing the Right Ticket Status Colors in HaloPSA
Have you implemented unique colors for your Ticket Statuses in HaloPSA?
Coloring these Statuses adds a great Quality of Life to your Agents working tickets. Often, it is treated as a nice-to-have or “let’s just make it look pretty,” which are fine if it works for you. However, we invite you to imagine instead with us: what if you could leverage symbolic colors that guide an Agent through your defined ticket process. What if you could implement that in a reasonable way?
So, to help lessen that decision fatigue for you since we know you’re busy customizing every other setting in HaloPSA as well, here is the framework that Rising Tide uses to approach customizing these settings to help you quickly and sensibly label your Ticket Statuses. In a future article, we’ll tackle Ticket Action color codes; however, the concepts will generally remain the same.
Laying out the Ticket Status Colors Framework
Before we jump into coloring statuses, let’s start by defining a ticket’s lifecycle according to how your Agents need to allocate their attention to those tickets, whether that is dictated by standard professionalism or ensuring SLAs are kept. For the sake of this conversation, we are going to address these ticket attention phases with the segments: Normal Attention, Elevated Attention, or Inert Attention.
Normal Attention
Ideally, your Agents receive a ticket and all things are “Go,” they have everything they need to start working, and then Close the ticket when they've successfully completed the task and can rest on their laurels (or move on to the next ticket!).
We recommend all Normal Attention tickets to be assigned “cool colors” like greens, blues, and purples. (And not cool because we think they’re rad, cool as opposed to warm colors, more information here on color theory) Statuses like New and In Progress generally belong here. We have the ticket, everything is going as planned. What a perfect, serene world. Peaceful, isn’t it?
Unfortunately, that’s not the reality in most of our businesses! What happens when tickets require extra attention or action to ensure their timely completion?
Elevated Attention
Here in Elevated Attention is where we see statuses like Escalated, Pending Approval, or Reopened: tickets that we need to be actively thinking about and revisiting, especially ones that are keeping our SLA clock running. To inspire action and increase visibility, we’re using warm, fiery colors like Orange, Red, and Yellow.
What if there is a ticket where we cannot take immediate action, or it doesn’t warrant it? That’s our last category: Inert Attention.
Inert Attention
There will be times when our tickets are active but there is literally nothing we can do but wait. The SLA clock isn’t running, so we don’t need to worry about taking action on these just yet: statuses like Waiting on Client or Waiting on Vendor. We recommend using greys to signify these statuses’ inactive character.
In general, we recommend you set up HaloPSA to do most of the status setting and remembering to move tasks in and out of statuses, especially Inert-type statuses. Specifically, when setting up these Inert Attention statuses in HaloPSA, be sure to build those Ticket Statuses, Ticket Type Settings, and your related Workflows so when a ticket enters or exits an Inert status, it automatically puts the ticket on or removes it from SLA hold. You can see examples of these settings in the screen captures below.
Some examples of this recommendation in action could be:
- Setting a Waiting on Client ticket to Attention Required when a customer replies to an email
- Setting a Waiting on Vendor ticket to Attention Required when a Supplier updates
- Setting a ticket to Scheduled upon creating an Appointment (Ticket Type Settings: Status after user appointment booking (resource booking), or Status after Agent creates appointment)
- Automatically setting Waiting on Client tickets to Closed after a certain number of hours with no reply according to SLA rules you set.
Ticket Status Colors Framework in Action
With all of these ideas in mind, we suggest as you approach customizing each ticket status, you ask:
What type of Attention do I expect of my team at this status: Normal, Elevated, or Inert?
When you have that answer, choose a color from the suggested family. Remember that color for other statuses you may have for other Ticket Types so it stays consistent regardless of what Area your Agent is operating from!
Here are some examples for what we specifically recommend to Rising Tide Customers. You will likely not need all of them, depending on your MSP’s needs:
Normal Attention
- Brand New/Assigned (Waiting on You): Green — Ticket is newly created and waiting for initial action. Green indicates readiness to start and clear action needed.
- Claimed/Work in Progress: Blue — Ticket is actively being addressed towards resolution. Blue symbolizes confidence in ongoing work and progress.
- We’d be remiss if we didn’t specifically call out that at Rising Tide we recommend that your Agents should not be "Claiming" tickets until they're ready to work on them.
- Closed: Black — The ticket has been fully resolved and all necessary actions are completed. Black signifies completion and closure of the ticket.
Elevated Attention
- Pending Approval: Yellow — Awaiting authorization or approval to proceed. Yellow is high-visibility and unique to call attention to follow up that may be necessary.
- Escalated: Orange — Moved to a higher level of support due to complexity or urgency. Orange highlights urgency and attention required.
- Customer Updated/Vendor Updated/Approver Updated: Orange— Orange is used to indicate recent release from a paused status like Waiting on Customer or Waiting on Vendor and subsequent re-instating of the current SLA timer, if applicable.
- Attention Required: Orange — Elevated attention needed following removal from an SLA hold.
- Reopened: Red — Previously closed/resolved ticket is active again due to additional issues or dissatisfaction. Red indicates a critical reactivation that needs immediate reassessment.
Inert Attention
- Waiting on Client: Grey — Progress on the ticket is paused because it requires input or action from the client. Grey suggests inactivity from the MSP’s side, waiting on external action.
- Waiting on Vendor/Waiting on Parts: Grey — Progress on the ticket is halted while waiting for action or information from an external vendor. Similar to waiting on client but specific to external vendors.
- Scheduled: Purple — Scheduled could also technically be included in the Normal category, hence the cool purple. Denotes a paused status where work is planned, but no active work is required.
- Resolved: Teal — Similar to Scheduled, Resolved straddles the Normal category as well. The issue within the ticket has been addressed, awaiting final closure or verification from the requester. Teal is a calm yet upbeat color indicating resolution but awaiting final closure.
As with most rules, there are going to be times when items cross between phases, or you may operate differently and not define a ticket status the same way we did here.
Maybe you have some color-blind technicians on staff and decide to use completely different colors completely or none at all. (If you do want to create a color-blind friendly palette, here’s a great resource.)
Maybe you want to choose different values (light or dark) within a certain family than what Halo provides.
Good! Break our rules. They're just here to help you decide what you do or don't actually want.
Our main recommendation is that you use your best judgement on what is right for your team and just be consistent which sometimes means keeping it simple. And let us know what you ended up doing, you may help someone else. Happy customizing!
Throughout my career, I've had the joy of leading many diverse and multifaceted teams.
Community building, especially within the technical community, is truly at the heart of what I do. I’m dedicated to fostering inclusive spaces where professionals can connect, share insights, and grow a culture of innovation and ongoing learning together, both in-person and when the team is 100% remote. I take pride in my ability to lead with both clarity and empathy, deftly handling the complexities of technology-driven projects while always keeping the human connection at the forefront of every decision.
For companies seeking consulting and project work, I bring a deep understanding of operational efficiency and project management. I am skilled at not only identifying areas for improvement but also implementing strategic solutions that enhance productivity and outcomes. My strong background in technology, education, and people management allows me to seamlessly integrate innovative tools and processes to address specific challenges, ensuring that projects not only meet but exceed expectations, and that teams are motivated, well-coordinated, and focused on delivering and maintaining organizational goals.
Outside the office, I enjoy blueberry muffins, Doctor Who, weight-training, gardening, and spending time with my cats.
See some more of our most recent posts...
By The [Run]Book: Episode 1
What do webhooks, Agent Trophies, and a 10-year scheduler have in common? In Episode 1 of By the [Run]Book, consultants from Renada and Rising Tide walk through HaloPSA releases 1.86 and 1.88—field-testing features, skipping the fluff, and asking better questions than the release notes ever do.
Read post
Welcome to By the [Run]Book
HaloPSA features, field-tested.
We’re not here to sell you a perfect system. We’re here to show you what’s possible when smart, slightly feral people get curious about tools that were allegedly designed to help us.
By the [Run]Book is a new podcast collaboration between consultants from Renada and Rising Tide, where we dig into the latest HaloPSA features, challenge what’s been handed to us, and ask: What else could we do with this?
No fluff. No shiny demo decks. Just real-world testing, practical breakdowns, and a healthy disrespect for default settings.
By the [Run]Book – Episode 1 Feature Guide
By the [run]Book's first episode breaks down HaloPSA releases v1.86 and v1.88, this episode explored what’s new, what’s weird, and what’s actually worth your time. Use this guide to follow along.
Event Management | 2.186 #798529 | ▶️ 6:06
Create and update tickets based on webhook events—without needing Runbooks.
- Easier interface for handling alert data
- Trigger rules based on payload content
- Map fields into tickets dynamically
Chat Interface Redesign | 2.186 #764942| ▶️ 10:06
The new chat view makes internal and client conversations more manageable.
- Conversation list/table instead of floating popups
- MS Teams chat support improved
- Much more usable in high-volume settings
Tabbed Interface in Halo | 2.186 #446952 | ▶️ 12:03
Multiple tabs now open inside Halo, not your browser.
- Reduces tab clutter
- Smooth for screen sharing
- Plays well when Halo is run as a desktop app
Agent Trophy Feature | 2.186 # 831583 | ▶️ 14:28
Yes, agents can now earn trophies for closing tickets.
- Visual badges on agent records
- Available in assignments and dashboards
- Fun, but scoring logic is a bit suspect
- Custom Leaderboards via CSS. Mostly a morale booster—not reporting-grade insight
Date Filters, Forecasting Module + TimeGPT Integration | 2.186 #830461| ▶️ 19:41
Prevent retroactive ticket floods when new rules are applied.
- Set start dates to control retroactive logic
- Helps avoid spam from old data
- Crucial for clean automation rollouts
Enforce Unique Email Addresses | 2.186 #829650 | ▶️ 20:43
Avoid duplicate users and weird portal issues.
- Blocks user creation if email already exists
- Critical for integrations and self-service portals
- Best turned on early before it breaks things quietly
Opportunity Variables: Annual, Monthly, One-Off | 2.186 #828897 | ▶️ 22:31
New fields help break down potential revenue at-a-glance.
- Available for ticket templates and reporting
- Auto-updates from quotes (with correct config)
- Useful for sales forecasting and quote summaries
Runbook Sleep Steps | ▶️ 30:55
Introduce delays in automation logic—finally.
- Wait X seconds before next Runbook action
- Great for API pacing or async dependencies
- Simple but long-awaited
To-Do Groups Linked to Clients | ▶️ 33:28
Tie checklists to specific clients.
- Good for client-specific onboarding/offboarding
- Still clunky, but now usable in context
- Replaces “one-size-fits-all” task lists
Dynamic SQL in Ticket Actions | ▶️ 33:34
Use SQL-powered fields in your ticket logic.
- Previously unreliable, now stable
- Can pull dynamic field values into workflows
- Adds power to advanced configurations
Xero + Avalara Sales Tax Integration | ▶️ 34:15
Auto-calculate sales tax in Halo quotes synced to Xero.
- Uses Xero’s built-in Avalara tax engine
- Requires
invoice.updatedwebhook enabled - Real-time, regionally compliant tax logic
Direct User-to-Client Association | ▶️ 37:40
Users can now be tied directly to clients, no site required.
- Supports more flexible org structures
- Great for shared-stock or multi-client setups
- May simplify certain workflows
10-Year Scheduling Period | ▶️ 42:24
Because someone, somewhere asked for it.
- Schedule things a decade out
- Useful for contract reminders or licensing renewals
- Feels deeply aspirational
Got a Feature You Want Us to Cover?
Introducing Rising Tide Proactive Support
Tired of tools slipping through the cracks? Discover why Rising Tide built Proactive Support: a low-lift, high-impact way to stay in control of your systems like HaloPSA, Hudu, and Rewst—without needing a full consulting engagement.
Read post
Built for Busy MSPs: Why We Created Proactive Support
While we pride ourselves at Rising Tide on being clever, we didn’t make this up on our own.
Over the past year, multiple clients told us the same thing in different ways:
“We don’t need a full-on consulting. We just need someone to help us stay on top of the tools we already have.”
“Can you set aside time each month to tell us what’s working, what’s not, and what we should actually do next?”
“Honestly, I just want to know if anything’s falling through the cracks.”
MSPs weren’t talking about emergencies. They meant the small stuff. The not-yet-broken-but-might-be. The features that got launched but never rolled out. The bugs they forgot to follow up on. The process that made sense when they built it... but not anymore.
So we listened and built out a Proactive Support offering for teams like yours. Support that pays attention, leveraging the best of Rising Tide to make the best of your systems. It’s not reactive. It’s not rushed. It’s not about being broken.
It’s about staying in control, without wasting time figuring out where to start.
What You Get Each Month
Designed for Rising Tide clients who’ve already implemented tools like HaloPSA, Hudu, and Rewst, and just want to keep things running smoothly without spinning up a full project or workshop every quarter.
Here’s what Proactive Support looks like in practice:
1. Systems Health Review
A short, focused check-in on the systems you want our guidance on. for:
- Are automations running like they should?
- Are there missed SLAs or ticket pileups that can be fixed with better workflows?
- Are there any underused (or over-complicated!) features?
You’ll walk away with a small, clear action plan that you can execute on your own or leverage the Rising Tide team to complete.
2. Feature Release Briefing
We read the release notes so you don’t have to. You’ll get:
- Highlights of what’s new
- Suggestions for features worth trying and what isn't
- Warnings about what’s likely to break or change
3. Vendor Liaison Support
We’ll chase the vendor on your behalf. That includes:
- Logging and tracking bug reports
- Validating bugs and escalating to dev teams directly.
- Identifying workarounds and assisting in implementation.
- Following up on feature requests or stuck tickets
- Communicating feature requests clearly (and tracking them)
4. Immediate Error Support
If something breaks in a tool we’ve implemented or documented, we’ll:
- Help triage and fix it
- Identify if it’s a vendor issue
- Tell you clearly if it needs escalation into a project
What Proactive Support is Not
To be clear, the Rising Tide Proactive Support Plan is not consulting. Proactive Support is only for systems we’ve implemented and reviewed. It doesn’t include:
- New tool or system implementation
- Redesigning workflows or processes
- Training or onboarding
- Deep reporting or strategic planning
If we find something that should be a project, we’ll tell you and help you decide how you would like to move forward.
Pricing
$900/month
Includes up to 5 hours of support time
Bundled with licensing or dashboard/reporting add-ons, if you need them.
Let’s Be Real
The goal isn’t to keep you dependent on us. It’s to help you feel like you’re on top of your systems instead of under them.
We’ll help you spot friction before it becomes fire, surface fixes you might’ve missed, and give you the clarity to act, delegate, or table things with confidence.
That’s the tide we’re trying to raise.
Ready to add Proactive Support? Or want to see a sample check-in?
Contact Rising Tide Consulting Today. We’ll show you what this looks like.
2025 Q3 Newsletter - Get more out of Halo, Hudu, and Rewst
Rising Tide’s Q3 2025 newsletter is here—with fresh updates shaped by the conversations we’ve had with you on the road and in your consulting calls. Check out our new Proactive Support plan, admin tools in the client portal, and hands-on YouTube training for HaloPSA, Hudu, and Rewst. Let’s keep your team sharp and your systems humming.
Read post
It’s been a few months since our last update. We’ve enjoyed seeing many of you on the road at Right of Boom, MSPGeekCon, and Flow. Hopefully you’ve taken the learning and tools you picked up at each even and are using them to their fullest!
In light of the conversations we’ve had with many of you at these conferences and in your consulting calls, we’ve been building a few new offerings that we hope will help you and your teams continue to learn and grow in your use of HaloPSA, Hudu, and Rewst. Take a look at our new Proactive Support, YouTube videos, and Administrative tools for you in the Rising Tide Portal.
Proactive Support with Rising Tide
Shaped directly by your requests, the Rising Tide Proactive Support plan is for teams who want another set of eyes on your systems, to make sure you’re getting the most out of your subscriptions. This new monthly support plan includes:
- A health review of applicable systems
- Updates on vendor features that matter to you
- Vendor liaising regarding bugs and requests (we’ll validate bugs and escalate to dev teams directly. If there's a workaround or fix we'll identify that and provide them for you too.)
- Hands-on support for tools we’ve implemented or reviewed
Read more about it here:
https://www.risingtidegroup.net/thoughts/introducing-rising-tide-proactive-support
Learn With Us
We’re actively growing our YouTube channel to create more and more helpful resources for you as you implement your tools and automations. Of note, check out:
- By the [Run]Book – A bi-weekly series, aired live with our friends at Renada where we review HaloPSA’s release notes and make suggestions on what to implement (and what not to!) in your HaloPSA instance. Watch the first episode here.
- Drag-and-Drop Dispatching in HaloPSA – Jason's video on how to visually schedule tickets for your technicians using dashboards and filtering lists.
- Streamline Your MSP Ticket Closure Process with HaloPSA – Jen's latest video on systematically restricting ticket closures and communicating why to your technicians until they’ve completed associated tasks, tickets, and activities.
There’s plenty more! Be sure to subscribe to our channel and hit the bell to get notified when new videos drop.
Let's keep your projects moving!
As a reminder, if you have hours on your pre-pay total, we keep them viable as long as you have a project on the books with us within a calendar year. If you want to know what your current hours are, visit the Rising Tide user portal at portal.risingtidegroup.net. In this area of our website, you can:
- View hours remaining on pre-pay blocks.
- Submit and track tickets.
- Refill Pre-Pay hours for consulting work.
- View feature requests and bug reports submitted to Halo by Rising Tide.
We recommend booking an hour at least once a month, and more frequently if you have work you want to get done! We don’t charge cancellation fees, so book time freely with any of our consultants and we’ll get your sorted. To book time, access your project from the portal to grab your booking link or pull it off any of the recap emails sent.
- Mendy Green - Halo General, Automations – Halo and Rewst, Hudu General and Migrations from IT Glue
- Jason Parsons - Halo General
- Jen Butler - Automations – Halo and Rewst
- El Copeland - Halo Invoice/Quote/Email Templates, UX/UI, Branding+Marketing
Of Note
A recent change to how HaloPSA processed notifications caused them to break in certain conditions. If your notifications stopped working, update your Permissions - Base role client restrictions to grant all clients to role members. Reach out for more specific instructions if you need it.
Lastly, as a bonus, enjoy the new Rising Tide theme song generated with Suno by our very own Jason Parsons.
Thanks for trusting us and being part of this work with us. We’ll keep refining what we offer based on your feedback so don’t hesitate to reply and tell us what’s working, what’s still messy, and what you’d like to see next.
Until next time,
The Rising Tide Team