Las grandes mentes piensan igual

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

We use stand alone invoices (for B2B commerce) and also online payments.  We would like to encourage the client to use ACH/direct debit as opposed to mailing in a physical check.    Currently, there is no way to give a discount to make this encouragement.  Either the whole invoice has to be (one-time) discounted or payment links with discount codes have to used.  Neither of these options work for us.  We don't want to discount clients paying by check and we can't just make payment links. We need to send an invoice ahead of time (net 90) to the client.   Can we get discount codes to also work for invoices?  Payment links can create invoice it seems (after payment) so why not support it on invoices?   Alternatively, can the existing payment fee structure be allowed to use negative numbers?  I can add a 3% fee for credit card payment, and I can add a positive fee percentage for direct debits but not a negative value.  ... Mostrar más

TL;DR At month-end, the Scheduler displays a calendar filled with past dates and a zero-state message (“No available dates this month”), along with an email link. Many visitors bounce instead of clicking to the next month, which leaves unused capacity at the start of every new month.   This is an expensive UX issue for us.   Problem The calendar is locked to the current month, so most of the UI becomes unbookable days at the month's end. When the remaining days of the month have no slots, the page shows an email and a “next month” control—users often stop here and do not advance. Result: higher abandonment rate and under-utilized availability on the first days of the following month (costly for teams that staff to capacity).   Proposal Add a rolling, future-only view with these behaviors (as a setting or default): Hide past days in the current month. The past is never bookable. Auto-advance to the next available date when the rest of the current month is fully booked. Highlight “Next available: {Date}” and preselect that day/time list. Optional admin setting: show the next N days (e.g., 14/30) regardless of month boundaries. Also, you can use the scheduler's availability window.   Expected outcomes Fewer bounces at month-end; more bookings in the first week of each month. Clearer UX: visitors always land on a screen with bookable options—never a dead end.   Examples: Zero Availability = High Bounce Rate Example: Past Dated Dominating the UI Examples: Excess Availability at Start of Next Month   Our Context We are on the Platform Enterprise plan. We are aware that there are scheduler alternatives that are compatible with HubSpot, but they are more feature-rich and expensive than we require. We need a simple scheduler that shows available future dates by default. Please upvote if you see a similar drop-off at the end of each calendar month. ... Mostrar más

Some of my customers wish that their CRM Users see fields that are created as "single Checkbox" as a "Checkbox" field (to check/uncheck) in the left column on object level (and other places). I am very surprised that this is only possible in forms. Why can't I change the visualization from "dropdown" to a "Checkbox"? ... Mostrar más

We do a lot of site migrations from WordPress and other CMS' to HubSpot, and as we know WordPress always has the trailing slash and other CMS's have it, and in order to not hurt any SEO we need the ability to keep this. When it comes to HubDB Dynamic Pages, there is no way to add the trailing slash in the path column. It would be great if there was just a global control to have this turn on if we need.   ... Mostrar más

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

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

Changing the Enter key behavior in the helpdesk from “send message” to “create a new line” would significantly reduce accidental sends and improve communication quality. Right now, pressing Enter too early can trigger incomplete or half-written replies, which can confuse customers, interrupt the flow of a support conversation, and require follow-up corrections. By making Enter simply move to the next line—while using another shortcut or the send button to submit the message—agents gain more control and confidence when writing longer or more detailed responses. This small adjustment helps prevent misclicks, reduces message clutter, and keeps interactions cleaner and more professional. This change also aligns the helpdesk with the typing behavior found in most modern communication and ticketing systems, where Enter creates a line break and sending a message requires a deliberate action. Because agents frequently multitask and work quickly, intuitive and forgiving input behavior matters. Allowing Enter to insert new lines makes it easier to structure thoughts, organize troubleshooting steps, and craft clear responses without the fear of prematurely sending a message. Overall, it enhances usability, boosts agent efficiency, and supports a smoother, more polished customer experience. ... Mostrar más

Please implement support for Subresource integrity validation (https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) Reason 1 to implement this security measure: When a resource is referenced on the HTML code with a different domain from which the same HTML was loaded, then a malicious actor could interfere in the DNS resolution on the end user's machine, to make the resource be downloaded from a different location. Thus, a resource referenced with "https://js.hs-scripts.com/***.js" could be downloaded from a malicious server with malicious code. This type of attack can be prevented if HubSpot adds a verification string that allows the browser to confirm that the received asset is the expected one, without alterations. Reason 2 to implement this security measure: Even if there is no attack from a malicious actor. Security audits rise this security flaw as a vulnerability, causing reputational damage to the people maintaning the website and to the website's owner. Please provide a solution to this. ... Mostrar más