クリエイティブな才能を開花させよう

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!  ...その他を表示

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. ...その他を表示

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. ...その他を表示

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! 🚀 ...その他を表示

It would be very helpful to expand the "Prioritize contact owner" functionality in the Meetings tool to allow referencing custom owner properties—not just the default Contact owner field. Currently, this feature is limited to the default Contact owner, which can be restrictive for teams that manage contacts using multiple ownership properties. For example, in our case, we use a custom property called Benefits Contact Owner for scheduling "Benefits Discovery Call" meetings. Ideally, this meeting link would prioritize the Benefits Contact Owner instead of the general Contact Owner—but there's currently no straightforward way to achieve this. Adding the ability to select which owner property is prioritized for a given meeting link would provide greater flexibility for teams with specialized sales or service processes. ...その他を表示

In short: Add the ability to view and reply to chats in Slack with the Helpdesk Slack integration, to mirror how it used to be with the legacy inbox Slack integration. Maybe this could be a toggle between posting comments or chat replies to Slack.   The legacy integration between Hubspot and Slack for inboxes allowed you to handle incoming visitor chats right in Slack - this meant seeing and responding to chats right in the Slack thread created by Hubspot for a specific chat. Helpdesk, while it also has a Slack integration, only allows internal comments to be communicated back and forth between Slack and Hubspot. If you keep the legacy inbox system and opt not to use Helpdesk, you miss out on key features. This could be a toggle when a user is configuring their Slack integration - perhaps they can toggle whether or not they want comments or chat replies to post to Slack. My screenshot below confirms this - look at the description below Bring conversations to Slack and Sync Help Desk tickets to Slack - they are different.   ...その他を表示

Per this thread, I am requesting that you provide us a setting to turn off this feature. It would be ideal if we could turn this off at either at the individual user level or at the admin level. This autosave feature is extremely disruptive to our workflow. ...その他を表示

In the future, it would be incredibly helpful if HubSpot forms could allow users to create multiple contacts from a single form submission. Use Case Example: Imagine a scenario where a customer is filling out a form on behalf of someone else, or needs to provide information for multiple stakeholders, such as their manager, billing contact, company owner, or other relevant parties. Proposed Solution: Add a “+” or “Add Contact” button to the form, allowing users to dynamically add more contact fields as needed. When clicked, a pop-up or conditional section appears where the user can enter the details for the additional contact (name, email, role, etc.). All submitted contact details are processed and create separate contact records in HubSpot, linked to the original submission. Benefits: Streamlines data collection for group registrations, event sign-ups, or any scenario involving multiple stakeholders. Reduces friction for customers who need to provide information for more than one person. Improves data accuracy by capturing all necessary details in one go. Example Workflow: User fills in their own details. Clicks “Add Contact” to include their manager’s information. Optionally adds more contacts (billing, owner, etc.) as needed. Form submission creates all relevant contact records in HubSpot. ...その他を表示

As the title says "Access management per user/team on snippet folders" would be very handy. Currently this is not possible as i understand from the Hubspot knowledgebase: https://knowledge.hubspot.com/conversations/use-snippets. Please make this possible as this will provide more flexibility in managing a large set of snippets to a specific group of users. ...その他を表示