Great minds think alike

Our global HubSpot account is used by teams operating in multiple countries and languages. To ensure strong user adoption, it is essential that we are able to translate custom properties—including custom pipelines and pipeline stage properties—into a broad range of languages. This need is particularly important for our Sales Representatives and might even become a roll-out roadblock.   Currently, HubSpot supports only a limited set of languages for custom translations: Chinese, Dutch, English, French, Finnish, German, Italian, Japanese, Polish, Portuguese, Spanish, and Swedish. To fully support our multilingual operations, we also require the ability to translate custom content into Slovenian (sl) and Slovak (sk). ...read more

Hey! Context HubSpot’s Customer Agent works well in live chat, but when deployed on email channels the stakes are higher. Email replies are often more formal, more binding, and in some industries (like banking and finance) a wrong or imprecise answer can have legal consequences. Because of this, we cannot allow the Customer Agent to automatically answer every incoming email. Problem Today, when the Customer Agent is enabled for email, it can respond automatically to all messages that meet its confidence threshold. However, this creates risk in cases where: The inquiry is legally sensitive, The customer’s request requires manual investigation, The reply could be interpreted as a binding statement, Or internal policy requires a human approval step. Without guardrails, we cannot safely use the Customer Agent on email. Proposed Feature: Guardrails & Human-in-the-Loop Workflow We would like a way to control which types of emails the Customer Agent is allowed to answer automatically — and which ones should require human review and approval before sending. Key components could include: Content-based Guardrails Allow admins to create rules (keywords, categories, sender-address, intent types) that determine when: Customer Agent may auto-send a response Customer Agent may draft but must wait for approval Customer Agent should not respond at all Approval Queue / Human-in-the-Loop If an email falls into a higher-risk category, Customer Agent should generate a draft and place it in a review queue for a human to approve, edit, or reject before sending. Confidence Threshold Settings per Channel Ability to set a stricter confidence threshold for email than for chat. Impact These controls would allow regulated industries (like banks, insurance companies, healthcare, or legal services) to safely use Customer Agent in email channels without risking compliance breaches or legally binding miscommunication. This would significantly increase adoption and trust in Customer Agent across enterprise and compliance-focused teams. Regards, Marte ...read more

Hello,   We are looking to adapt our chatflow for multiple languages across the globe. We currently have 3 "Select Industry" pick lists; one for each of our two business units and one that pulls in all industries.    That being said, we have loaded translations for these options, however the chatflow tool does not support the translated values. This is very frustrating and the only option that was given was to create a seperate property for that specific language. We are looking to deploy this across at least 6 different languages, which would require us to build no less than 12 different properties to satisfy the language varients, not to mention workflows to copy these to the English values that we use internally.    It would be great if translations are able to be surfaced in chatflows. We are not interested in a workaround as it is too cumbersome for our needs and will require ongoing maintenance. Can you please build functionality to support translated properties in chatflows? ...read more

If a group of contacts qualifies for a survey that you decide you don't want them to get (or you accidentally let them qualify), there needs to be a way to remove them from the survey during the survey delay.    For example, if the survey send delay is 2 days, you should be able to see who is in the queue for the survey and remove them if you do not wish for them to receive it.    Survey workflow controls should more closely mirror workflows rather than having no visbility into which contacts are in the waiting period and no control over unenrolling them. ...read more

Currently, Load Balanced routing distributes tickets to the user with the fewest total open tickets. This rigid counting logic makes the feature impossible to use for teams that handle a mix of quick transactional tickets and long-term complex issues.   We have agents holding longstanding tickets that are effectively "parked" or require low daily effort (e.g., tickets waiting on a vendor or customer response). Yet, these still count against their total capacity. Consequently, the system incorrectly assumes the agent is "busy" and stops routing them new, quick-turnaround tickets, which overburdens other team members.   The Solution: To make Load Balancing viable for complex support teams, we need two specific enhancements that allow for true workload equity rather than just ticket-count equity:   Exclusion Criteria for Open Tickets: : We need the ability to define what counts towards an agent's capacity. For example, we should be able to exclude tickets in specific statuses or pipelines from the load balancing count. Ticket Effort Weighting: Not all tickets are equal. We need the ability to assign a weight or capacity cost to tickets based on their properties (e.g., a Tier 3 ticket counts as 3 capacity points, while a Tier 1 counts as 1 capacity point). ...read more

I’d like to suggest an improvement to the card layout options in the centre panel, specifically around how properties are shown.   Right now, when using the Property List card type, properties are displayed in four columns across multiple rows. This makes the information quite hard to read; rich-text fields become blocky, and the overall layout ends up being more confusing than helpful.   I know there is also a Table card type, although it presents properties horizontally rather than vertically, which is equally restrictive and difficult to read.   Some of the challenges with the current layout: It is difficult to get quick, at-a-glance information because properties are spread across four columns; users have to scan around to find what they’re looking for. Fields that logically belong together often end up split across rows. For example, first name might appear at the end of the top row while last name appears at the start of the next row. Longer text fields disrupt the layout and make it even harder to locate the property you want.   Other posts I have seen say to create a custom card via UI extensions, but that's an overly burdensome ask for something as basic as displaying properties in a clean, readable list. Users should not have to resort to custom code just to see their properties in a tidy, vertical, inline format.   A simpler layout would make a big difference: an inline, vertical table-style view where each property appears on its own row, with the property name on the left and the value on the right. This would keep everything clearer, neater, and much easier to read.     Thank you ...read more

Hi everyone I’d like to suggest a product improvement for HubSpot reports and dashboards that I think would have a big impact on usability and analysis:   Add the ability to filter reports and dashboards using an Associated Records dropdown, in the same way we can already do it in Index Views:     What do I mean exactly? In Index Views (for example, in deals or contacts), we can already filter very quickly using dropdowns based on associated records: companies, contacts, deals, etc.   The idea is to bring that same experience into reports, so we can:   Filter reports by associated company using a simple dropdown. Filter by owner, pipeline, contact, or any associated object without having to edit the report every time. Allow end users to “play” with the data using simple filters, without needing access to the advanced report builder.   Why would this be useful?   It would make reports more dynamic and reusable (one report, multiple views depending on the association). It would significantly improve the experience for sales/CS teams, who often work by account, segment, or owner. It would reduce the need to duplicate the same report just to change an associated record filter.   If this would be helpful for you as well, please give this idea an upvote so it gets more visibility with the product team. ...read more

Previously we were able to navigate directly from the member we were talking to, to their lists page, From this page, we used to have a drop-down button Manage Registration which gave you the option to either Resend registration email or Reset password.  So this meant there were 2 clicks to reset a password, and that my team could stay on the tab they were working on with the member.  Now, if a member calls or emails for a password reset we need to: Click Content Click Memberships Scroll the list and then click the list named KB Access: All Members - List Sync  Find the member using the search option Then click password reset or resend registration.   This new process requires opening a separate tab to the member profile and then 5 clicks versus the old process which was 2 clicks. My team’s morale is down about it, so they are working even more slowly. Please implore your leads to undo this terrible move. We need the button back on the member’s profile for efficiency. ...read more

Hi HubSpot Community,   I recently discovered that HubSpot’s native file attachment area appears to have a 10-file upload limit per batch. While this isn’t officially documented anywhere, it seems to be a built-in system limitation.   For one use case, this restriction has been quite challenging — the team often needs to upload multiple photos and management reports to Deals and other record types including Custom Objects from said record, which can easily exceed that limit.   It would be great to see HubSpot enhance the file upload functionality in future updates to allow larger or unlimited batch uploads.   If anyone has workarounds, or if HubSpot has plans to expand this functionality, I'd love to hear more.   Thanks, ...read more