Great minds think alike

The new Beta form doesn't allow the use of properties from custom objects, it would be wonderful to have that ability on the Legacy Form.  The lack of this ability causes unneeded properties to be created so we can then workflow the property to the Custom Object/Create the Record in the Custom Object. ...read more

We got some feedback from customers asking for more customization options for the Customer Portal to better align with different business environments and countries.   For instance, our Japanese customers are not used to being casually referred to by their first names due to cultural norms. It would be great if there were options to display contact and user names by their last names on the portal. Also, not being able to add honorifics to names might feel a bit off.   I understand that adapting to cultural differences can be challenging on the development side, but I hope this feedback is helpful! ...read more

Hello,   My team and I have been working on implementing some regularly scheduled emails for our clients using HubSpot's Transactional Email API + the beta custom coded template/module features.    These emails are really more like marketing emails, but to leverage hubspot's single send API features we've been implementing them as transactional emails (it best suits our use-case for a range of reasons; for example, because there's a lot of bespoke data that needs to be pulled into the emails per-client in our backend, and which we don't want to store on HubSpot). Overall our desired implementation has gone well and the emails are almost ready to ship.   We've included unsubscribe links in the email footer which leverage our own unsubscribe solution, since these are going to act more like marketing emails and need to comply with relevant regulations. The unsubscribe url – which we're sending as a customProperty with the api request, and then implementing in the template – points to an endpoint of ours which implements in-house unsubscribe logic. This is important to us because we want our clients to be able to manage their subscription status both in-platform (ours) and through clicking the unsubscribe link.    The above setup for a footer unsubscribe link is working well. But to get to the point here, as a final step we want to implement those same unsubscribe links with List-Unsubscribe and List-Unsubscribe-Post headers for these emails, to comply with recently announced requirements from Google and Yahoo for marketing emails. I recently made a post on Hubspot Community inquiring whether it is possible to somehow specify values for these headers somewhere in the Transactional Email/Single-Send API flow, and per your Community Manager (and my scouring of HubSpot documentation) it looks like this is not currently supported.   This seems like a relatively simple ask and one that we'd like to formally request. From skimming around the web it looks like many email services are adding manual support here, including for teams like us with their own unsubscribe solutions: here's an example from Postmark showing what looks like a relatively straightforward manual implementation (the two headers and their values getting sent inside a "Headers" list with the API request). Is this something Hubspot can implement for its Transactional Email/Single Send API?   TL;DR: Enable specification of values for List-Unsubscribe and List-Unsubscribe-Post headers within API requests to HubSpot's Transactional Email / Single-Send API (example implementation from PostMark here), in support of compliance with Google/Yahoo requirements, for teams that need to implement an in-house unsubscribe solution with that API. ...read more

It would be a game changer to be able to select custom user properties for the meetings scheduler.    Example scenario:  In an account with multiple business units, that have overlapping contact records (one person might enquire with multiple business units/brands) we have a separate custom contact owner property per business unit (separate sales teams in each business unit). Issue is that the meetings tool only considers HS default contact owner properties. The option to select from a custom user property would come in extremely handy.  This should be applied not only to 1-1 meeting links but also round robins and groups. To fully function with round robins - it should be able to apply teams to custom user properties as well.  ...read more

The introduction of the Object Library opens up a huge opportunity to become more plug-and-play for non-SaaS industries like Manufacturing. One problem I hope to alleviate with this idea thread is the fact that so many of us serving manufacturing are building and solutioning in silos right now. Without a community-led effort to support a Manufacturing Data Template in HubSpot, it will be very difficult for HubSpot to provide a template free of the need for custom objects. In my opinion, no need for custom objects is one of the biggest benefits of the new Object Library. I think we can get there. Here's how. Here are the native CRM objects that can be leveraged by most all manufacturing companies: Contact Company Product Marketing Events Lead Deal Line Item Quote Cart Payment Link Order Invoice Payment Subscription Ticket Appointment Course Service While Appointments, Courses, Services were not meant for manufacturing, it is not hard to adapt them to use cases like Field Services, Product and Application training, and Repairs and Preventative Maintenance contracts. But where does leave us for use cases like inventory, logistics, and quality management. Without templated objects like Assets, Installs, Shipments, Warranties, etc. we will still need access to custom objects to complete the customer-centric manufacturing data model. Now, I am not suggesting that we are trying to replace inventory management systems, accounting systems, and ERPs. They all have their place and have functionality that, IMO, we should not try to replicate in HubSpot. What we do need is a place in HubSpot for all of the data our customer-facing teams need to serve great customer experiences. Instead of creating object "creep" and a lack of standardization for the manufacturing industry, I think we can solve for all of these different post-sales use cases with one object.   I call it the "Deliverable".   Just like the Product object is designed in a general way to serve any product/service/experience a HubSpot customer might provide, the Deliverable object can be thought of in the same way. I think of it like this... The Product Library is the strategic, pre-planned version of what you want to sell.   Line items are the ultra-customizable version that help close the sale based on specific customer need. Not to be changed post-sale.   Deliverables are what was promised to the customer at the close AND any other deliverables needed to support that promise. (Ex. Warranty) Put simply: Product <> Line Item > Deliverable I have been working with Deliverables as a custom object and the magic is in leveraging Pipeline functionality. So, instead of easily coming up with 5-10 more CRM objects, I believe we can serve known use cases with Pipelines instead. This also allows for customized configuration for each business via new pipelines instead of new objects.   The "stage-and-gate" nature of pipelines not only unlock the rest of the HubSpot Customer Platform, they also create the perfect place for data coming from other systems that manage inventory, production, purchasing, and accouting processes. Think of Product, Item, Expense, and Order pipelines that are found in other systems. See the NetSuite Integration as an example of what I mean Let this post not be seen as the final solution, but simply a means to support the HubSpot team trying to give us a sustainable one. I'll be sharing more links and diagrams in support of this discussion and I hope the community will feel safe and motivated to do the same. Let's Build! ...read more

Currently, when creating invoices from the deal card, all contacts associated with the deal are selected by default to be associated with the invoice. This creates an inefficiency as users often need to manually deselect contacts and associate the invoice only with the designated billing contact.   The idea is to have a feature where users can set a default contact association based on the "Billing Contact" association label. This would significantly reduce the number of manual clicks and time required by allowing users to filter by association label and create invoices directly linked to the appropriate billing contact. This enhancement will streamline the workflow, improve user efficiency, and reduce the potential for errors in contact association during invoice creation.   This feature would be highly beneficial for users who regularly manage large volumes of invoices and need to ensure accurate and efficient billing processes.   ...read more

Problem: Currently, when creating surveys in HubSpot, there are limitations that hinder our flexibility and reporting capabilities. One major issue is the inability to add more than one industry standard question to a survey. This restriction prevents us from customizing surveys to suit our specific feedback collection needs. I strongly believe that we should be able to include multiple industry-standard questions in our surveys.   Additionally, we face challenges in aggregating total NPS, CSAT, or CES scores across surveys. There's no way to access our company's total NPS score, even when attempting to create a separate report. This is because survey submissions are not treated as objects for reporting purposes, further complicating our ability to track and analyze overall customer satisfaction metrics efficiently.   Suggested Solution: I propose that HubSpot enhances its survey functionality by allowing users to freely add multiple industry-standard questions as needed. Moreover, implementing a feature to aggregate and display total NPS, CSAT, and CES scores across surveys directly within HubSpot would significantly streamline our reporting processes. This enhancement would empower us to better manage and analyze our feedback data, ultimately improving our ability to make informed decisions and drive customer-centric strategies. ...read more

Hello,   Our organization pipes HubSpot data into an external financial forecasting system, where "deal" objects share data bi-directionally with "project" objects in our external system. When a Deal in HubSpot moves from stage to stage, in the HubSpot web app, we require certain properties to be filled so our external system functions properly.  In Slack (nor the mobile app), required deal stages are not displayed nor enforced when a deal moves between Stages. Property stage requirements are critical for our implementaiton and we cannot use the Slack integration (which we dearly want to) until they exist.   With a priority for Slack, please add this to the roadmap! ...read more

Hello! I'm wondering if it's possible to require that a deal have at least one associated company after the first stage of our sales pipeline. In some cases, the company isn't known yet when the deal is at this first stage, but we want to be able to require that deals have at least one associated company before moving forward. Thanks for your attention to this, and I hope to see this developed in the (not too distant) future! ...read more