HubSpot Ideas

Monjogard

Field dependencies in Playbooks

Would be very useful with some smartness to questions in Playbooks (similar to dependent fields in HubSpot forms), e.g. ff answer is  X on question 1, show question 1B, otherwise move on to question 2.

 

A Playbook can become quite tedious for a sales rep to scroll through when not all questions are relevant to the conversation.

 

Also great if a Playbook could update properties on multiple objects within the same Playbook. Now a feature!

Mises à jour HubSpot
Statut mis à jour : In Beta
November 22, 2024 12:53 PM

Hi, I'm Winnie the Playbooks PM. We just went into Private Beta with Conditional Properties in Playbooks this week. It allows for dependent fields or conditional property options in Playbooks. 

 

The rollout is for property based conditional logic. It does not include section based conditional logic nor if/then branching.  

 

If conditional sections or if/then logic branching is what you're looking for, I'd love to learn more! That isn't possible in current Playbooks given the way it was built so my team is actively exploring a new feature we're calling Process Guides for enforcing process in HubSpot. A big part of this feature will be conditional sections / steps and multi-step flows.   

 

We're gathering input from customers on what the top processes they care about are. Check out the loom linked in this survey to see a demo of an early proof of concept and and help us out by filling out the survey by Dec 15th, 2024!

 

The survey is open to any HubSpot customer or prospect. This data will help us decide if we're can move ahead with this project, so please help us out by filling out the survey! 

60 Commentaires
kelseygalarza
Contributeur | Partenaire solutions Diamond

Desperately need branching! The whole idea of playbooks is to do discovery and then do something different depending on what the prospect says/does.

MObry
Contributeur

That would be so helpfull !!!!! We need it it would be so time saver !

MCollier
Membre

I agree! This would be awesome! I would use this feature right away, I can already think of a lot of situations I could use this in.

DanCliff
Membre

This would be a very valuable feature, the whole purpose of a playbook it to capture the relevant information - it doesn't make sense to include every single field option every single time if we could simply select what the theme is and display relevant questions (basically the same functionality that's already supported for dependent object fields).

jmbray
Participant

Definite +1 for adding conditional logic for Playbooks (like if/then branching).  We have customers who request different services, and those services require different input information that our reps need to gather from the customer.

adzleach
Membre | Partenaire solutions Platinum

This is important for our clients, especially when using playbooks for calling.

AThalheim
Membre

Yes please! This would be so valuable in removing some of the visual clutter, for non-relevant questions!

TErickson_OW
Participant

This is 100% needed. 

_BF_
Participant

100% agree a If this then that approach would be fantastic here!

GeeklyMedia
Membre | Partenaire solutions Diamond

So needed!!!

drumicd33
Membre

Agreed! We need this!

LWessels
Membre

This would be extremely useful... currently have to use "if Y go to section X" instructions.

MFerret
Membre

up
Could be really helpful for lost reasons or deep dependencies within fields for qualification.

DFenton
Participant

I don't understand why this is not already a thing when it is in other features. Especially with calls, the conversation can go in so many directions. We should be able to choose conditions and prompts if answered a specific way. The fact that this isn't an option is making our process 1000000x more time consuming and complicated!!

BLewty
Participant | Partenaire solutions Diamond

This would be really helpful. We also have clients who require different products, which have multiple stages of additional dependants. Below is a basic example of what I mean: 

 

Product brandOption oneSub-option
Brand ABrand A, option oneBrand A, option one, sub option one
  Brand A, option one, sub option two
 Brand A, option twoBrand A, option two, sub option one
  Brand A, option two, sub option two
  Brand A, option two, sub option three
Brand BBrand B, option oneBrand B, option one, sub option one
 Brand B, option twoBrand B, option two, sub option one
  Brand B, option two, sub option two
  Brand B, option two, sub option three

 

This is a very basic level. The options and sub-options can total hundreds and if someone is filling out a playbook and has to search through hundreds of options in one go, there is huge room for error. 

AKnechtl0
Membre

Playbooks are quickly becoming an integral part of our sales discovery and customer health scoring process.

I love being able to tie questions back to our CRM however some are obviously conditional based on how the customer responds.

To drive adoption and complete form fills, conditional branching would drive adoption through the roof at my company

EMcCuin
Participant

This is a basic feature that should be included. 

RHumphrey
Membre

It would be incredibly helpful for our team to have this functionality.

RebeccaShultz
Contributeur

This would be very helpful. I use playbooks as walk-throughs, so allowing sales people to bypass questions based on pervious answers would really streamline this.  Also if we could link playbooks to one another, ie if a sales meeting goes well, I would like to be able to send someone directly from the contact playbook to the corresponding deal playbook. 

MYapp
Membre

+1, this would be great.