Great minds think alike

It would be great to be able to integrate apps with more than one business units. Currently it is just Zoom. ...read more

Sequences are surprisingly limited in the control they allow over delays.    For example, there is currently no way to add a delay at the beginning of a sequence. We want sales people to be able to send a quote, then enrol the person in the sequence immediately, wait X time and if there has been no response to the quote, send the first email in the sequence that says "following up on the quote":.    The problem is that the way sequences are now, the email that's the first step can only send immediately.    I know you can customise this when enrolling people manually, but we want to use a Workflow to enrol people, and there is no way to set a delay in the sequence when using a workflow. Yes we could add a delay in the workflow, but this will then not remove anyone who does reply to the quote in the first place (hence not needing the sequence to send).    The second problem is that the minimum delay between sequences is 1 day. There is no way to trigger something immedialy, or 1 hour/minute later. Only one day. This makes no sense when you're trying to do something like "Task to call contact - completed --> send email immediately about the phone call".    Please allow more control over sequences in the same way most other tools allow, and in the same way you allow more control over regular workflows.  ...read more

When you create a Deal from inside a Contact or Company you can choose which properties to include on that form. Line Items is also there which is great, but you can not choose which fields to include on the quick create form. It is very frustrating for the user to have to choose the line item and click save, then have to go back into it on the Deal record and find the Line Item to add QTY, Price etc. Can we please add this functionality?? ...read more

Hey HubSpot Community,   We are considering buildling out the Customer Portal in the Service Hub, but are concerned the portal does not have MFA. Any thoughts on if and when Hubspot will be adding MFA to the customer portal?   Happy Thanksgiving! ...read more

Hello, I would like to suggest the possibilty in Hubspot that custom survey can be also linked to a ticket (or more objects, not only a contact as it is right now) so that we can then produce tickets related reports with feedacks : Show only feedbacks with the Source Ticket = Phone, or with a specific Ticket Category etc...   At the moment :  - Only feedbacks with CES survey are linked with ticket but this survey allow to filter only on the pipeline property to identify the recipients of a survey, which is too light - Custom survey allow to choose from any property of a ticket related to a contact ... but the feedbacks will be linked only to the contact ...read more

Problem: At the moment, Insights does not work for every field properly. (More info here: https://community.hubspot.com/t5/CRM/HubSpot-Insights-Database-enriches-wrong-address-information/m-p/419158#M125703)   You already implemented an option to disable it completely. (https://community.hubspot.com/t5/HubSpot-Ideas/Option-to-turn-off-HubSpot-Insights-on-company-records/idi-p/178713/page/2#comments)   This is not ideal, as some information is correct and we want to benefit from it.   Solution: Provide the option to enable and disable Insight on a field basis instead of as a whole.       ...read more

Apparently most Hubspot users operating in Europe send out Meeting Links to exising contacts instead of embedding them on their websites. When collecting personal data from prospects all of us need to make sure we have the explicit consent to process that data. The Hubspot Forms in the Marketing Tools in fact pay respect to that by enabling Hubspot users to add/edit the respective field to the form: after enabling GDPR settings generally or for a specific form you can edit the form and under other form fields add or edit the GDPR field; the drop down let's you choose between legitimate interest, - which you should choose only if you know what you are doing - a checkbox for consent for communication and a simple text for data processing (which is standard for no reason if you ask me), or checkboxes for both consent for communication and consent for data processing (the latter is then automatically a required field as it should be). Only the last option is the safe option here; the "standard option" should only be used if you already have this contact in your crm and have the consent from another source; it is practical when you additionally want your contact to join a marketing list for example.   Now to the actual issue I and basically all Hubspot users operation in the EU have: when we send out a Meetink Link to a contact we obviously do have the consent from another source to process their data or we would be in dangerous violation of the GDPR. BUT when we want to embed the meeting link on a website to turn prospects into leads I need to have that additional consent for data processing checkbox. Sadly when we edit the form that is integrated into the Meeting Link there is no way to add that. Although it would have been logical to add it here when it was added to the GDPR form field... this was pretty new in 2020 IIRC... so apparantly nobody noticed this discrepancy in the last 3 years. Except I pointed it out 3 years ago while working for a different company. So how about someone at Hubspot implements the same option Forms have to the Meeting Link forms? That would be nice... and GDPR compliant. ...read more

HubDB currently lets you backtrack to the previous version, but unlike pages, there's not a full version history. This is a major problem for use in contexts where recordkeeping is essential, like regulated industries. I see it as a major flaw in HubDB. Clearly, HubSpot has the records in the background; we just need a UI for managing them. ...read more

Some people in our company create lists of contacts and then enroll them in workflows.    To allow that, we have to give them access to all workflows so they can edit them. This is a high-security risk of them being able to actually change workflows.   We need a more precise distinction here so that we can grant access only to those who should make changes to the current workflow. ...read more