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

I have noticed that we can look into workflow revision history but we do not have the option to restore that previous revision history. I would really like to be able to restore based off revision history, we can currently do this for landing pages. What is the point of having revision history if there isn't an option to restore it?    I also noticed that if you remove an action at the top of the workflow all following actions and steps are instantly deleted without a warning sign. This is extremly dangerous espically since we cannot restore workflows based on revision history. We just had a very long workflow with an action at the very beggining that needed to be removed. We needed to remove this action and our understanding was that it would just go to the next step in the flow or at least give a warning sign that steps are about to be deleted if you remove this action, but it did not. Now the entire workflow is deleted and we have no way to restore it ourselves.     I wanted to flag this becasue this is potentially very dangerous to user who are updating workflows.    ...その他を表示

Chat support is great, so great that the reps are often all taken 🙂 and the support channel is grayed out. It's tough not knowing whether I could check back in 5 minutes or whether it's best to use another support option.    With that in mind, might I suggest a chat queue. Knowing where I am in line and how long it might take to get to me would be awesome.   Staking a claim to a place in line or at least getting some visibility into the chances of me being able to connecto chat would be great.   Perhaps there's other ways of improving the experience, so hey, whatever works.  ...その他を表示

Is it possible to add an "open all links in new tab" function for blogs? As of now, the default is to have the links open in the same window — if you want a link to open in a new tab, you must manually select each individual link to change the default setting.   For research-heavy blogs, on average we spend an hour per blog solely on clicking on each external link to open in a new tab. As users, since this function is already provided, it would be more efficient to have the option to apply this to an entire body of text.   For our team, this would save us a ton of time. If we could apply this to the entire body to begin with, we could get it done in less than 10 minutes.    Here, you can find a previous HubSpot forum with a similar idea — other people have continuously been experiencing this same issue since 2017. And in terms of SEO, if you’re opening external links in the same tab as your site, this affects both you and your users.    The optimal user experience would be for the external link to open in a new tab, and for the blog reader to continue reading the post, going back to the other tab later. Otherwise, once the reader leaves your website, they likely won’t make it back.    In fact, this HubSpot blog states “opening a link in a new browser window, as opposed to the window they are currently in (your website) makes it less likely that a user will permanently abandon your website for the one you linked to.”    All companies are different. Optimal experiences are different. Workflows are different. We should have the option to decide what works best for us and our clients while having the tools to make our workflow easier.    If we can change link behavior on CTAs manually, why not allow a default setting? ...その他を表示

Customers who know the product could be involved more by adding a chance for them to browse existing feature requests, upvote them and comment them just like in this Ideas blog. Making it available as a community tool would be great, e.g. as a template for pages allowing to link feature requests with user contact and company contact. Other idea would be to just add it as a whole new service hub feature or even an individual "feature hub". The value should be obvious: You hubspot guys could add it as a paid feature, while clients could improve their customer involvement and help to narrow product and service development. Samples would be this idea blog awa productboard, canny or any other tool looking for helping to map feature requests. ...その他を表示

We would like a "Dennis Badge" to be created for community champions. See attached image to use.   ...その他を表示

Currently is there a solution where you can link deals together?    We need a solution that shows phases of deals in separate categories, stages and price points. For example, a deal is started, but an additional line item is added. We don't want to change the deal, because the original deal has already started or in production.    Is something like this being thought of? Or out there already?  ...その他を表示

Set unique permission levels on Projects. For the moment, when users have access to the Projects tools, they are able to see all of the projects within the tool.   We need a way to restrict the access levels of users so that they can only access the projects that they own. ...その他を表示

It would be fantastic to be able to create forms for niche uses that did not map back to contact properties.   One use case: You're doing a special contest or collaboration with a partner where you're  collecting information to offer a product/ service/ or contest that is not part of your core product.    Right now to do this, all of these custom/ niche fields must be created as contacts and map back to contact properties. ...その他を表示

Hi!   There should be a functionality when creating a form, to enable customers receiving an email receipt after they submit anything through a form.   They should receive a copy of their submission within their email. Similar to how Google Forms functions.    Currently, when our customers use our Hubspot forms, they have no documentation or proof of their initial submission. We often have to send this back to them. ...その他を表示