Great minds think alike

Hi,    It would be beneficial for users to access the personalised webinar links from Go to Webinar.  This would mean when a contact submits a HubSpot form, they can retrieve the personalised meeting link for the thank you page from Go To Webinar.    https://knowledge.hubspot.com/integrations/use-the-gotowebinar-integration-with-hubspot?_ga=2.156655483.1992317474.1530048615-1008103761.1519675135#segment-and-follow-up-with-registrants-and-attendees:~:text=The%20integration%20does%20not%20have%20an%20automated%20mechanism%20for%20inserting%20personalized%20links%20from%20GoToWebinar%20within%20HubSpot%20emails.  Thanks ...read more

Our business model is a "Seller-Agent" model - a bit like the business model of a real estate agent that is selling different houses. Think of the individual house as the "pipeline" and the interested house buyers as "deals".   To sell House A, we set up Pipeline A where we track all potential buyers as deals. Naturally, we want to provide the seller of House A with frequent updates about how the sales process of his/her house is going.    For House B, we need a Pipeline B, with exactly the same stages, but with different deals (i.e. only buyers interested in House B). And so on...   Current Solution (how we use Hubspot today) We have 1 pipeline per house we sell and 1 overarching "housing pipeline" where we track the stage of the different housing sales process. (Happy to demo you this example in our hubspot.)   This works great with the caviat that after 14 houses sold, we will run out of pipelines (and will have to come up with a new solution). Given the fact that our model entails that eventually House A is sold (and thus Pipeline A isn't used anymore), it would be great to be able to archive Pipeline A (without loosing the history). When we sell House A, we no longer need Pipeline A, but want to keep the history for future reference (e.g. the use case being a bit like "remember the house C we sold in 2022 - let see who was interested in the house back then but didn't get to buy it and contact them again about house X".   Problem: 1. Today, we cannot "archive" a Pipeline, only "delete" it. This way, after 14 Houses sold (assuming we use one Pipepline as a "Master Pipeline" where each deal is one house (A, B, C, D,...)), we either need to start deleting Pipelines (in which case we loose the history - not an option), export the data before deleting (kind of missing the point of having a CRM), or upgrade to Enterprise (but besides being more expensive and cluttering the pipeline list we'd have the same problem again after 100 pipelines.)   2. Today, when we want to create a new pipeline for a new house, we need to configure the pipeline from scratch (e.g. create the pipeline stages, deal tags, etc.)   Expected Behaviour 1. If it were possible to archive a Pipeline with all deals in it, it would be possible to keep the "pipeline" history while staying below 15 open pipelines.   2. Setting up a new Pipeline B (for House B) with the same pipeline settings like Pipeline A is much easier if I can just "clone" Pipeline A with all the same stages and properties (but without House A deals, obviously).   Potential Use Cases (i.e. why is this actually relevant for Hubspot) - Real Estate Agents - Insurance Agents/Brokers - Fundraising (Startups/Investors) - Affiliate Marketers - Music/Sports Agents - Headhunters/Recruitment Agencies - etc. ...read more

Currently, dealing with (hidden) fields in existing forms requires manually editing each form individually. This process becomes time-consuming and tedious, especially for organizations managing numerous forms with multiple (hidden) fields that change over time.   I'm especially thinking about hidden fields for language or utm-parameters:   Hidden fields typically used in multiple HubSpot forms   We recently decided to add another hidden field, so we had no other choice but open each form individually to do so.   It would be nice to have a feature that allows users to add (hidden) fields to multiple forms simultaneously. This functionality would significantly streamline form management, particularly for hidden fields whose placement within the form is not critical. Plus, it would reduce the potential for oversight when updating form structures. ...read more

Hi there, it would be really helpful to be able to view custom properties in the line item using the Hubspot Mobile App. ...read more

Hi team! Submitting on a user's behalf.  They are wondering why from the prospecting tool they cannot send WhatsApp messages and if it would be in the roadmap soon  Thanks!  ...read more

Hi Team! posting in a customer's name, they used to have the option only to clone the marketplace module and add it to their themes. Currently, there is no option to clone the module and add it to the team so they have to copy the entire code and recreate it in a new module. This is taking too much time and sometimes is bringing "alerts" that show the cloned module needs review but there is no noted error.  Would it be possible for them to clone the information directly to the new theme? If not, is there a reason why it wouldn't be possible? Thanks!  ...read more

The order that snippets are presente to people when they go to click add. I want a specific one to be at top for quotes and it is not.  ...read more

It would be great if the first option was the US for number formating ...read more

Due to the columns you set when you go into "edit line items" in a deal UI being a global setting, this has caused us to have to purchase two separate Hubspot instances, doubling our cost.  We have 2 pipelines which serve 2 very different product lines and they need to see 2 different column set ups in the "add line item UI". It is not practical to have all columns showing for both busniess units as the sales team will have to scroll past the columns not relavant to them and it will create poor compliance and data gaps. It is so important that you are able to set a view with specific columns on this by Pipeline or by Team, or we will have to move to another platform once we are "unlocked" from our current contract as this is not fit for purpose and is too costly to run 2 separate instances for the 2 BUs.     ...read more