Looking for early users for Required fields feature
Hello all,
Me and my team are looking for early users for Required fields feature. More info is to follow in this post, but if you are interested in having more control on what data is required to add deal/org/person, please leave a comment with your email here.
Best regards,
Kirill
Comments
-
Would love to test it!
0 -
0
-
-
what level subscription would be needed to have this once it goes live? Do not want to enable a test that get taken away down the line.
0 -
-
Please add easycrm thanks
0 -
-
Would love to be involved. Brandon at ectucson.com
0 -
interested
0 -
Please enable [email protected]
0 -
-
0
-
0
-
Hi Kirill
0 -
Please enable [email protected]. I would love colaborate!
0 -
-
Yes please! [email protected]
0 -
-
Count me in - [email protected] :-)
0 -
Ill be happy to test!
0 -
fx (at) 4front.tech thanks
0 -
Hi. I want to try it and give my comments.
Important fields without filling your data is one of the headaches in the use of crm
0 -
Nathan Weill said:
Yes please! [email protected]
@Kirill Grebtsov, what's the ETA on this? Can't wait to test!
0 -
Hi there, I'd like to test this feature and also give some feedback. I don't work in the B2B field, I work directly with consumers. I like how Pipedrive allows sorting and reports based on "organization" but in sales, what I really need is to track my highest converting referral sources and business partners, so that I can tweak my business activities based on this. Thank you.
0 -
Yes please, though I worry that this undermines the principal of Pipedrive of being easy to use hence the extremely high uptake with sales people. If mandatory fields are introduced it might kill this. I'd rather see a nagging feature that constantly prompts for fields to be completed, similar to important deal fields but on organisations and people. As an example, let's say management want the postcode set as a mandatory field and I have a lead but don't know the postcode just yet. I won't be able to capture the lead in Pipedrive and will probably never remember to do it later.
0 -
Jason Rainbird said:
Yes please, though I worry that this undermines the principal of Pipedrive of being easy to use hence the extremely high uptake with sales people. If mandatory fields are introduced it might kill this. I'd rather see a nagging feature that constantly prompts for fields to be completed, similar to important deal fields but on organisations and people. As an example, let's say management want the postcode set as a mandatory field and I have a lead but don't know the postcode just yet. I won't be able to capture the lead in Pipedrive and will probably never remember to do it later.
I do believe that it's a powerful tool that can be used for both good and bad, this is why when designing required fields we have thought of salespeople and introduced an option for management to choose in what stages certain fields are required, so that deal flow is not impacted.
Additionally, you mention leads and this part is covered by our Lead inbox which is built around fast lead capture and qualification
0 -
-
Jason Rainbird said:
Yes please, though I worry that this undermines the principal of Pipedrive of being easy to use hence the extremely high uptake with sales people. If mandatory fields are introduced it might kill this. I'd rather see a nagging feature that constantly prompts for fields to be completed, similar to important deal fields but on organisations and people. As an example, let's say management want the postcode set as a mandatory field and I have a lead but don't know the postcode just yet. I won't be able to capture the lead in Pipedrive and will probably never remember to do it later.
@Jason Rainbird - respectfully, I don't think that's a problem with having mandatory fields as much as with the way people design their sales process. Clearly, active dialog needs to happen around "what do we absolutely need to capture and where in the process do we need to capture it". We've actually engaged our sales reps and brainstormed about what the minimum bar should be. This really helps in getting it right.
The way it works now is elegant - and we shouldn't throw this out. I think most people just ask for the possibility of stronger enforcement than the current "nudge" of important fields.0 -
@Mike van der Valk Am I supposed to see something that I don't? Or has this not been enabled in my org yet?
0
