Great minds think alike

Would love to have the ability to update Activity properties, such as Meeting outcome, Meeting type etc..  ...read more

In Hubspot payment links, if a client purchases subscriptions that have different term lengths on them, they get charged separately for each subscription with a different term length (even though they paid through 1 payment link). This is not only annoying for our clients who get hit with 2 different charges every month, but it is also very frustrating for our billing/finance team, when it comes to payout reconciliation. Implementing a feature to consolidate payments on payment links that have multiple subscriptions with different term lengths not only improves the checkout experience for our clients, but also makes reporting much easier for our accounting team. This solution is useful to any Hubspot user who offers their clients subscriptions with different term lengths.  ...read more

Hereby suggest/ propose a feature that enables users to set access levels for workflows on both an individual and team basis.   With this functionality, users would have the ability to create, edit, and delete workflows exclusively for themselves or their team, ensuring focused productivity and accountability.   Crucially, teams would be isolated from one another, with no visibility into workflows created by other teams, fostering a secure and confidential environment for collaboration.  ...read more

For one-to-one emails, HubSpot enables this option by default for any user that connects their personal email address:     For admins, there currently aren't any options to disable this for all users or for select users (that I'm aware of). Each user must disable this checkbox individually.   For some HubSpot customers, certain types of one-to-one emails do not require an unsubscribe link. Typically, ticket and customer service communication falls in this category of communication. For a customer reaching out to customer support, it's strange to receive a reply that suggests unsubscribing.   This becomes a bigger problem the larger the support team in a company. For each new support team member, an admin has to keep in mind that during their onboarding, they should disable this option.   Please either create an option under Settings > Privacy & consent or include an options within presets so that admins can disable and enable this settings in bulk for users. ...read more

This request refers to the double opt-in features in HubSpot: https://knowledge.hubspot.com/marketing-email/set-up-double-opt-in-for-emails#send-opt-in-email-to-individual-contact   When HubSpot users want to bulk confirm the email addresses, the only way is currently via bulk edit:   Once you have the double opt-in feature enabled, you can update the double opt-in status for your contacts in bulk from your contacts home.   This means that every time there are new contacts to confirm, a user has to manually select and update contacts.   Please create a workflow action to update the 'Marketing email confirmation status' to 'Customer marked confirmed'.   Reasons why this is needed Some contacts should be automatically marked confirmed. For example, in many SaaS companies, software customers are considered confirmed because they already signed up for the software. In other companies, customers are generally considered confirmed across the board and should not have to go through a double opt-in process again. While there are workflow workarounds, using additional custom properties, it should be possible to update the confirmation status directly. If it's possible to update contacts in bulk (see article linked above), Professional and Enterprise customers should not be forced to do this manually. The point of such a subscription is that things do not have to be done manually. Thanks in advance for considering / evaluating. ...read more

At the moment, form permissions aren't as nuanced as email permissions. Users with edit permissions for form can edit live forms while permissions for marketing emails, for example, differentiate between suggesting changes (edit) and publishing changes (publish).     It would be great to have the same permissions / distinction for forms - and ideally also form approvals, similar to marketing email or landing page approvals.   Context Forms are an entry point for new contacts and it's important that contact information is captured in a standardized way across large organizations. This can only be ensured with standardized fields, standardized hidden fields and form settings (e.g. "Always create contact for new email address" or the marketing contact settings). Especially in large companies with many regional teams and varying degrees of confidence and competence, it's challenging for HubSpot admins to provide quality assurance for forms. If they take away form edit permissions, they become a bottleneck. If they grant form edit permissions, they constantly have to monitor newly created forms which might be created not following standard guidelines.   What happens if we don't get this feature? HubSpot admins will always be a bottleneck. General adoption of HubSpot in the company is slowed down as HubSpot admins have to work around the risks or downsides of not having these permissions.   Thanks in advance for considering! ...read more

It is very much needed to have the possibility to edit the ticket owner in the Helpdesk in bulk.   For example if an employee leaves the company and open tickets should be handed over the another colleague. Or if open unassigned tickets need to be divided between colleagues. Now we have too many clicks to change the owner in bulk. ...read more

Currently (April 2024), it is possible to add code snippets only to selected KB articles. It is not possible to add the same code to all articles at the same time. Code added to "all pages"  won't be applied to the knowledge base pages. ...read more

Right now you can only use lifecycle stage or form fill. We're running into a scenario where we want to suppress leads that reach certain lifecycle stages but end up disqualified/closed for whatever reason. I don't want to create a "Closed" lifecycle stage, so being able to use a suppression list or add something like lead status to the event criteria would be useful. ...read more