Great minds think alike

I need to disability comments in notes in ticket for specific account.  ...read more

I am a Customer Success Manager for a company that has multiple different selling channels. They partner with some companies who will sell their product (third-party type selling). Once the product is sold through the third-party, the payment is made to the partner (and they charge the partner directly, not the "child company" that is sold to), but they still have to service to the "child company". Due to this, we wanted to pass back these "child companies" from Quickbooks to a custom object in HubSpot, but this is not currently possible.  ...read more

The title kinda says it all.   We can customise secondary display properties for custom objects - great! But we are currently limited to single-line text or number property types, considering there are currently over 15 different property field types, that is rather limiting.   Pretty much all portals I am active in, which use custom objects, the custom object follows a nice pipeline structure - projects, contracts, leads (yes we build our own) - so naturally one would like to see the stage the object is on, or display a value from "contract type" dropdown field, and so on so forth.   So, just wondering why the limitation and can anything be done about it.   Ohh, and what happened to the BETA were we could customise these fields for HubSpot's standard objects? 🤔   ...read more

We need to be able to create smart properties for custom objects as soon as possible! I have clients who could 10x their work in HubSpot with smart properties but most of their data model is composed of custom objects. Would LOVE this functionality! ...read more

Having the ability to rename default CRM cards or clone and rename non-Object CRM cards would be useful since we often use a card for something but our terminology for what that thing is differs from that of the card.    For example,    We plan on using Playbooks only for pre-qualification scripts that we call Battlecards.  Having the ability to rename non-object CRM cards would mean that  Instead of having each Playbook be titled "Battlecard - [Name]", we can instead name the CRM card itself named "Battlecards" and have each Playbook just be "[Name]".    Since we are now able to rename default Objects, it seems a logical extension of renaming defaults to be able to rename non-Object CRM cards.   ...read more

Example: When creating a NEW object record from the "associations" tab of a company on the mobile app, you have to select the company again to create the association. HubSpot does not currently prefill that association based on the company record you're creating the new associated record "from", like it does on desktop. This frustrates mobile sales team and means we're missing many associations from mobile-generated records. ...read more

Add other sections to the pipeline card for the services pipeline. Currently, in the 'Add section' list there is only Properties for the services.    In the tickets or deals pipelines, there are other section available : Activites Associations Priority   Add this type of sections in the services pipeline will help to ensure a better follow up of our customers' journeys and a better management of the Customer Success team. ...read more

Current Limitation When a HubSpot form includes properties from multiple objects — for example, Contact, Ticket, and a Custom Object— the form can only: Create or update the contact, and Optionally create one additional object (e.g., a ticket). The result: if both a ticket and a custom object are created through a form, they are not automatically associated with each other. Both end up associated only to the contact.   Why This Is a Problem Many service and operations use cases rely on linking multiple records together from one submission. Example: A customer submits a “Repair Request” form. The submission creates a Ticket (the request) and an Item (the product being repaired). The team needs those two records linked to track service status by product, without manual association or complex workarounds. Currently, the only workaround is to use workflows that recreate the custom object and associate it afterward, which requires duplicating all related properties as temporary contact fields. This increases maintenance overhead, risk of errors, and makes large-scale setups unwieldy.   Suggested Enhancement Enable form-based multi-object association, where: A form can associate two or more objects upon submission (Ticket ↔ Custom Object ↔ Contact). Or, allow a form to pass a unique identifier (e.g., Serial Number or Custom Object ID) to associate an existing record instead of creating a new one. Additional option: expose association logic as an advanced form action, similar to the “create record” option available today. Business Impact This improvement would streamline multi-object processes like: Product registrations Warranty claims Equipment repairs Service requests tied to assets or accounts It would significantly reduce reliance on redundant properties and workflows, improving data integrity and user experience for both teams and customers. ...read more

I created a custom object in HubSpot called Visits. When creating a Visit, my agents can associate it with an existing Contact using the association field, but there’s no option to create a new Contact directly from that view. It would be incredibly helpful if the association field for custom objects worked the same way as it does for core objects like Deals or Tickets, where you can either select an existing Contact or create a new one right from the panel. This would allow us to create both a Contact and a Visit in one step instead of having to create the Contact first, then go back and associate it manually. ...read more