Great minds think alike

Currently, as I understand it, Chatspot doesn't have access to custom objects. We find Chatspot super useful and would love it if the functionality was extended to custom objects. Especially given this is where we keep some of our more complicated, but business critical information ...read more

When associating a company to a contact, or a contact to a company, a feature exists where the user can create a new record, withing the same page.      The same tool should be available on the lead creation form, as currently an association is required. However, the user must open a new tab, create the record, and then return to creating the lead to successfully do so on new leads.   This would help with consistency and ease of functionality across the tool. ...read more

Currently use a custom Object for conferences we attend.  Encountering an issue of when activities are created and associated to the "Conference" Object, the associations are not showing up on the specifc Conference.  ie. A meeting is logged, the meeting is associated to Contact(s), Company, and one of our Conference objects.  When you navigate to the Conference, select the Conference referenced, the contacts nor the conference are showing up.     This is roadblock if using custom objects if activity associations are not going to link and show up on the custom object.  Please fix!  ...read more

Hello and thank you. I have worked with a customer and they would like to request for you to modify in the Object view when filtering it in advance filters some of the options come up with a new option that is Is Equals to Any Of, this new feature is very different from the Contains Exactly but for her co-workers since they are not HubSpot experts they do not know the exact difference and this seems to be causing issues on their end. Since the Contains exactly option used to be first in the dropdown select, she wanted to request to make it the second options instead of the first one in the dropdown to avoid this type of confusion for people in general.  ...read more

Contact records are created via email address property, so any imports / updates relating to the email address updates the contact record.   Whereas for custom objects, you cannot assign a property as the unique identifer. Currently, you would need the record id number in the import for hubspot to match the import record to an existing record. without the record ID, you get multiple records.   Ideally, we would want a primary property for imports to match and connect to existing records in order to update. ...read more

Create a Helpdesk Object under the Data Management section so it can have more customizing options, like Deals and Tickets (as an example). Similar to what is explained here:  ...read more

The introduction of Prospecting to manage leads is a welcome addition to HubSpot.  We have adopted it and over all it works really well.   However, some of the standard functionality in how you manage other record types (companies, deals and contacts) aren't available for Lead records.  This includes: exporting leads to a spreadhseet, and the ability to make wholesale changes to that export and re-import it back into HubSpot.  The ease of use of HubSpot doesn't seem to apply to Lead records which is frustracting and hard to understand.  Can this be fixed to make data management of lead data easier and encourage the adoption of the Lead feature in HubSpot?   ...read more

Current Functionality   Currently it is possible to create new cards via the record customisation page.   For cards created that are displayed in the center tab, it is possible to apply filtering on some of the card types to only display the details you want to see.   In the below example, I have an "association table" card that allows me to display associated records, the properties I want to see, and a filter to only show certain types of records that match the filter criteria; in this case I only want to see product subscriptions that are not deactivated:     Limitation   While this is true for cards in the center tab, sidebar cards on a record currently are only able to display all associated records. It is possible to create new cards to display different properties of those records, but it will still show every associated record. When creating a new card, there is only the option to change the properties visible, and nothing else.     Suggestion   My suggestion would be to be able to create cards with similar filtering and sorting options, so as only to display associated records with certain criteria you are interested in, at a glance.   Example   On a company page you could create a sidebar card called "Ticket Openers". This card would show associated contacts of the company, but filtered on a custom property that exists on the contact level, "Number of tickets opened". You could set the filter to be "Number of tickets opened" > 0, sort by "Number of tickets opened" descending.   Now this sidebar card would show you, at a glance, the contacts associated to the company record you are viewing that have opened tickets, in order of most to least.   Benefit   Due to the sidebar cards always being present on a record (unless minimised) they have the benefit of displaying information without needing to navigate around the record. Sometimes teams will be looking for common information, and the ability to display that information on the sidebar would minimise the amount of navigation required as it will be visible at a glance.   This would also help to clean up associations somewhat. In my first example of "Active Product Subscriptions", the current functionality displays all of our custom object Product Subscriptions. Some of these may be old trials that we ran. Some may be deactivated products, or legacy products. This is all useful data, but due to the associations showing all records, it means we could have 10+ associated records showing in the sidebar, most of which are not relevant. By allowing filtering, we could change this to only display the ones that are useful at a glance. ...read more

More and more, we are encountered with the need to mandate associations when moving deals/tickets/custom objects along the pipeline. Mandated associations "post record creation", the same way we can mandate properties to be updated based on a pipeline stage.   This means, we already have the mandated associations when creating a new record and we wish that we could for example mandate the association of a ticket with a custom object and/or deal before we close the ticket.   This association cannot be mandated from the creation of the ticket record. ...read more