In our company we have a pre-sales pipeline, when a deal reach at its last stage in this pipeline, we automatic create a deal in the sales pipeline with all the informations.
But, sometimes in pre-sales, we have deals with the contact without knowing its company from the beginning.
So i want to know if i can oblige the SDRs to associate a company in a specific stage of the pipeline (the stage where i can assure that they know which company they are talking to).
Example: When the SDR move the deal to “Meeting scheduled” he has to associate a company before doing this.
Hi @HenriqueBattu,
Would it also be permissible that the association is required right when the deal is created?
If so, then this is easy. There is a new beta for that:
You can then configure the the record create form under Settings > Objects > Contacts / Companies / Deals / Tickets > Customize the ‘Create …’ form.
Here’s the full announcement:
[Public Beta] Configure associations when a record is created
Dec 8, 2022
What is it?
Currently, you aren’t able to set associations as visible or required when a new standard object record is created. This means that admins lack control over record creation, leading to inconsistent data and gaps in associations between records.
This feature will enable you to set associations as visible or required when a standard object record is created. You will be able to set both standard objects and custom objects as visible or required associations.
Note: This feature is not reflected in the Mobile experience yet.
Why does it matter?
Without this feature, you miss out on being able to segment deals or contact decision makers based on the deal status. For example, if a deal is created, and no associated contact is required, you miss the opportunity to attribute that deal to a specific rep.
How does it work?
Navigate to Object Settings, then click on “Customize ‘Create Record’ Form.”
In the left sidebar there is a section called “Associate [Record] With.” Check boxes to add an association to the form, and set these associations as required using the right panel.
A cardinality icon next to each option represents whether a record of that type can be associated to one or many other object records.
There are three scenarios where the “one-to-one” cardinality option will appear:
- Contact → Companies
- Deal → Companies
- Ticket → Companies
Selecting the Companies → option means that a user will only be able to associate one company record to a new contact, deal, or ticket record, and this company will be automatically labelled “primary.”
If that’s not an option, the only approach I can think of is a bit more elaborate. It requires an assisting custom property which cannot be edited by users.
The approach is as follows: Using a calculated property, a deal property counts how many companies are associated with a deal. A workflow then sets the value in a single checkbox property, let’s say it’s called ‘Company associated to deal’. This checked property is then required property for moving the deal forward, see here. This checkbox property is set to view only and can’t be simply checked by the user when prompted. They will have to associate a company first.
Unfortunately, view only access to properties is an Enterprise feature: Manage view and edit access for properties
If you have an Enterprise subscription, let me know, and I’ll happily elaborate more, if you’d like.
Best regards!
Hi @karstenkoehler. Thank you for your help!
I don’t think that this feature would be a solution for my problem. Because in pre-sales sometimes, we don’t know the contact’s company until our first call.
Example: Our pre-sales pipeline is like this => MQL > Call scheduled > SQL (only here i have 100% confidence that we know the company we’re speaking to) > Meeting Scheduled.
I want to oblige a company association only in the SQL phase. Is that possible?
Hi @HenriqueBattu,
No, it’s not within a Professional subscription. Did you review the second part of my reply?
[T]he only approach I can think of is a bit more elaborate. It requires an assisting custom property which cannot be edited by users.
The approach is as follows: Using a calculated property, a deal property counts how many companies are associated with a deal. A workflow then sets the value in a single checkbox property, let’s say it’s called ‘Company associated to deal’. This checked property is then required property for moving the deal forward, see here. This checkbox property is set to view only and can’t be simply checked by the user when prompted. They will have to associate a company first.
Unfortunately, view only access to properties is an Enterprise feature: Manage view and edit access for properties
If you have an Enterprise subscription, let me know, and I’ll happily elaborate more, if you’d like.
Best,
Karsten