Would be great to have a calculation method that allows you to calculate business (working) days/hours/minutes between two dates. This allows for more accurate SLA reporting. Business days should also take into consideration local public holidays as well as weekends e.g. in New Zealand Waitangi Day is not a working day and therefore should not be included in calculations between two days.
An example of this calculation in action would be:
Ticket created on a Friday minus ticket closed on a Tuesday with Monday being a public holiday = 2 days and not 5.
Excluding weekends from lead timing calculations would be extremely valuable for avg sake. (Especially given there’s no median calc and weekends introduce skew to the distribution)
Yes this is absolutely needed! We would have to purchase operations/data hub just to do this simple custom calculation. OR get a third party app. It really should already exisit.
@JJahnke that third-party app exists, and it’s free.
I built Business Days Calculator specifically for this. It adds four workflow actions to HubSpot, the one relevant here is Calculate Business Days, which counts working days between two dates, excludes weekends, and excludes public holidays for your country (145+ countries supported, including New Zealand with Waitangi Day and all regional variants).
For the exact use case SKirwan described, ticket created Friday, closed Tuesday, Monday is a public holiday = 2 days, it handles that correctly out of the box.
The setup for SLA tracking:
Create a custom numeric property on your Ticket object, e.g. “Business Days to Close”
In your ticket closed workflow, run the Calculate Business Days action with create date → close date
Write the result to that property
Report on that property instead of HubSpot’s native date diff
No Operations Hub required. No credit card. Works on any HubSpot plan that supports workflows.
We absolutely need the possibility to calculate how much time did each card spend at any stage, of any object, in hour business hours. Don’t know what people do with cumulative time time in x stage in consecutive hours, but for almost any analysis, this is not usefull!