By
El Copeland
July 8, 2025
•
20 min read
Tutorials
Solutions
News

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.

Episode 20 of By the [run]Book dives into HaloPSA v2.214 with a mix of practical improvements and some quirky additions. Connor and Mendy walk through everything from new dollar variables and asset controls to Avalara fixes and portal enhancements—highlighting what actually matters for day-to-day MSP operations. This episode is especially useful for MSPs refining workflows, automation, and reporting accuracy in Halo.
Watch Now: By the [run]Book: Episode 20
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Mendy and Connor noted this was very useful.
Highlighted during the user action demo as a practical workflow improvement.
Called out as a genuinely useful UI improvement.
Allows more flexibility in how incoming emails are matched to tickets.
Enables automation of asset configuration through API usage.
Introduces a new variable to output custom fields in Q&A format.
Improves visibility into asset changes over time.
Returns the email address of the user associated with a purchase order.
Enhances usability and visibility of search results in the portal.
Provides control over configuration synchronization.
Ensures correct popup behavior when multiple rules trigger.
Makes ticket source available for reporting and filtering.
Adds safeguards when configuring email matching tags.
Allows distribution lists to target all email addresses tied to a user.
Improves clarity in Avalara transaction records.
Adds control over visibility of user actions in the portal.
Improves flexibility when using Accounts and Prospects.
Enables dynamic fields based on asset lifecycle status.
Ensures asset tagging consistency during stock processes.
Adds control over Avalara synchronization scope.
Allows a predefined score for surveys.
Improves visibility when prorating billing items.
Automatically generates a ticket alongside sales orders.
Allows column width customization in list views.
Changes ordering of lists in the team view.
Adds asset status as a usable variable in buttons.
Improves flexibility when viewing lists.
Allows visual customization of buttons.
Enables distribution lists based on ticket criteria.
Adds control over forecast data ranges.
Enhances performance of Azure/Entra sync.
Improves visibility of ticket closure information.
Optimizes webhook performance and payload handling.
Refines permissions for asset management.

Episode 19 walks through HaloPSA v2.212 and v2.214, covering a wide range of quality-of-life improvements, admin controls, and workflow enhancements. Connor and Robbie highlight updates around ticket forms, invoicing, templates, and automation, making this especially useful for MSPs looking to tighten processes and improve day-to-day efficiency.
Watch Now: By the [run]Book: Episode 19
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Allows assets to be linked directly to a client instead of only via a site.
Improves tracking of report usage across dashboards.
Adds control over end-user assignment in templates.
Prevents actions on tickets for stopped clients or sites.
Allows updating custom fields directly via actions.
Prevents approval of expired quotes.
Adds variables for original customer addresses.
Ensures hidden fields do not retain values.
Adds advanced relative date filtering.
Adds preview functionality for templates.
Allows editing of existing meter readings.
Improves grouping of invoice items.
Enables merging duplicate assets.
Displays number of related tickets.
Enhances monitoring integration mapping.
Adds more control to purchase order lifecycle.
Enables workflows triggered by agent emails.
Adds mapping and geolocation features.
Introduces guided project setup.
Allows updating ticket fields post-creation in chat.
Prevents deletion of populated top-level structures.
Improves timesheet usability.
Fixes inconsistent quote PDF behavior.
Aligns quote email behavior with configuration.
Adds access to billing profiles from invoice screen.
Allows use of quote data in actions.
Adds new automation trigger.
Adds rich text support for asset fields.
Prevents closure when tasks remain open.
Adds approvals to activity feed.
Removes agent login option from portal.
Adds ordering control to lookup codes.
Adds planning field to releases.
Enables guided onboarding tools.
Adds note field to consignment lines.
Expands team visibility.
Extends accessibility tools to main app.
Displays previous invoice values.
Exposes billing data to API.
Adds search to selection fields.
Aligns call screen logic with ticket settings.
Links credit lines to original sales orders.
Improves invoice ID handling.
Introduces role-based API identity.

In this episode of By the Runbook, the team continues through the HaloPSA 2.212 release notes and spends time unpacking what several of these changes actually mean in practice. The conversation covers workflow design, mail campaigns, ticket views, reporting, and automation behavior, with especially useful commentary for MSPs trying to decide what to enable, what to ignore, and what to be careful with.
Watch Now: By the [run]Book: Episode 18
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Check out MSP Blueprint for info on runbooks: MSPBlueprint
This allows the ticket screen to automatically refresh when a background automation completes.
Expands qualification matching to include custom field criteria.
Adds delayed and retry-based webhook processing options.
This change limits the available “From” addresses on a ticket action to mailboxes the assigned team can actually access.
Adds Email Address as another attribute option for follower behavior on the portal.
Allows changes to Mail Campaigns after they have started.
Restricts pipeline stages based on opportunity type.
Adds webhook processing options including delayed and retry handling.
Adds the ability to hide tickets from the change calendar.
Adds Service Users as a selectable option in distribution and user lists.
Allows campaigns to be sent from sales mailboxes.
Adds a warning when an action email will fail.
Adds asset relationship mapping during SQL imports.
Adds an isRunning field to asset discovery.
Expands qualification matching with custom field rules.
Allows ticket view to auto-refresh after automation runs.
Adds ability to update currency values on quotes.
Requires comments for negative KB feedback.
Adds control for showing nested tickets.
Enhances AI reporting capabilities.
Restricts KB edits to owners only.
Adds translation support in the portal.
Adds secondary MAC address support.
Adds character limits to text fields.
Adds more fields for OLA and rule reporting.
Prevents approvals from email replies.
Extends field copying to deeper ticket levels.
Adds primary asset as a runbook condition.
Adds AgentID variable for lookups.
Adds reporting changes to config tracking.
Adds filter profiles to child ticket views.
Adds more configuration options to other open tickets view.