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 8 of By the [run]Book jumps into HaloPSA v2.200 beta features. From distributor integrations (ArrowSphere, Raynet), AI controls, forecasting improvements, Pax8 automation, and new ticket workflow controls, there’s a lot for MSPs to explore. This episode is packed with updates for finance, automation, security, and reporting that can streamline operations and open new possibilities.
Watch Now: By the [run]Book: Episode 8
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
ArrowSphere integration is now available
Raynet One integration is now available
Added Mobile App release versions and release information
When using Save As on Configuration Areas the Access Control List is now copied
Actions that send Webhooks can now be triggered on Create, Edit, Delete
Added Mark Billed/Not Billed to the CSP Invoice List
Added ability to override price per currency
ITIL Ticket Type and Ticket Type Group added as criteria for Ticket Rules
Added option for Workflow Step to show a message rather than being added to the Ticket History
Added ability to self approve Invoice Approvals
Added Opportunity Value and Opportunity Profit as criteria for Opportunity Approval Rules
JWT PS256 Assertion is now supported for Custom Integrations
Improved logging has been added to Freshdesk Migrations
Added mandatory fields when manually creating a Customer
Fixed issue where $_userid variable would not use Ticket User when using a non logged in session
Added ability to link CSP Licenses to Customers by Tenant ID
Added new rule criteria "Is draft amendment"
Removed Change Sequence field from Device and Site endpoints
Added Item Supplier SKU to Quotes, Sales Orders, Purchase Orders and Invoices
Added $_CONFIRMFEEDBACK variable to allow inclusion of feedback links in emails without risk of submission by web scanners
Added ability to paste images into plain text notes
Added "None" option to Opportunity Pipeline Stage
Added paragraph formatter to Knowledge Base Articles
Added Recurring Invoice IDs to Project Deliverables
Added new Virtual Agent function 'Web Search'
Added a setting to disable anonymous access to Reports
Added a setting to mark Actions created from forwarded emails as Private
Reduced the refresh interval on Ticket Details
Added ability to push Purchase Orders to Xero using converted currency
Fixed issue where Subscriptions imported without End Dates would default to 1st Jan 1970, they now default to the Contract End Date
Added ability to map Employee Type field from Entra ID
Added ability to hide Ticket Type selection at Action level on new Ticket screen
Added Collision Detection for Billing Entities
Added Ticket Tags as criteria for Ticket Rules
Added ability for Ticket Rule Outcomes to set User Custom Fields
Added Configuration Tracking for Lookup Profiles
Updated interactive login flows for Custom Integrations
Added ability for Feedback endpoint to filter by Start and End Dates
Added ability to auto create Items and Invoices from Pax8 Subscriptions
Added Client, Mailbox and End User fields to Qualification Matching
Added Customer Type field to Ticket Details screen
Added option to clear Supplier on Recall Actions
Improvements to Forecasting Module
Added Holiday Rules to Schedules
Added ability to auto group Quotation Lines by Item Group
In Episode 7 of By the [run]Book, the team finishes off highlights from v2.196 before diving into the first v2.198 beta features. From multi-column ticket layouts and SQL-driven scheduled tickets to dynamic field visibility groups, AI exclusions, and multi-page ticket logging, this release is stacked with quality-of-life improvements and automation power-ups. A must-watch for MSPs looking to fine-tune service delivery and streamline configuration.
Watch Now: By the [run]Book: Episode 7
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Lets you define how many columns appear in end-user ticket forms.
Filter CSP mappings to assign values by Azure group membership.
Schedule tickets dynamically based on SQL queries for assets.
Prevent certain appointment types from including client attendees.
Ticket areas can now display custom images in the header.
Improved reporting with stacked bar splits.
Projects tasks can now follow sequence numbers.
Quote settings and approvals are now managed separately.
Show product list prices in the target quote currency.
Billing configuration split into clearer sections.
HaloPSA integration now supports remote session invites.
Introduces improved line total calculations.
Control the order of CRM note custom fields.
New grouping logic for dynamic field conditions.
Exclude sensitive customers from Halo’s built-in AI.
Control which asset columns users see when logging tickets.
Pull products straight from Ingram Micro.
More control over “Favourite Services” in the portal.
Ticket Kanban boards improved.
Granular permission for pushing config changes.
Improved grouping for user access restrictions.
Settings now stored in a new format.
Mailbox sender restrictions expanded.
Single Select IDs can now use non-integer values.
Cloned tickets can now inherit milestones.
Credits can now be applied as payments.
Contracts can now be swapped in the review list.
Enhancements for AWS usage billing.
Split ticket forms into multiple pages.
Bulk toggle users between service and non-service.
Item groups now support a default sequence.
Episode 6 breaks down HaloPSA v2.196 (stable). We cover improvements to billing recalculation and recurring invoice scheduling, on-prem integration security, ticket UI/UX (action groups, field group behavior), role-level controls, chat on existing tickets, and a big boost to project billing performance in Ready for Invoicing. Ideal for MSPs tightening finance, project, and automation workflows in Halo.
Watch Now: By the [run]Book: Episode 6
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Choose a consistent default font for editors in tickets and actions.
A banner warns when integrations allow unauthenticated webhooks.
Recalculate billing for a selected customer over a defined window.
Control when a billing rule applies.
Declutter your recurring invoice view.
Filter or route tickets by the mailbox they came from.
Security and reliability enhancements for on-prem connections.
Make start dates automatic for certain ticket types.
Keep grouped fields always visible.
Automate around CRM note activity.
Runbooks can process text-only API responses.
Safer, clearer Excel imports.
Bill on an exact day each month.
Lock milestone structures from templates.
Let end users chat directly on an existing ticket.
Reduce confusion on sales order lines.
Granular “log on behalf” controls.
Group actions into dropdown menus on tickets.
A big boost to project billing performance.
More events to hook automations into.
For more insights, see our guide on choosing the right ticket status colors in HaloPSA
Also, check out our partner Renada’s video: From Feedback to Forest: Automating Tree Planting in HaloPSA