Great minds think alike

I find very handy the feature to clone a quote. For me is especially useful when you have a similar quote that you need to redo.   My problem is that when I need to clone, a quote is not for the same deal.  Let me try to explain: 1) I create a deal A  2) Inside deal A, I create a quote QA 3) Deal A is won, and the quote QA is signed. Great. 4) After a while, I create a Deal B similar to Deal A, so I go to Deal A, and I clone QA, and I obtain a QB associated with Deal A.   Now I have deal A with quotes -> QA and QB and I have deal B with no quotes   Now I need to be able to associate quote QB with a deal B   Is it possible?   ...read more

It would be nice that within the pipeline flow we could place mandatory properties as it can be done today but that depend on another property, if I have a customer that I know visits my branch, the date is mandatory but if he does not visit it, it is not, for instance ...read more

The main objective would be to be able to define or change the value of a property of a specific transaction based on a task completion status.    There are multiple ways of doing this but after trying many options, I found that the easiest one would be to have "Activities: properties" as a trigger for transaction-based workflows (as we currently have for Contact-based workflows). It's currently possible to do this for contacts but not for specific transactions.   An example of what is possible today and what I would like to do:   Context: 1 contact 2 associated transactions ("Transaction 1" and "Transaction 2")   Today:   Transaction 1 reaches phase 3 of its pipeline. A task ("ToDo A") is automatically created. This task is linked to Transaction 1 and the contact.    Another transaction-based workflow does: if "Todo A" is completed, then define "Property X" to "Yes". That will modify Property X on both Transaction 1 and Transaction 2, even if Todo A is only linked to Transaction 1 because there is no way to identify the transaction.   Tomorrow:   Transaction 1 reaches phase 3 of its pipeline and a task ("ToDo A") is automatically created. This task is thus linked to Transaction 1 and the contact.    Another transaction-based workflow does: if Todo A is completed, then define Property X to "Yes" only for transactions associated with this Todo or only for transactions in phase 3 or only for transactions with property Y value = "Yes".   I hope it's clear, and that we'll soon have a solution to this major problem that requires minimal improvement in the way workflow works (I guess) ...read more

Different levels meaning. If I have a deals size under a certian figure my company alouds this to go through without any approval from a supervisor but if the deal size is high it should go directly to supervisor for approval. Look into GetAccepts approval process for qoutes to learn more about a perfect process. I would love to have it becuase now my sales guys are furious that all qoutes needs to be approved by me.  ...read more

This would essentially allow us to create a unique job number with each new deal. It would be so useful and would then be used as the root for a whole range of quotes and orders. There is a similar request here https://community.hubspot.com/t5/HubSpot-Ideas/Deals-Automatically-Associate-A-Consecutive-Number-To-Each-New/idi-p/15770 which is marked as resolved. However this is NOT true. The problem solved is a unique ID to avoid duplication, NOT a sequential 4/5 digit number increasing with each new deal created.   I really would like a sequential , human useable number to be generated with each new deal within a range of contexts i.e. across company or within a given pipeline etc. I'd like to be able to set the seed number i.e. a 5 digit number starting 10000. I'd definitely want the number to be available to add to the deal title when it is created. ...read more

It would be super helpful for clarity if you could define rules in the list view of deals and tickets that would highlight rows in color if they do not meet certain filters. For example, highlight in red all deals that have not yet been completed and won ...read more

We would like to have a better overview of the attachments in our deals. Ideally we would like to add "Attachments" in the columns when we see our Deals as "list view". In our case these are recordings so we would like be able to listen to them without downloading the attachment.  And of course have a function to be able to download the recording if we wish.     ...read more

Hi!   It would be a great addition to the already-existing deal conditional logic for deal stages and deal creation if there's a custom property conditional logic WITHIN the deal stage conditional logic if the latter is being moved to the next stage.   Context: We have a lot of deal owners that are having trouble filling out service line revenues within the deal because if all of the relevant service line fields are chucked in to the deal form whenever a deal stage is to be moved, it's going to be a LOOOOONG list of fields that the deal owner would be filling out on the deal form alone.   If we then remove all of the service line fields from the deal form and place it only on the left sidebar, chances are the required service line revenue fields will go unfilled when a deal has been closed won (hence, delivery teams will question either sales or AMs as to why revenues are not filled out accordingly during handover. Having a very complicated "gating system" using a combination of workflows and email alerts would not be scalable (and sustainable) too when the company's service portfolio increases.   Impact: Reduced data integrity especially revenue values, which then causes reports to skew and, ultimately, miscommunication between teams as well as clients   Idea: If we could have something like this (this is just an example, but this is the conditional logic setup example from the deal creation part) that's within the deal stage conditional logic, then this would now serve as a convenient way for deal owners to fill in the missing required data under a specific deal stage before moving it to that stage. Let's say I'll set up the deal stage conditional logic with the required fields, and one of them is "Service/s". So if "Service/s" is SEO, then the SEO-related service line fields will pop-up WITHIN the deal stage conditional logic.   By having this functionality within the deal stage, we can ensure: 1. Better data integrity, ensuring all required properties are filled out completely via the deal form 2. Efficient admin on the side of the deal owner (they'll just be doing admin the deal form rather than going back and forth the deal form and the left sidebar) 3. Seamless deal form basically, no more long list of fields.   I hope you find this sensible! ...read more

Before Hubspot rolled out the Deal Collaborator function we created a property  that worked in a similar way. We would like to do a mass transfer of our Deal Contributor property to the Deal Collaborator option.   Currently, this isn't a property that Hubspot allows imported data to populate. With our hundreds of deals we'd like to make the switch with, this isn't feasible to do manually. ...read more