Great minds think alike

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

Currently, when using the Global Search Function, we cannot amend the default Global Search Results Settings to display properties in the Global Search Results View columns that are relevant to the specific business, and customise views to different teams/ team members in the business.    i.e. Global Search Results for Contacts only show default columns for Name, Email, Phone number, Primary company, and job title.  Global Search Results for Companies only show default columns for Company Name, Domain, City, Region, Phone and Company Owner.  Similarly, we are locked to default properties with Deals, and all other objects.    Goal  We are able to tailor the Global Search Results settings to meet the needs of different teams/users, much like the way we already can edit the object-specific search result views with the Contact/Company/Deal search tabs. This will enable us to:  - Choose properties to display in the Global Search Results view  - Choose order of columns that display  - Change length of column.   Different teams have different needs:    Use cases Different properties/columns to display for different teams  - Service teams may find it more useful to see a customer code property/column in the Global Search Results View; while they can use the Global Search to find the correct company, they can't see on the screen they are clicking on the correct company, because we cannot bring in the <CUSTOMER CODE> company property to the results view.  - If searching companies, would be great for sales teams to see the primary contact in a column, and click directly onto this, rather than needing to click on the company record, to then search for the primary contact  - If searching tasks, would be great to see the internal task owner in a column, so you can easily see accountability.    Ability to edit length of columns  There may be several entities e.g. deals, companies, with nearly identical names, but a small variation right at the end of the deal/company name. So we can correctly read the name, we need to be able to edit the length of 1 particular column in the display screen. This means we don't have to click into the record/hover over each record, to read it. e.g. COMPANY NAME is likely to be longer than other properties, so we want the ability to make this column longer than others.    ...read more

Right sidebar for Custom Objects has no option to add Orders and Carts. Please add this feature as it is already available for other objects. ...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

Our organizaiton has goals/success metrics for each of our client organizations. These goals change year over year and the numbers vary based on the company, engagement and population. Current state, we are having to capture these under "Deals" as this is the best route we can think of to house this information given it changes each year, want to tie to the company and be able to track/export. It'd be great if we could have goals tied as a seperate association to track.  ...read more

Idea publicada en nombre de un cliente.   Es necesario implementar la opción de búsqueda por palabra clave en el cuerpo de un correo. Por el momento los resultados se basan en términos que se encuentran en los siguientes campos de actividad: asunto del correo, asunto de la tarea, cuerpo de la tarea, cuerpo de la nota, cuerpo de la llamada y cuerpo de la reunión.    Por favor, revisen la funcionalidad para que se pueda buscar por palabras clave en el cuerpo del correo, no solo en el asunto, como hasta ahora.   Gracias,   Equipo de Soporte      ...read more

Using the Jira integration tool, there are default properties available. I would like to be able to add further properties. When creating a new Jira, it gives an option to select the Issue Type:     But that is not an available property to select for workflows.     And it would be great to be able to modify the default Jira card to include additional properties than what is displayed. We sometimes link multiple Jira IDs to a single Help Desk ticket but with different Issue Types. It would be great to see that on the card or any of the existing ones available as well.   ...read more

Hello product team,   For HubSpot admins, one of the biggest challenges is keeping a portal organized, cleaned up and prevent overall chaos. Especially in Enterprise portals with sometimes hundreds of users, it's almost impossible to get users to follow a naming convention for email names, landing page names, workflow names. Quickly this becomes a cat and mouse game where HubSpot have to constantly chase and remind users to name their assets correctly.   Why is this currently a bad user experience for users?   Naming conventions are usually documented outside of HubSpot, in a wiki, stored as a Google Doc or something similar along the same lines. Forcing them to interrupt what they're currently doing, look up a naming convention and then come back means that they're losing time. They also have to leave HubSpot momentarily. Even then, they might misunderstand the naming convention and type in an incorrect name.   Why is this currently a bad user experience for admins?   Incorrect naming means that list or workflow filters for Recent conversion might not work. It can also mean that reports become a mess, if these reports are pulling in asset names.   If admins have to look into this on a permanent basis, in portals where there are new assets every day, this takes time away from developing the HubSpot portal and generating more value for all users.   Here's what a solution could look like   To solve this, it would be great if there were tools to enforce a naming convention. Ideally, admins would specify what constitutes a correctly named asset and similar to the forms editor, arrange fields to their liking.   Here's a quick mockup of what this could look like when creating a new page.     The user could select from dropdowns which team they belong to, the language of the assets, the asset type, include a title and date. The system would then generate a title from this that cannot be further edited.   Admins should be able to specify the options for each dropdown, separators, order and field validation (e.g. max length for a title).   (In case this is eventually introduced, please consider to make this a feature that is at least included in all Professional and Enterprise subscriptions.)   I would love to see this for all assets in HubSpot: emails, workflows, lists, campaigns, imports, properties, files etc.   Thanks in advance for reviewing! ...read more

I would like to suggest an enhancement to the HubSpot CRM that would allow the association of the Leads object with custom objects. Currently, it’s not possible to directly associate a lead with a custom object. The only workaround is to associate the lead with a contact, and then associate that contact with the custom object. However, this method doesn’t fully meet the needs of our use case. This feature would greatly improve the flexibility and functionality of HubSpot, allowing us to better manage our data, workflows and reports.  ...read more