Great minds think alike

The pop up screen for merged records only allows users to "merge" or "cancel" so if a user wants to reject the merge, they have to click out and reject on the previous screen. It would be wonderful to be able to reject from the pop-up screen.  ...read more

Hello everyone, I have the problem that I cannot restrict folders for the e-mail templates for individual teams. I can only restrict the individual emails. This means that the teams can see all folders, but not all emails. Maybe some of you have the same problem. It would be good if you could share folders with certain e-mail templates with certain teams and not with others. Best regards Julian Niebuhr ______ Hallo zusammen, ich habe das Problem, dass ich Ordner für die E-Mail Vorlagen nicht für einzelne Teams beschränken kann. Nur die einzelnen E-Mails kann ich beschränken. Das bedeutet, die Teams sehen zwar alle Ordner, aber nicht alle E-Mails. Vielleicht, haben ja manche von euch auch das Problem. Es wäre gut wenn man Ordner mit bestimmten E-Mail Vorlagen an bestimmte Teams freigeben kann und manche eben nicht. Viele Grüße Julian Niebuhr ...read more

Currently, there isn't a way for us to see the user status "deactivated" or "invite pending" etc when we export the user list from HubSpot because this column is not added to the report.    Since the deactivated user list will get longer over time, it becomes very cumbersome in trying to manage data of users who are no longer with the company. Hence please consider including the "user status" column in the Export User Report. ...read more

This feature request is something that many have asked for in the past. When you either have the manual tracking code embedded on the site or utilizing a CMS module that integrates HubSpot into your site (like WordPress), it tracks all forms.  You can get around this to a point by utilizing modern form modules (WP Forms for example) that have native integrations with HubSpot that basically causes the form to be seen as a native form versus a non-HubSpot form.  If you have login forms, or other sensitive data type forms then sometimes these forms are included. I realize that "sensitive" data isn't tracked per se...but then you still get a ton of entries for logins, non-marketing forms, etc. There have been plenty of work arounds over the years, but it's definitely time to get this resolved fully for the HubSpot customers/community.  I envision that to make this easy, in the HubSpot Admin you could toggle individual "tracked" forms that appear and block them from sending any notifications on a form by form level, and/or just stop tracking them completely. Remember - currently the non-hubspot form notifications appears to be a global setting, not on a form by form level. Thanks for the consideration in this MUCH needed / simple feature. ...read more

This request is referring to the email health tool in HubSpot: https://knowledge.hubspot.com/marketing-email/monitor-your-email-sending-reputation-with-the-email-health-tool   At the moment, this tool is a great overview for marketing emails in general. However, there are improvements that would make it easier to draw conclusions and take action - most notably the ability to see health broken down separately for marketing emails, one-to-one emails sent through HubSpot and transactional emails. Thanks in advance for considering this request. ...read more

I was very excited to see the new Help Desk feature then I got into using it. The very first thing I tried to led to, what is in my opinion, a major issue related to the default views and users with paid service seats. The current default views are setup that anyone with a paid service seat has the ability to view "All Open". This view is for ALL open tickets in Service Hub. The permissions that manage the views and access in pipelines/teams/user permissions do not extend to the Help Desk feature.    We have multiple teams, parent and children, each with indivdiual user permissions that limit their access to only tickets related to their teams. While this feature would be great for letting them see all the tickets related to their teams in one view plus adding workflow to channel tickets to the best agent, we do not want them to see all tickets. This negates our ability to utilize the feature at all.  ...read more

We're locking down our internal communications and it would be great if there was a way to lock down the specific "from address" users can send from.   So being able to designate which "from" addresses users are able to send from. ...read more

Description: Implement a feature allowing for the customization of meta and title tags on author pages to accommodate varying lengths and strategic content, instead of being restricted to a fixed format.   Possible Actions: Enable variable length settings for meta descriptions to ensure they can be concise when necessary or detailed for complexity, adjusting dynamically to the content's needs. Allow title tags to include essential keywords or phrases that reflect the current focus areas or expertise of the authors, regardless of their length. Why: The current limitation is that meta descriptions and title tags on author pages are static and confined to a one-size-fits-all model, which isn't always effective. This restricts our ability to:   Optimize for Search Engines: A fixed-length meta description may not always use the optimal number of characters necessary to rank well in search engines or to entice clicks from potential readers. Reduce Inefficiency: Without the ability to dynamically customize meta and title tags, much manual intervention is required to keep these elements relevant, leading to inefficiencies and missed opportunities.   Customizing meta and title tags dynamically on author pages can help overcome the limitations of traditional SEO and make it more flexible and targeted. This approach will ensure that the metadata is concise and effective, which will improve the visibility and appeal of author pages in search engine results. ...read more

Currently, transactional emails are categorized as Marketing emails.  We use transactional emails to send receipts and platform updates to our app users. This can be a large volume of emails, and, based on subject alone, a contact knows if they need to review the email or not, resulting in a significant amount of unopened emails. Our users want to receive these notifications, despite only needing them once in a while. Because of the low engagement with Transactional Emails, users are often categorized as Unengaged, preventing real Marketing Emails from being sent.  It would be better to treat Transactional Emails as a separate category, maybe 'Transactional Emails' to make the distinction. Or allow us to set the email type on the actual email itself. ...read more