JavaScript muss installiert und aktiviert sein, um diese Boards verwenden zu können. JavaScript ist in Ihrem Browser deaktiviert oder Ihr Browser unterstützt kein JavaScript. Einzelheiten zur Aktivierung von JavaScript finden Sie in der Hilfe zu Ihrem Browser.

Gute Ideen sollten geteilt werden

Du hast eine Idee, die deiner Meinung nach die HubSpot-Software verbessern würde? Wir freuen uns, mehr darüber zu erfahren!

87 Ideas in development 244 Ideen, die gerade in der Betaphase sind 2109 Ideen, die erfolgreich umgesetzt wurden 33 Alternative solutions

Browse all ideas Create idea

Im Forum HubSpot Ideas nach Lösungen suchen oder eine Frage stellen

Status:

We’d like a customer-facing setting that allows admins to fully disable Conversational Context analysis, rather than only managing the related notifications. The KB confirms this cannot be turned off. Right now, the available workaround is to disable the notification, but that does not solve the core issue for customers who want more control over whether this analysis happens at all. This would help with: Transparency for customers who want a clearer understanding of how conversation data is being analyzed Granularity so teams can choose whether to keep notifications, analysis, or both Customer control for portals that do not want this functionality enabled by default Suggested improvements: Add an admin-level on/off setting for Conversational Context analysis Separate the controls for analysis and notifications Provide clearer in-app explanation of what the feature does and how the data is used This kind of control would reduce friction for customers and make the feature more flexible for different use cases. The current limitation is not about cost, but about the lack of a customer-facing setting to disable it. While the notification can be turned off today, the underlying analysis setting cannot currently be disabled.

Status:

When dealing with large segments, checking the master checkbox at the top left of the table only selects the records on the current page (e.g., 25, 50, or 100 records). To select the entire segment, HubSpot displays a small, blue text link "Select all # records". Because this text is small and embedded in a light blue banner, it's very easy to miss. This UI layout frequently leads to: Accidental partial actions: Users thinking they've selected the whole segment, only to accidentally apply a bulk change, sequence enrollment, etc., to just the first 25, 50, or 100 people. UI Frustration: Users spending unnecessary time hunting for how to select their entire segment. Proposed Solutions: Turn it into a button: Instead of a hyperlinked text string, make "Select all # records" a clear, high-contrast button within that action bar. Increase visual contrast: Give the banner a more distinct background color or border when a user checks the master box, signaling that a secondary choice needs to be made. A clear warning/pop-up: If a user clicks a major action (like "Enroll in sequence") while only a page-level selection is active on a multi-page segment, show a quick prompt asking: "Do you want to apply this to the 25 selected rows, or all records?". This small UX improvement would save teams from major bulk-editing headaches and make segment management significantly more intuitive.

Status:

Hi team, Currently, sorting is inconsistent across different sections: Overdue — chronological Upcoming — chronological Timeline — reverse chronological Ideally, users need the ability to define a global date sort for all sections, or to configure the date sort for each section separately.

Status:

When HubSpot forms are embedded on external websites using the standard embed code, reCAPTCHA (v2 Enterprise, invisible mode) fails to initialise if the host platform wraps the embed inside its own cross-origin iframe. This affects platforms like Cvent, which use iframe isolation for embedded widgets. The browser console shows "Invalid domain for site key" and reCAPTCHA timeout errors. The form cannot be submitted. This is not a domain allowlisting issue. HubSpot's reCAPTCHA site key has domain verification disabled. The failure occurs because Google's reCAPTCHA cannot validate origin trust or access behavioural/cookie signals when running inside a nested, cross-origin iframe controlled by the host platform. Current workarounds: 1. Remove reCAPTCHA from the form (loses spam protection) 2. Use the HubSpot share link inside an iframe instead of the embed code (works, but requires replacing every embed across every site) Neither workaround scales well for organisations with many forms embedded across many external websites. Requested improvement: HubSpot should handle reCAPTCHA in a way that works inside third party iframe containers, or provide a configuration option that allows the standard embed code to function in these contexts without requiring customers to switch to the share link for every form. Use case: Event management organisations using Cvent (and similar platforms) to host registration and contact forms powered by HubSpot across dozens of event websites.

Status:

We would like a feature that will allow us to import Past date events in Properties recording past changes. Ex. Contacts lifecycle Change Was changed but not Companies. We would like this to reflect Past history of the Lifecycle stages from Contacts to Companies.

Status:

HubSpot has made strong progress in centralising communication, but email organisation still lags behind. Many teams continue to rely on tools like Front because HubSpot lacks the structure needed to properly manage shared inboxes and historical communication at scale. Key gaps: No native folder structure for organising important emails Limited filtering and view creation for email records Difficult to track emails by sender, tags, or CRM properties Heavy reliance on external inbox tools for proper management Proposed solution(s): Introduce Inbox folders for categorising emails (internal, partners, escalations, etc.) Expand filters to include; Sender / domain Tags Associated object properties (contacts, companies, deals, tickets) Enable shared, saveable views for team collaboration This is about unlocking the value of email data. High-quality CRM data needs to be accessible and usable across the platform, and while HubSpot is improving centralised email management, this is the next logical step. It also sets the foundation for AI to automatically categorise and prioritise conversations . If HubSpot can match what dedicated inbox tools already do well, it would reduce tool sprawl and strengthen its position as a truly unified CRM.

Status:

In Sequences and sales email templates/snippets, the Fallback value for a personalization token currently only supports static text (e.g., “there”). We often want a more intelligent fallback based on another property (e.g., “Preferred name, else First name, else there”), but that isn’t possible today. Problem: The fallback for a token like {{ contact.firstname }} can only be plain text. We can’t express logic like: If Preferred name exists → use that Else if First name exists → use that Else → use “there” This forces us to do more data‑engineering and workflows just to get reasonable fallbacks, rather than handling it at the content level. Proposed solution: Allow the fallback field for a token to reference: Another property (e.g. contact.preferred_name as fallback for contact.firstname ), or A simple priority chain (e.g. “Preferred name OR First name OR static ‘there’”). This could be surfaced either via: A UI that lets us choose a “backup property,” or A simple expression/logic builder for token fallbacks. Why it matters: Produces more natural, human‑sounding emails without heavy data prep. Reduces risk of awkward greetings and salutation issues in sales outreach. Gives more flexibility for multi‑language and multi‑region setups where naming conventions differ.

Status:

Issue: When a table with multiple data rows is rendered inside a custom card (UI extension), the header row scrolls out of view as the user moves vertically through the table. Once the headers are gone, it becomes difficult to tell which column a given cell belongs to — especially when editing values inline. Requested feature: Add the ability to freeze/pin the header row of tables rendered inside custom cards, so column headers remain visible while the user scrolls through the data rows.

Status:

1. Year-Based Discounting for Multi-Year Contracts Our standard sales motion includes multi-year agreements (typically 36 months) with different pricing or discounts applied by year (e.g., discounted Year 1, standard Years 2–3). Currently, HubSpot does not support applying discounts by year within a single subscription. Attempting to model this with multiple line items breaks ACV calculations and causes ACV to match TCV, which impacts reporting and forecasting. What we need: Ability to define pricing or discounts by year within a single multi-year subscription Maintain accurate ACV vs. TCV calculations regardless of structure ⸻ 2. Flexible Contract Terms We occasionally have non-standard contract terms (e.g., 40-month agreements), but HubSpot only supports clean 12/24/36 month structures in a way that ties correctly to reporting. What we need: Support for flexible term lengths beyond standard yearly increments Accurate prorating and reporting across custom term durations ⸻ 3. Minimum/Base Fee Logic within Tiered Pricing Our pricing model includes a minimum annual fee below a certain threshold, which cannot be natively enforced within HubSpot’s tiered pricing model. Current workaround requires separate products, which introduces complexity and inconsistency. What we need: Ability to define a base/minimum fee within tiered pricing logic Conditional pricing rules (e.g., “if below X, apply minimum fee”)

Status:

The Problem HubSpot allows admins to mark custom email properties as "required" via the email create form editor (Marketing > Email > Setup > Edit Form > Make Required). This is a great feature in concept. At GreenHouse Agency, we use it to enforce operational data hygiene across our clients' emails, things like campaign type, audience segment, or in this case a "Sent to Unengaged" classification property. However, the enforcement is inconsistent and misleading. When a user attempts to publish or send an email without filling in a required property, HubSpot surfaces the message "Sent to Unengaged is required.", but then categorizes it under Warnings, not Required Fields, and still allows the send to proceed. This means the word "required" appears in the warning text itself, but the system does not actually require it. Users can easily overlook that warning and publish or send anyway. The Ask Required custom email properties should behave like the existing hard-required fields (Recipients, Subject Line); they should block publishing and sending until resolved, not surface as ignoreable warnings. Specifically: Required properties marked in the form editor should appear under the "Required fields" section, not "Warnings," when the pre-send checklist runs. The Send / Publish button should remain disabled until all required properties have a value, consistent with how Recipients and Subject Line already behave and how custom properties on the workflow create form behave. Optionally, surface the create form to complete required properties after template selection but before redirecting to the editor. Why It Matters For teams using custom email properties for reporting, segmentation hygiene, or compliance tracking, a "soft" required field provides no real governance. The current behavior creates false confidence in the admin who configured the requirement, while giving senders an easy path to bypass it. If HubSpot exposes the concept of a required field in its UI and labels it as such in the warning copy, the system should enforce it accordingly. This is especially important for Marketing Hub customers at scale: agencies, enterprise teams, and regulated industries (like financial services) where email metadata accuracy is tied to reporting integrity or audit requirements. Workaround (and why it's insufficient) Currently, there's no reliable workaround. Admins can document the requirement in SOPs, but there's no way to programmatically enforce it at the platform level.

Vor Kurzem umgesetzt

Enable Sequences Analyze 'Meeting Rate' Data for Segments, Contact Views, and Campaigns

27 Likes

Catch-up Tab Order in Company Object

12 Likes

Add “Used in Lists / Segments” Visibility for Forms (Parity with Workflows)

30 Likes

Create a setting to turn off autosave feature

160 Likes

Set Association Labels On Records via a Workflow

1096 Likes

Vor Kurzem in der Beta-Version

Workflows based on meetings

116 Likes

Multi-Step Forms - Required Fields

177 Likes

Calendar view for Custom Objects

41 Likes

Customise Global Search Results Settings, including Properties showing in columns, order, length

153 Likes

653 Likes

Autoren, für die die meisten Kudos vergeben wurden

Benutzer

Anzahl

10

10

7

4

4

4

3

3

“ The ability to partner with our Community members for Ideas and feedback is one of my favorite parts of working in the Community. HubSpot's customers know our software better than anyone else, and having their continued input and creativity is essential. ”

Jenny Sowyrda,Community Program Manager

“ The Ideas forum is our go-to tool for gathering user feedback. It helps us with prioritization, research, and most importantly, amplifying the voice of the customer. Thank you for all your great Ideas! ”

Francis Ndicu,Product Manager

“ The Ideas Forum helps me get a finger on the pulse of customer demand. I get new Ideas on my radar, as well as find early beta users for new features. Thank you to all our HubSpot Community members for pitching in! ”

Stephen McMillian,Associate Product Manager

“ When a user shares how an idea would help their business, it’s an incredible gift and show of trust in HubSpot. Thank you to everyone for your feedback! ”

Hannah Roberts,Product Manager

“ The fuel for this sprocket-shaped rocket ship we’re all on together always has, and always will be feedback from our customers. You all helped us shape what HubSpot is today, and will help us shape where HubSpot goes tomorrow. Sincerely, thank you ”

Shay Redmond,Senior Product Manager