Las grandes mentes piensan igual

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.   ... Mostrar más

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. ... Mostrar más

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. ... Mostrar más

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. ... Mostrar más

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. ... Mostrar más

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”) ... Mostrar más

Use case: I need to monitor and report on meetings booked as a result of enrolling contacts into sequences. We use sequences as part of our 1:1 sales outreach program and we need to determine ROI, as well as individual sequence performance. I combine meetings booked with opportunity created and closed data for high-level metrics.   Reconciling sales results can be a manual process between HubSpot and other CRMs and I need an easy to work with and sharable table of data that includes contacts' information, not just aggregated stats. I would also like to easily use this contact data in campaigns. While I can generate graphic reports and view stats and some contact details on sequence Performance and Analyze tabs, these have critical limitations that would be solved by also being able to replicate and generate this data in text-based segments and contact views. Challenge: In sequences and contact views, I'm unable to replicate the list of contacts that have booked a meeting through a sequence link, and/or booked a meeting through another means (ex., manually in the HubSpot CRM or synced from a connected calendar) within 7 days of being enrolled in a sequence. Currently, this aggregate information in a text-based format is only available via Sequences --> Analyze tab --> Meeting Rate. Clicking on the hyperlinked percentage pops up a list named 'Scheduled meeting' that includes: Contact enrolled Company Sequence Status (enrollment status, not lead status) Latest Meeting Booked Date (if available; this is specifically related to meetings booked via the HubSpot scheduling link) There is no way to add additional properties to the pop-up 'Scheduled meeting' list, filter the data, export it, or add it to a segment or contact view. There's also no way to save the settings used to generate the 'Scheduled meetings' pop-up, so if I've selected specific sequences, enrollment dates, folder, etc. I have to re-select those settings every time I want to view the 'Scheduled meetings' data or save the URL somewhere handy.    The best attempt at replicating the results in a segment generates contacts that have been enrolled in a sequence at some point and booked a meeting at some point. These two activities could be unrelated or related to each other. I can add date filters, but there is no way to guarantee causuality or association between the sequence enrollment and the meeting booked.   The ask: In segments, I want to view contacts that have booked a meeting through sequences. I want the ability to choose whether to show the results for all sequences overall, or specific sequences.   Having this information in a segment format would allow me to add and filter by properties such as company type, industry, country, lead status, lead stage, deal details, and other data not currently available in the default 'Sheduled meetings' pop-up. This would expand my understanding of the results and impact, and greatly improve stakeholder reporting. I could also use these segments in saved contact and company views to share with my sales team for targeted follow-ups and coordination. These views would also provide the ability to add and filter by more properities if I didn't apply those at the segment level. This would enable me to create contact views that are specific to each sales person so that they have a clear view of their booked meetings and the related contact details across the sequences they've enrolled in. It would also allow me to send marketing campaigns to people who had booked a meeting through or associated with a sequence (some people book and cancel and may need marketing nurturing) by adding the segment name to the recipient list. Thank you! ... Mostrar más

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. ... Mostrar más

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. ... Mostrar más