Grandes mentes pensam igual

It would be a nice feature to be able to set call and meeting types and outcomes by team. ... Exibir mais

When a prospect/contact fills out a form and they are clearly spam, it would be good to be able to mark that contact as SPAM and add to the block emails list. ... Exibir mais

When you need to add a line item to a quote the only information you get from the "Add line item" menu is the name and the cost of the product.   We have many of same products that use the same name but they have different SKU's. It would be nice to be able to edit these menus so you can have them the way you like it. ... Exibir mais

For both contacts and company fields, allow the Admin to make fields required. ... Exibir mais

Currently it seems that files uploaded to HubSpot are served with a static URL and the Cache-Control header directive "max-age=1209600", which instructs client browsers to cache the file they receive for 14 days (1209600 seconds).    Of course, HubSpot also provides an ability to replace files with an updated version, but because that is served through the same URL, users returning to the website or landing page will continue to see the original cached version for up to 2 weeks after the file was replaced.    The only exception to this is if the user forcibly reloads the file URL or otherwise clears their browser cache, but (a) users have to know that they need to do this, and (b) most browsers do not provide a facility for refreshing links to downloadable files, like Word documents or other assets, that are not natively rendered by the browser.   This idea has a couple possibilities: Website/landing pages that link to a file should include a version query parameter in the rendered link, such that this version changes whenever a file has been updated.  This will ensure that users who refresh the website/landing page will see an updated link to the file, and therefore their browsers will fetch the updated file rather than relying on the older cached version. File assets should expire from browser caches more frequently than once every 2 weeks -- at least within 24 hours, ideally within 1-4 hours.  This change need not sacrifice bandwidth resources because browsers that have the file cached will automatically perform a conditional request for the content, and your CDN provider can simply respond with a "304 Not Modified" status in the event that the file has not changed.  The only sacrifice here is the latency of a single round-trip from client browser to CDN edge server to perform the conditional revalidation. The final part required is to ensure that your CDN/edge caches (which are controlled by HubSpot) do not serve older versions of the file for too long, once a new version has been uploaded.  As an external developer, I don't have visibility into this part of your system, but every CDN provider I'm aware of (CloudFlare, Akamai, AWS CloudFront) has controls in terms of static configuration, per-response headers, and on-demand invalidations that can be used to ensure the CDN-cached content is fresh.  I imagine the ideal scenario would be for the CDN cache to have a long TTL, and then to perform on-demand invalidation of the existing URL whenever a new version of a file is uploaded (since I imagine this occurs with much less frequency than the number of times content is served from origin.) ... Exibir mais

I am trying to give access to a team to view live chats that come through our "reservations" inbox but I don't want them to be able to reply or be "active" in these chats. There is currently no option for a normal user to have access to what has happened in this inbox but not be able to reply to it. We do still need this person to be able to reply in other inboxes. ... Exibir mais

I'd like to recommend the ability to group properties together in a bar graph chart or pie chart when making a report. Right now I have to do work arounds by creating a new custom property field or assigning the same color to more than one property value. ... Exibir mais

Hi guys,   Can you consider making E-Sign part of the Professional package €400/mo + €75/user should be plenty sufficient to make it so your users can utilize E-Signatures, it's a very basic function and it feels a cheap tactic that it's gated behind a €700/month upgrade that we (and I'm sure most companies) do not need for any other feature.   Please consider making this a separate module or packaging this into Professional.  ... Exibir mais