Las grandes mentes piensan igual

Hi there!   I would like to have the ability to create multi-language property names for internal use.   My company database is entirely in English and my Dev, Product, Data and other more technical users prefer to use HubSpot in English as well. However, Sales, Customer Success, Collection, and Customer Experience teams prefer to use HubSpot in Portuguese (our country's main language).   HubSpot default properties usually are translated from English to Portuguese, but we use a lot of custom properties because of our business needs and in these properties, we can't auto-translate based on our employee's HubSpot language. This generates a little friction because technical users want our CRM property naming like our database (English) and operational users want our CRM property naming in our country's language.   If a could manually insert the default property name (English) and the translated one (Portuguese) this problem would be solved.   Best, Felix ... Mostrar más

I would like to be able to reorder the fields and associations displayed when previewing a record. Ideally, we could edit which fields we want showing but even just being able to reorder the categories would be great. For example, we always want to check what deals are associated with a contact record (and vice-versa) but the associated deals section is buried at the bottom of the preview tab. ... Mostrar más

We would like to be able to change the colour and look of the meeting booking widget. We have an external webpage and would like to change the design of the meeting booking widget to match the site/company brand guide. The only thing you can change now is the Primary colour of the whole HubSpot account to change the background of the meeting booking calendar. This is very limited and not ideal. With the HubSpot forms it is possible to embed it in raw html without the iframe. It would be great if we could do the same for the meeting booking widget to add our own css. ... Mostrar más

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.    ... Mostrar más

Currently the setting for users to edit contacts is an all or nothing deal. If you want your users to be able to edit a contact's phone number they also get permission to delete it.    Would be awesome if you could remove a user's ability to delete a contact but still allow them to edit basic info like phone number, address, etc.  ... Mostrar más

I want my reps to be able to edit records they are assigned to, but not have the ability to create a new record (deal, company or contact).    With anyone being able to create a record, we deal with duplicates, false information, and skewed data.   When we control the record creation, we can be sure our data is clean and accurate.   As businesses grow and have more and more sales, service or marketing reps, it seems unlikely every single user would be responsible for creating records, or should even be able to create records.   Surprised there is no setting for this in roles and permissions, but would love to see it added in the near future. ... Mostrar más

I noticed HubSpot recently introduced Teams. It would be really nice if you could create different default property views based on team membership.    For example when Team A visits a contact profile, they might only need to see HubSpot Owner and Lead Status, where Team B might need to see a totally different set of properties.    It's a pain to tell each person to individually customize their views.  ... Mostrar más

When negotiating a deal, dropping a custom discount on-the-fly can often be what ultimately tips a lead to a customer. In turn, that discount changes the value of a deal...or at least, it should!   The trouble is, right now it doesn't.   Custom discounts aren't automatically reflected in the deal value and it's not an option. So in order to keep deals up to date, every time a new discounted quote is produced, a rep has to remember to head back to the deal and update the value manually.   That might be ok once. But doing that multiple times, on multiple deals is setting reps up to fail. What's more, it seems kinda crazy, particularly when product level (i.e. a discounted version of the product) discounts are reflected in the deal value.    So it's not that the value doesn't update. It's that discounts are disregarded despite unqeustionably impacting the value of a deal. How is this intended behaviour?   Sure, we could go in and build out 5%, 10%, 15%, 20% discounted versions of each of our products, but where do we stop? It seems like it would be incredibly confusing and result in an unnecessarily bloated product library, while making the in-quote discounting essentially arbitrary.   The inconsistency adds confusion for reps, extra steps toward managing deals in the pipeline, and will likely result in inaccuracies when it comes to reporting—meaning extra time double checking the values on all deals.   It seems like it would be easily rectified. I suggest either making it standard behaviour for a deal value to sync with the most recent/accepted quote including discounts, or to at least have some option for that behaviour to exist. ... Mostrar más

Like, contacts, deals and companies, it would be great if you could add custom user profile properties. There are times when you might want to include an owner token within an email, like a phone number, title or some other property that's outside the signature. Even though there is a phone number field on the user profile, you can't use it as a token within an email. ... Mostrar más