topic Re: Field dependencies in Playbooks - Status changed to: In Beta in Sales Hub Tools

Field dependencies in Playbooks

Monjogard — Wed, 06 Mar 2024 09:39:58 GMT

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!

Re: Field dependencies in Playbooks

kelseygalarza — Thu, 18 Mar 2021 00:32:57 GMT

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

Re: Field dependencies in Playbooks

MObry — Fri, 02 Apr 2021 11:42:15 GMT

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

Re: Field dependencies in Playbooks

MCollier — Tue, 12 Oct 2021 20:56:35 GMT

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.

Re: Field dependencies in Playbooks

DanCliff — Tue, 30 Nov 2021 05:46:46 GMT

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).

Re: Field dependencies in Playbooks

jmbray — Mon, 07 Feb 2022 17:06:08 GMT

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.

Re: Field dependencies in Playbooks

adzleach — Tue, 01 Mar 2022 12:45:25 GMT

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

Re: Field dependencies in Playbooks

AThalheim — Tue, 03 May 2022 13:44:02 GMT

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

Re: Field dependencies in Playbooks

TErickson_OW — Mon, 20 Jun 2022 18:57:16 GMT

This is 100% needed.

Re: Field dependencies in Playbooks

_BF_ — Wed, 22 Jun 2022 08:37:18 GMT

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

Re: Field dependencies in Playbooks

GeeklyMedia — Wed, 28 Sep 2022 19:08:35 GMT

So needed!!!

Re: Field dependencies in Playbooks

drumicd33 — Tue, 07 Feb 2023 02:24:17 GMT

Agreed! We need this!

Re: Field dependencies in Playbooks

LWessels — Wed, 15 Feb 2023 22:50:50 GMT

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

Re: Field dependencies in Playbooks

MFerret — Mon, 20 Feb 2023 10:18:14 GMT

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

Re: Field dependencies in Playbooks

DFenton — Thu, 09 Mar 2023 16:05:58 GMT

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!!

Re: Field dependencies in Playbooks

BLewty — Fri, 24 Mar 2023 03:45:33 GMT

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 brand	Option one	Sub-option
Brand A	Brand A, option one	Brand A, option one, sub option one
		Brand A, option one, sub option two
	Brand A, option two	Brand A, option two, sub option one
		Brand A, option two, sub option two
		Brand A, option two, sub option three
Brand B	Brand B, option one	Brand B, option one, sub option one
	Brand B, option two	Brand 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.

Re: Field dependencies in Playbooks

AKnechtl0 — Fri, 24 Mar 2023 18:05:51 GMT

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

Re: Field dependencies in Playbooks

EMcCuin — Fri, 31 Mar 2023 15:50:05 GMT

This is a basic feature that should be included.

Re: Field dependencies in Playbooks

RHumphrey — Wed, 31 May 2023 18:08:50 GMT

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

Re: Field dependencies in Playbooks

RebeccaShultz — Thu, 01 Jun 2023 15:59:41 GMT

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.