On January 21, 2026, HubSpot released seven platform updates spanning workflow automation, calling features, task management, and data visibility improvements. The updates address long-standing user requests, particularly around business day timing for automated workflows and enhanced task organization capabilities.
This release includes features currently in beta alongside generally available enhancements that expand calling functionality, streamline approval processes, and improve data visibility at the company level.
HubSpot calling users can now manage their calling connection through the Chrome extension, eliminating the need to keep a separate browser window open for inbound and outbound calls. The feature is currently in public beta and requires users to install or update their Chrome extension through the Chrome Web Store.
Why It Matters: Maintaining call connections in the background through the extension reduces window management overhead and streamlines the calling workflow. Users can focus on CRM tasks while remaining available for calls without switching between multiple browser windows.
For more details, visit: Chrome Extension Calling Support
The Sales Power Dialer now extends beyond contacts to support deals, companies, and leads objects. This public beta feature allows sales teams to initiate power dialing sessions directly from these index pages, with task object support coming soon.
Why It Matters: Sales teams can now accelerate outbound calling workflows from whichever workspace makes sense for their process. Instead of navigating to the contacts page to use power dialing, reps can dial directly from deal pipelines or company views where they're already working.
For more details, visit: Power Dialer Object Support Expansion
HubSpot now provides AI-powered explanations for conversation and ticket routing decisions. When users view routing details, they see human-friendly descriptions of which routing rule fired, who was eligible at that moment, and how the final assignment was determined.
Why It Matters: Routing decisions are no longer a black box. Support managers and administrators can quickly diagnose why conversations landed with specific team members, making it easier to adjust routing rules, train new staff, and troubleshoot assignment issues without recreating scenarios or digging through settings.
Join beta: Assignment Details AI Explanations
Admins can now configure targeted quote approval workflows based on quote properties or properties from associated objects like line items and deals. Instead of requiring all quotes to undergo approval, rules can be set for specific scenarios such as discounts above 30%, enabled eSignatures, or specific line items exceeding discount thresholds.
Why It Matters: This update eliminates unnecessary approval bottlenecks by focusing admin attention on quotes that actually require scrutiny. As quote volume grows, this targeted approach scales more effectively than reviewing every quote, regardless of complexity or risk level.
For more details, visit: Property-Based Quote Approval Rules
Workflows now include an option to exclude weekends from delay actions. When enabled, delays count only Monday through Friday. For example, a contact entering a one-day delay on Friday will proceed to the next action on Monday rather than Saturday.
Why It Matters: This feature aligns automated communication with business operations schedules. Teams can ensure follow-up emails and tasks occur during business hours when staff are available to respond, improving engagement rates and eliminating the complex workaround logic previously required to approximate business day timing.
Request beta: Business Days Workflow Delays
HubSpot now supports breaking down tasks into up to 30 subtasks per parent task. Subtasks can be created in Gantt views within projects, deals, and services, as well as in project records, previews, and the customer success workspace. Subtasks maintain the same properties and permissions as regular tasks.
Why It Matters: Complex tasks often involve multiple discrete steps that don't warrant separate task records. Subtasks provide granular tracking for multi-step initiatives while keeping related work organized under a single parent task, making it easier to delegate specific steps and track progress on larger projects.
Request beta: Subtask Functionality
Company records now display form submissions from all associated contacts on the activity timeline. This consolidates engagement data at the company level rather than requiring users to check individual contact records for form activity.
Why It Matters: Teams evaluating company-level engagement can now view all form touchpoints across the organization in one location. This saves time and provides a more complete picture of company interest, supporting better-informed outreach and coordination across sales, marketing, and service teams.
For more details, visit: Company Record Form Submission Visibility
Workflow Timing Improvements: Business days support addresses a long-standing workflow timing challenge, enabling automated communications to align naturally with business operations schedules without complex workaround logic.
Enhanced Task Organization: Subtasks provide more granular project management capabilities within HubSpot's existing task framework, supporting better delegation and progress tracking for multi-step initiatives.
Expanded Calling Access: Chrome extension calling support and Power Dialer expansion to additional objects reduce friction in calling workflows and meet sales teams where they're already working.
Smarter Approval Processes: Property-based quote approvals enable more scalable management as quote volumes grow by focusing attention where it's actually needed.
Improved Data Visibility: AI-powered routing explanations and company-level form submission views increase transparency and reduce the time required to understand system behavior and engagement patterns.
Several features remain in beta with opportunities to request early access through the links provided above. Teams should evaluate which features address current workflow pain points and consider testing beta features that align with their operational needs.