クリエイティブな才能を開花させよう

I would like to share some feedback regarding the support form on HubSpot accounts.   As you know, when submitting a support request, users are provided with a simple text field where they can enter their message and attach files:   HubSpot contact support form   While this is helpful, I believe there are some improvements that could greatly optimize the user experience and the effectiveness of the support process.   Firstly, I often find myself wanting to include formatted text or hyperlinks in my initial support requests to provide additional context or resources.   However, the current text field lacks the ability to format text or add hyperlinks, which can make it difficult to convey information effectively. It would be beneficial to have a rich text field, similar to the one available in the Support Inbox, to allow for better communication and clarity:   Rich text field in HubSpot Support Inbox   Additionally, the size of the text field is fixed, which can be limiting for users like myself who frequently need to provide detailed information or multiple pieces of information in their support requests.   Having the ability to adjust the size of the text field would greatly improve usability and ensure that all necessary information can be included without constraints.   I believe these small improvements would go a long way in optimizing the support experience for users like myself who rely on HubSpot for assistance. ...その他を表示

Before the latest update, HubSpot users could contact support and view their support inbox through the purple help button presented at the bottom right of their portal. Now, in order to contact support and view our support inbox, we must go through the question mark symbol in the top right of the toolbar. Unfortunately, through this method, we must interact with the support bot before being able to access the support team or the support inbox. This update is not intuitive or user-friendly.  ...その他を表示

So I am working on creating sales goals for my team. Something I am unable to do but would be beneficial is to have somewhere to input actual revenue for the prior year (or even month). We are wanting to compare year over year and are unable to do so because we started using HubSpot in February at my company so we don't have deals from 2023.  ...その他を表示

Gathering tickets at a company level is a must have. More and more of our customers are in multi-site environments, where tickets are managed by a super-user for all related companies. At present, the portal only allows to view tickets for the main company. Our customers need to be able to view in their portal all tickets from all companies grouped under a parent company. ...その他を表示

Hi all.   HubSpot has an "Enforce Two-Factor Authentication (2FA) for All Users" security option but (and I have followed this up with Hubspot Support who have agreed with my observation) it is ineffective since:   a) Users can bypass this control simply by selecting "Remember me" at login time.    b) Users can authenticate using only their password on mobile devices, once again bypassing the 2FA requirement.   This lax approach to security policy enforcement may put Hubspot customers (err... me!) at risk of legal action. Consider the scenario where my organisation attempts to appropriately protect the PII of its clients (those whose data we have stored in Hubspot) by enforcing 2FA, as per to legislative requirements such as the APPs (Australia) and the GDPR (Europe).  Aside: Such 2FA requirements for the protection of PII are also generally found in cyber-insurance policies.   Now consider the case that an employee disregards the director's instruction not to use the "Remember me" security bypass hack and/or uses their password to authenticate to the mobile app, and that later, the employee falls foul of a phishing or password spray attack.   That user's Hubspot account can now be compromised by the attacker, and the HubSpot customer (the user's employer) may be exposed to legal action because they will be unable to show that they protected the exposed PII according to legislation and insurance requirements. Instead, the plaintiff lawyers will show, correctly, that in fact the customer (employer) allowed access to PII via nothing except a stored cookie.   It's nearly March of 2024 and breaches of PII are a weekly (if not more frequent) occurrence. I can see no possible way that, if the PII that is in our care is breached, that I will be able to defend myself against an accusation of negligence, if the only defence I have is that I told non-technical sales staff to delete a certain cookie every eight hours.   My insurance, the APPs and our PCI DSS compliance requirements demand that I actually implement effective 2FA and logging (and I'll raise another issue about security logs later!) and I am very concerned that allowing users to bypass the 2FA security setting will land me deep in lawyer **bleep** if a user account is breached and the PII in our care ends up on the dark web.   I strongly recommend Hubspot configure the security settings so that the settings do what they say on the tin: Specifically, disallow security bypass hacks and password-only authentication on both web and mobile apps, and enforce 2FA on every login.   Cheers!           Tim.   PS:  Considering the fact that it's a big deal nowdays, Hubspot might also want to have a category below for "Security".  For now I'll log this under Hubspot Support.  ...その他を表示

The goal is to have an automated Zip file creator, which allows my visitors to download multiple files at once. These files are sorted by a HubDB table.   Details: My products have a wealth of informational documents associated with them. Spec sheets, user guides, 3d step files, viewer software. etc. When a visitor wants a user guide, we ask for name/email. Next visit if he/she wants a different file, we then ask for job title. HubSpot progressive fields at work. All good! But...   In addition to this, what if we add a button to rule (download) them all?   The visitor fills out a long form and gives the 6 qualifiers my Sales team wants. First name/last name/email/job title/phone/country but in return, they get the entire suite of files associated to the product.   Sometimes the same file is used for multiple products, so a manually created zip file will not do. When one of these files is updated, ALL copies need to be updated as well. To counter this, we can pull the file names from a HubDB table and package them into a zip folder on demand.   No more updating the same file in multiple places and the visitor has all the information they need to help them in their buyer's journey. ...その他を表示

In the dynamic world of digital marketing, where speed and precision are paramount, email marketing plays a crucial role in engaging with customers. However, for those of us relying on HubSpot as our go-to email marketing service, a frustrating obstacle stands in the way – the 24-hour sending rule. This rule requires marketing teams to schedule emails with local time zone sends at least a day in advance, hindering the ability to deliver messages at specific times to target audiences across different time zones.   This is frustrating because the essence of effective email marketing lies in delivering messages to recipients at the right time, maximizing engagement and conversion rates. Unfortunately, HubSpot's 24-hour sending rule adds an unnecessary layer of complexity to this process. Marketing teams are required to plan and schedule emails a day in advance to ensure timely delivery, limiting their ability to respond swiftly to changing circumstances or capitalize on real-time opportunities.   Our marketing operations are often hindered by HubSpot's rigid sending rule, preventing us from seizing spontaneous opportunities or adjusting campaigns based on real-time data. This inflexibility not only impedes our ability to stay ahead of competitors but also hampers our responsiveness to the ever-evolving needs and behaviors of our target audience.   Many alternative email marketing platforms, including Klaviyo, have recognized the importance of immediate responsiveness in the digital landscape. Klaviyo, for instance, allows marketers to send emails immediately to recipients in time zones where the designated send time has already passed. This feature not only enhances the precision of our campaigns but also provides the agility needed to navigate the complexities of modern marketing.   Given the advancements in technology and the capabilities of modern email marketing platforms, HubSpot's 24-hour sending rule appears increasingly nonsensical. In a world where instantaneous communication is the norm, the inability to send an email promptly to a specific audience undermines the very purpose of an email marketing service. It's time for HubSpot to reevaluate its approach and align its features with the evolving needs of marketers.   In conclusion, we are urging HubSpot to reconsider its 24-hour sending rule and embrace a more flexible and responsive approach to email marketing. By removing this arbitrary constraint, HubSpot can empower marketing teams to operate with the agility necessary to thrive in today's competitive landscape. As loyal users, we believe that HubSpot has the potential to be a strong competitor in the email marketing industry by prioritizing user-friendly features that truly enhance the effectiveness of digital marketing campaigns. ...その他を表示

Hi,   I want a pony.   I discussed this after my initial request to sync with Salesforce had been resolved excellently by HubSpot Technical Support. So, since that was done to my satisfaction, I asked for a pony. I was told that I cut out a bit and to please repeat what I said, so, I restated my request and was told, unfortunately that that cannot be done   I was then told that it would be "so awesome if I could make a pony gallop across your screen right now." I agree. I said I would file this as a ticket in HubSpot Ideas. So I am.   I think that it would largely be agreed that we work pretty hard and that we deserve ponies.   If you agree, pleaseee share this with your teammates and vote this up. We want ponies. We each deserve a pony. We demand ponies. Give us our ponies. ...その他を表示

Hello,   We have many customers who raise an issue by emailing it to our support email and it creates a ticket, those customers also then use the portal to track the ticket progress and see all their tickets and email correspondance. However our customers struggle with the portal as the tickets in the customer portal do not show the initial ticket description field so it is hard to know what the issue raised was.  Could the ticket description field be added to the customer portal please, sort of like in the red box in the image.   ...その他を表示