Les grands esprits se rencontrent

I noticed that the recent update changed the comment color to a pale yellow, which blends in too closely with the white background, making it difficult to read. I would appreciate the option to revert to a brighter color or to select a color that I prefer. ... Afficher plus

When creating a note and adding photos, can you add a feature so you can select multiple images at one time? It's extremely inefficient to have to select each image one at a time.  ... Afficher plus

Currently when we add any existing properties as a dashboard quick filters, the only available operators are  "contains any of, Is Known, Is Unknown and Doesnt contain any of" Its missing "has ever been equal to, has ever contained" This is crucial to track historical data! ... Afficher plus

When knowledge base articles are created, we have a process for others to check those articles for accuracy. Once they are edited, there is only a filter on the backend that shows us who last updated the article but does not account for the original author. We need a way to be able to see the original author not just who last updated the article. ... Afficher plus

Being able to surface data from one object on another object without the use of workflows has been a huge improvement.    However, now that the data can be visualized on the second object, our users often times need to be able to update it while on that object without leaving the object's workscreen.    For example, we are syncing some key Company properties to the Lead Object so that data about the company stays evergreen but our sales teams can see that data in the leads tool while working their leads. It would be great if, as they engage with the lead, they had an easy way to update these values without having to leave the sales workspace. Currently it leads to some confusion when a property can not be edited due to it being a sync property - and even having a prompt that opens the appropriate Company property or something that tells them that the field needs to be updated on the Company object would be very useful in making sure data gets updated.    Ideally we'd be able to set sync rules the same way we do with other tools (such as data sync for integrations) but even just allowing for data to be updated in either object would help immensly!  ... Afficher plus

Description: Currently, HubSpot’s dropdown fields only support a flat structure, which makes it challenging to organize and select options that naturally belong in a hierarchy (e.g., Category > Subcategory > Detail).  I’d like to suggest that HubSpot introduce tiered or hierarchical dropdown menus. For example: Selecting “A” could reveal sub-options like “AA,” which in turn could reveal further sub-options like “AAA.” This structure would make it easier for users to navigate complex option sets without cluttering the dropdown with too many items at the same level. A Level 1 └── AA Level 2 └── AAA Level 3   Use Cases: Classifying companies or deals with multi-level categories. Organizing product or service options by main category and subcategory. Streamlining forms and reducing user error by showing only relevant sub-options based on previous selections. Benefits: Enhanced user experience, especially for large datasets. Improved data quality through more intuitive field structures. More flexible customization for businesses with complex workflows. Possible Implementation Ideas: Allow admins to define parent-child relationships between dropdown options. Let users expand/collapse dropdowns to navigate tiers. Offer conditional dropdown logic within a single dropdown property, rather than relying on separate fields and conditional visibility. Thanks for considering this enhancement — it would be a game-changer for us and most likely other companies that rely on structured data collection in HubSpot! 🚀 ... Afficher plus

Current HubSpot logic dictates that when a reply is received on a ticket from a customer, the ticket will move to the status of 'New' - We would like for that workflow to be editable by HubSpot users so we can change the status we would like our tickets to go into when a response is received from a customer (For Riverside Insights, we would prefer 'Customer Responded' instead of 'New'). As a workaround to this logic, I have built a workflow that will change the status for all tickets except those in 'Closed' status to 'Customer Responded' when the 'Last message from visitor is equal to True' in the pipelines specified - We have a separate workflow that will create a new ticket when a customer replies to an email from a ticket in 'Closed' status, referencing the original ticket (This is done so as to not disrupt SLA times for tickets). Looking forward to a solution to this platform limitation. ... Afficher plus

Currently, HubSpot only allows users to view change history on a property-by-property basis within individual CRM records (contacts, companies, deals, tickets, etc.). There is no native feature to create a report or dashboard that aggregates manual change history events (such as edits or updates) across multiple records. This functionality would be extremely valuable for audit purposes, transparency, and managing compliance. Specifically, a native report or dashboard should let users: See aggregated manual changes made to records (who changed what, when, and the previous/new values). Filter by object type, property, user, team, and date range. Export or visualize changes in dashboards. Set up alerts or notifications for certain types of changes at scale. Use Case Example: “Reporting managers want to audit all manual changes made by team members in the last month to key deal properties, or to see which contacts had their email addresses changed recently, all in one view.” Benefit: This would provide much greater visibility, streamline investigations and QA, and enhance governance and compliance capabilities within HubSpot CRM. ... Afficher plus

Since there's a fairly low amount of Triggers allowed when configuring an Agent, it would be great to have the triggers be a bit more flexible and behave like keywords rather than having exact-matching on. I'm using a lot of my limit of Triggers on variations of words like "cancel" and "cancellation", when a smarter keyword setup would capture "cancellation" from "cancel". ... Afficher plus