Gute Ideen sollten geteilt werden

create ability to send a preview email of a specific email in a sequence to user's personal email.   go to sequence->email->edit/preview->three dots-> send example to personal w/ random contact info (listed above) (ie Mary Jane @BiG Old Company Inc)-> click 'send preview' -> preview gets sent to users inbox, same as it would look if sequence was live and it hit target contacts inbox.   thanks ... Mehr anzeigen

Currently, we can set contact owner tokens but this can create a mismatch between the from address and the signature if it's not the contact owner sending the email.    Creating sender-based personalisation tokens in marketing emails would help solve this,  for example a sender-based email signature personalisation token which will populate signature of the user actually sending the email. ... Mehr anzeigen

Our support team works out of Help Desk all day, and we rely heavily on SLAs for time to first response and time to next response.   What we really want is a simple way for agents to look at one list of all open tickets and immediately see which ticket needs attention first – without having to think about which SLA (first vs next response) is driving it, or manually compare timestamps.   Right now: We have separate fields for Time to first response and Time to next response. In the Help Desk table, these show as due times (e.g., 1:52 PM), not as a “time remaining” countdown. SLA labels like Due soon / Overdue are helpful, but they don’t tell you: Which ticket across all SLAs is actually due the soonest, or How much time is left in a clear way. The workarounds (two different views, or constantly toggling sort between two columns) still force agents to stop and think, check timestamps, and mentally compare which ticket is truly most urgent. What we’d love to have: A single “Next SLA due” field per ticket One property that always represents the next SLA deadline for that ticket, whether it’s first or next response. We could add this as a column in Help Desk and sort the whole view by it, so the ticket at the top is always the one closest to breaching any SLA. Countdown-style display in the list view Instead of just showing a due timestamp, allow SLA columns (including “Next SLA due”) to display something like “30 minutes remaining”. This would make it much easier for agents to scan the list and instantly understand urgency without doing mental math. Why this would help: Agents get a single, trusted queue: just work from the top down and you know you’re handling the most urgent tickets first. Less cognitive load and fewer mistakes when juggling first vs next response SLAs. Better chance of consistently meeting SLAs, especially for higher-volume teams. ... Mehr anzeigen

I have been working with hundreds of clients in HubSpot for over 10+ years and user experience has been the top reason HubSpot is amazing. Though one thing continues to make this challenging and that is the main Sidebar menu HubSpot makes every user have without any ability to customize.   So simply put we want the ability to customize what shows on the sidebar based on things like Teams and Permission Sets. For example if a Sales Rep drops in they dont need to see the Marketing tab. Or things like Data Management.   ... Mehr anzeigen

Can we please have a link on the Review Automation Issues pages to go straight back to the main Workflows Index page ... Mehr anzeigen

It would be great if you could fully clone a hubdb table without having to map each column again.  ... Mehr anzeigen

1: There are too many timezones available on the contact timezone field - it should be one option per actual timezone. Currently in Hubspot I see over 200 possibly more (takes too long to count because there are so many).    2. This would be simplified and the problem erased if you could properly order the timezone on the tasks section. Currently, the tasks, if ordered by timezone, are ordered by alphabetical name of the timezone! Which completely defeats the point of having a timezone in the first place. It should be ordered: UTC-12, UTC-11, UTC-10 and so on. Currently it is ordered: UTC -6 US Mountain, UTC -4 US Eastern, UTC -5 US Central. The most frustrating part of all of this is that, when it comes to making a selection from the drop down menu of Timezones on the contact field, it is ordered in the second, more useful way: UTC-12, UTC-11, UTC-10 and so on. Suggesting that this should be an easy fix.   Tasks ordered by Timezone field:    Timezone field dropdown menu:  ... Mehr anzeigen

As a HubSpot admin who participates in weekly product update reviews, I need a native Product Updates object that surfaces beta and release data as CRM records, so that I can track evaluation status, communicate adoption decisions with my team, and demonstrate feature adoption over time, without manual data entry or external tools.   The Problem: HubSpot releases a significant and sometimes overwhelming number of product updates weekly across multiple hubs and product areas. While the Product Updates portal is excellent for discovery, there's currently no way to: - Track which betas or releases your organization has evaluated or joined - Create a structured, searchable record of evaluation decisions and timelines - Report on adoption patterns to leadership or during renewal discussions - Automate team communication about beta participation status - Maintain institutional knowledge about why certain features were pursued or deprioritized   The Solution: A native Product Updates object (similar to existing objects like Campaigns or Marketing Events) that automatically syncs publicly available product update data from HubSpot's Product Updates portal. Key fields would include: - Title, description link, and knowledge base article link - Rollout state (LIVE, PUBLIC_BETA, PHASED_ROLLOUT, etc.) - Release date and stage transition date - Hub and feature area categorization - Impact level (MAJOR, MODERATE, NOT_SIGNIFICANT) - Type (INITIAL_RELEASE, REDESIGN, BREAKING_CHANGE, SUNSET, etc.) - Whether it includes AI features - Rollout enrollment status Teams could then layer their own tracking properties: - Evaluation stage (Reviewing, Testing, Implemented) - Participation status (Requested, Joined, Not Pursuing) - Internal owner and decision notes - Last reviewed date   Business Impact: 1. Renewal and Expansion Evidence: CSMs and account teams can demonstrate concrete adoption of new features and expansion of HubSpot usage over time, strengthening renewal conversations. 2. Product Feedback Signal: HubSpot gains structured data on which betas resonate with customers, which are ignored, and why, which informs product prioritization. 3. Expansion Opportunities: When an account shows strong evaluation activity in one hub but hasn't expanded into another, it becomes a natural conversation starter. 4. Team Alignment: Reduces friction around communicating beta participation decisions across technical, marketing, sales, and service teams. 5. Operational Efficiency: Eliminates redundant manual data entry and tracking across disconnected tools.   Why This Matters: HubSpot's own customers are your best advocates for product adoption and expansion. Making it easy for them to track, evaluate, and demonstrate adoption of new features turns the Product Updates experience into a built-in sales and retention tool, not just a discovery channel. ... Mehr anzeigen

Idea Description Currently, Sensitive Data properties can be added directly to native record creation forms (e.g., Ticket creation forms) as standalone fields, but they cannot be used as dependent or controlling fields within conditional logic. This creates an important limitation in real-world workflows. In many operational scenarios, sensitive information is only required for specific record types or ticket categories, not for every submission. For example: A sensitive field should only appear when a specific Ticket Type or Category is selected. The field should remain hidden otherwise, to avoid unnecessary exposure and to keep forms clean and efficient. At the moment: The Sensitive Data property is allowed on the form But disappears from the selector when trying to apply conditional logic This suggests that conditional logic is not yet enabled to interact with the security/encryption layer of Sensitive Data properties Business Impact Forces teams to either: Show sensitive fields at all times (poor UX and security exposure), or Use workarounds outside native forms (custom UIs, integrations, or manual processes) Reduces adoption of Sensitive Data properties in structured, compliant workflows Impacts regulated environments where data minimization and context-based collection are mandatory Proposed Enhancement Enable Sensitive Data properties to: Act as dependent fields in conditional logic Be shown or hidden based on the value of non-sensitive controlling fields While maintaining their existing encryption, access controls, and audit protections This would allow teams to: Collect sensitive data only when necessary Preserve security standards Fully leverage native HubSpot forms without custom development This enhancement would significantly improve usability for enterprise and compliance-driven customers while staying aligned with HubSpot’s security model. ... Mehr anzeigen