By
El Copeland
July 2, 2025
•
20 min read
Business
Solutions
News
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.
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:
A short, focused check-in on the systems you want our guidance on. for:
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.
We read the release notes so you don’t have to. You’ll get:
We’ll chase the vendor on your behalf. That includes:
If something breaks in a tool we’ve implemented or documented, we’ll:
Hand Rising Tide the recurring and tedious-but-necessary tasks tied to administrative upkeep inside your platforms like:
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:
If we find something that should be a project, we’ll tell you and help you decide how you would like to move forward.
$900/month
Includes up to 5 hours of support time
Bundled with licensing or dashboard/reporting add-ons, if you need them.
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.
In Episode 4 of By the Run Book, the team digs into HaloPSA v2.192 with a mix of technical deep-dives and practical tips for MSPs. Robbie and Mendy walk through improvements in holiday approvals, contract schedule plans, and important security updates like webhook authentication. They also explore quality-of-life changes in ticket type restrictions, AI suggestions without an AI license, and new admin mode controls. To wrap up, Robbie demos his “Quick Ticket” browser extension for lightning-fast ticket creation without breaking your workflow. Whether you’re streamlining internal processes, tightening security, or speeding up ticket logging, this release has something to improve your day-to-day.
Watch Now: By the [run]Book: Episode 4
Robbie's Quick Tickets: Halo Quick Ticket - Microsoft Edge Addons
HaloPSA version 2.188 brought a variety of usability and backend enhancements—from runbook triggers in chat to finer-grain billing logic and cleaner settings layouts. In Episode 2, Mendy and Connor walk through these updates, troubleshoot common gotchas, and share the kind of real-world implementation advice you can only get from people deep in the trenches. They also made a point to mention a few times to add feature requests at ideas.halopsa.com
Watch now: https://youtube.com/live/6tjM4SGOcB4
Busy MSP? This guide recaps the episode’s major updates, links you to key moments in the video, and flags anything that might deserve extra caution in deployment.
Join us July 22, 2025 for Episode 3, where we'll start to cover v2.190!
Chat flows can now kick off integration commands—including runbooks. Embed chat on your website or in Teams, and let Halo handle the routing. You could:
⚠️ Be careful what runbooks you expose publicly—especially if they modify data.
You can now toggle the notification sound on or off—but the visual popup still appears. You still can’t upload custom sounds, and notifications can get out of hand across tabs.
💡 Bonus tip: You can suppress sound notifications per rule, but they may still clutter the alert pane.
Enable WebSockets for faster, real-time alerts instead of using the default polling (heartbeat). This reduces delay in receiving internal or backend alerts.
Debug runbooks, automations, email failures, and integration issues using the new service monitoring pane. It logs each backend action so you can pinpoint where workflows failed.
🔍 You no longer need to email Halo support for log digging—huge time-saver.
You can now set separate rates for time and distance in a single travel charge entry. Perfect for billing both mileage and technician transit time in a single step.
Settings like mailboxes, templates, and rules have been reorganized into distinct tabs instead of being buried under “General.” More logical, but prepare for some retraining of your internal muscle memory.
Set a contract status to auto-expire when the end date passes. A scheduled task now flips expired contracts to “inactive” if configured.
⚠️ Hidden contracts can cause trouble—pair this with automated tickets or alerts to track renewal conversations.
You can now:
Connor and Mendy share tips for keeping messy product catalogs from polluting QuickBooks/Xero.
To-do groups can now be restricted to specific customers. Use this to tailor onboarding checklists, project tasks, or compliance processes.
⚠️ Only one customer per group for now. Feels clunky, but it’s a start.
Quickly duplicate complex billing logic with a new “Clone” button. Ideal for MSPs using multiple templates per client or those needing custom combinations for each contract type.
Billing plan rules can now reference:
Use this to get laser-precise about when a contract or billing model should apply.
Choose between traditional storage (custom fields added to core tables) or a new “separate table” method. The latter avoids bloating system tables—but still stores multi-selects as comma-separated strings (ugh).
You can now import vendor quote spreadsheets directly into Halo quotes. Set up mappings for Cisco, Dell, or distributor quote templates and save serious time.
You’re no longer stuck using Halo’s shared apps. Bring your own app registration to limit scopes, improve auditing, and align with internal security policy.
A new setting condenses prorated adjustments into a single invoice line (instead of two). Easier to read—but harder to debug.
🔍 Consider leaving this disabled unless your team fully understands the logic.
The HubSpot sync continues to be... challenging:
Proceed with extreme caution or disable it entirely.
This release didn’t come with any headline grabbers—but for those deep in Halo, it delivered a handful of quality-of-life improvements and some thoughtful backend fixes. Below are the features worth your attention, especially if you're in billing, approvals, or building project automation.
Watch here now: https://youtube.com/live/WGnJXYeSxN4
Delegate Approvals for Tickets | v2.190 #830512 | 2:28
Ticket approvers can now assign delegates directly from the agent app ticket detail screen. Great for ITSM or structured orgs, but less relevant for fast-moving MSPs unless you're running approvals regularly.
Manual Proration Made Invoice-Ready | v2.190 #823611 | 4:18
A new checkbox on manual proration entries lets them show up in the invoicing screen immediately. Particularly useful for mid-cycle adjustments to annual billing, like licensing or domains.
Zero Draft Invoice Handling | v2.190 #819999 | 6:41
Halo will now ignore draft invoices created in Xero, preventing clutter and accidental syncing. You'll need to enable this in the Xero integration webhook settings.
Receive Stock Before PO Approval | v2.190 #829771 | 9:04
You can now receive items before a purchase order is approved. Risky for strict workflows but may fit fast-paced environments where hardware urgency overrides red tape.
Auto-Issue Items from Actions | v2.190 #837101 | 10:21
Set up actions to issue specific inventory items without user selection. Makes fixed-fee tickets more maintainable. Bug alert: doesn't yet work with quick actions—still requires a workaround.
Ticket ID in PDF Template Item Tables | v2.190 #837112 | 12:39
PDF templates can now pull the associated ticket ID into item tables—helpful for clarity in documentation, reporting, or client-facing PDFs.
Read-Only Appointment Subjects | v2.190 #829744 | 17:43
Admins can lock appointment subjects to match the ticket/project. It’s a small control that helps standardize records across large teams.
Editable Invoice Line Contract Links | v2.190 #823492 | 20:41
You can now edit the contract tied to a specific invoice line—especially valuable if you're tracking profitability across services with multiple contracts.
Prevent RMM from Changing Device Types | v2.190 #821917 | 24:58
ConnectWise RMM imports won't overwrite an existing device type anymore, assuming you check the new box.
QuickBooks Name Collision Workaround | v2.190 #829321 | 26:05
Halo now checks for matching item names before syncing, and links them rather than creating duplicates. A clever patch for a QuickBooks API issue.
Ticket Type as Rule Outcome | v2.190 #831422 | 27:28
You can now set ticket type via rule outcomes. Great for automating triage flows or conversions between types during lifecycle changes.
Team Custom Fields in Details Tab | v2.190 #831994 | 31:13
You can finally surface custom fields tied to teams directly in ticket details. Limited use cases for now, but it’s a step toward richer internal data visibility.
Granular Attachment Permissions | v2.190 #829812 | 32:36
Admins can now control who can view, edit, upload, and download attachments—down to the ticket type and role level.
Track Completion of Sales Lines | v2.190 #832113 | 33:58
Sales order lines can be manually or automatically marked as “Complete.” Adds helpful clarity, especially when you're tracking partial progress across installs or shipments.
Runbook Execution Modes (Parallel/Sequential) | v2.190 #830301 | 35:27
Control how runbooks trigger: run steps in parallel for speed or in series to avoid conflicts and ensure data accuracy.
Column Profiles for Invoices & Quotes | v2.190 #834755 | 44:01
Column profiles now work on sales orders, quotes, and invoices. You can personalize the data you see—and what you hide—for cleaner views.
Runbook Stats Tab | v2.190 #830996 | 35:27
Basic run metrics are now visible in a tab. Not yet robust for reporting, but a decent glance for usage and debugging.
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword. And join us on August 5th for a show with Robbie and Mendy: https://youtube.com/live/ApiYEmWJsPU!