I was wondering if it is possible to create custom task fields.
The current usecase is that we want our Account execs to flag when a contact should or shouldn't be contacted by the BDRs.
The issue is that BDRs work off of task and AEs work on deals.
Ideally....upon deal creation the AE would select a field value (One of these 3: contactable - not contancble - check w/ AE) and this would transfer to the associated company, contacts and tasks related to the contacts (as this is where the BDRs work from).
Although unfortunately I am already stumbling as I am unable to find where to create custom tasks fields.
The product team reviews these requests based on their popularity. I'd recommend upvoting and commenting. You can also help others find the request more easily (and drive traction) by accepting my reply as a solution. I'd appreciate it, too!
Generally, it does however sound like your AEs and BDRs should both maintain information about who should be contacted or not on the contact record. It would be a change in the mode of working but storing this information in tasks would not be good data hygiene.
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
I have already upvoted that idea, although can see that it is currently not planned. Is there a specific threshold of upvotes on which the product team commence reviewing the idea?
On your point of data hygiene: the information would be created - stored on the Deal/Company/Contact object and then just pushed through to custom task field and would be mainly for the visibility of the BDRs as they work off of Prospecting/Sequences and tasks.
I am happy to upvote your reply but struggling to see how I could accept this as a solution as you just confirmed what I thought wasn't possible on the system.
I have already upvoted that idea, although can see that it is currently not planned. Is there a specific threshold of upvotes on which the product team commence reviewing the idea?
On your point of data hygiene: the information would be created - stored on the Deal/Company/Contact object and then just pushed through to custom task field and would be mainly for the visibility of the BDRs as they work off of Prospecting/Sequences and tasks.
I am happy to upvote your reply but struggling to see how I could accept this as a solution as you just confirmed what I thought wasn't possible on the system.
Can you elaborate why you would want to pass on information about a contact who should not be contacted in a task to a BDR? Which purpose would the task serve?
If you want to include information in a task, you can also pass information to the title via personalization tokens and workflows. This would also allow for search. Trying to better understand your use case.
And no, there isn't a guaranteed threshold for review of ideas, I'm not aware of any.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
The main reason is because BDRs work off of tasks and use sequences/prospecting - so this would be to avoid having the BDR reach out to a contact when the AE is already in advanced commercial conversations with the company.
The issue is we work with big companies, so certain users/departments in the company who are already in conversations with AEs should not be contacted by BDRs but other departments/contacts should still be contacted.
I am happy to use workflows to transfer this information but i'm unable to see how I'd transfer from the company/deal/contact level to the task.
@karstenkoehler Thank you!! Always good to get the opinion of someone who is an expert on these tools.
Say the AE creates a Deal and wants to pause all BDR communications, he would select this field Flag for BDR - and set values to Do not contact OR Check with AE.
This would trigger a workflow to push the value of Flag for BDR field (on deal/company level) to Flag for BDR custom field on all tasks related to the company.
In the end, Management is happy for me to display only on Deal and Company level, so all good!
Understood, thank you, @ArtyCele. And how would an AE find and update that task if there was a custom task property? That's the part I'm struggling to understand.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
The product team reviews these requests based on their popularity. I'd recommend upvoting and commenting. You can also help others find the request more easily (and drive traction) by accepting my reply as a solution. I'd appreciate it, too!
Generally, it does however sound like your AEs and BDRs should both maintain information about who should be contacted or not on the contact record. It would be a change in the mode of working but storing this information in tasks would not be good data hygiene.
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer