Las grandes mentes piensan igual

making the management hierarchy feature—assigning managers and reports—available to all users, not just those with paid seats. This would enhance collaboration and allow more team members to fully utilize the feature without restrictions ... Mostrar más

I can use a calculation property to figure out the number of days since a ticket was opened so I can see how many days a ticket has been open. This is great! Except... I need to get the average number of days my tickets have been open.   The calculation property is formatted as a date and I can't get an average on a date property. I need the option to turn this property into a number format. I can't use a format action in a workflow either because calculated properties can't be formatted (or date, not sure what the issue is).    Can you either change "time between" calculation properties to be formatted as a number and use the number of days or give us the option to format the property as a number instead of date? ... Mostrar más

It would be great to have Inbound Ring Time Analytics within HubSpot calling to identify how long a call rang before it got answered or the caller hung up.    Missed calls (or lack thereof) and/or quick pickup rate is a key metric in B2B equipment/machinery support when equipment is down. But current state in HubSpot, if a caller only rang for a couple seconds (for whatever reason) it shows as a missed call, just as a caller that may have rang for a minute also shows as a missed call. The two scenarios are very different, but currently there is no data on it, so no way to differentiate between the two.  ... Mostrar más

We haven't been able to find a good phone system that our sales and support teams can both use. HubSpot calling almost meets our needs, but our sales teams need a local presence feature so when they make outbound calls their number is masked to look like a local number to the person they're calling.   This improves our connection rate which ultimately helps us drive sales. We're using Aircall right now and they don't have a local presence feature so our connection rate is lower because the numbers aren't local to the people we're calling and this is ultimately making a lot of our numbers show up as spam.   HubSpot calling is getting close so hoping to get my hat in the ring for a feature like this! ... Mostrar más

It is my understanding that when the account level option to allow call recording is turned on, and a call is made through HubSpot from a state that does not require consent to a state that does not require consent, the call is automatically recorded by defailt with no way to turn it off. I suggest that all call recordings are optional.  ... Mostrar más

Please allow us to choose a default folder view of our Workflows.  It's overwhelming for it to always open up to the full list every time. ... Mostrar más

The option to create new tabs in the middle pane of records is great, but I want more options of which cards can be added. Either an option to add a full Properties card, or remove the limit on the existing Data Highlights card (currently limited to just 4 properties). ... Mostrar más

As a recurring HubSpot user, I’m requesting the ability to create a single custom property (e.g., a dropdown or radio button) that can be used across multiple object types—specifically, Contacts, Deals, and Tickets—and displayed in their respective list views (index pages). Right now, I understand that HubSpot properties are object-specific. If I want to track the same information in Contacts and Deals (e.g., “Engagement Stage,” “Lead Type,” or a client tier dropdown), I have to duplicate the property for each object. That means managing multiple versions of the same data, training users to enter it in two places, and introducing unnecessary complexity. Here’s why this change would be so valuable: Efficiency: One shared property saves time and admin overhead. It allows our team to align data across records without switching between tabs or duplicating fields. Data Integrity: No more inconsistencies caused by updating only one object’s version of the property. One source of truth. Usability: Users can see, sort, and update that property directly from both the Contact and Deal dashboards (or Tickets too), making their workflows much smoother. Reporting Clarity: Shared properties across views would also enhance custom reporting, filtering, and segmentation. I understand that fields like “Contact > Deal” are currently limited to displaying associations, not shared, editable values. But introducing cross-object editable properties—at least optionally—would be a game changer for scaling and aligning CRM data. If there’s any workaround or beta functionality in the works, I’d love to know. Otherwise, I hope this makes it onto the product team’s radar. Thanks for all the great work, Michael ... Mostrar más

Please make playbooks usable in the sales workspace. ... Mostrar más