It would be really good to have conditional logic on Playbooks, where if on question one the rep selects option A it displays question 2, if they select option B it jumps to question 3 etc.
We have a wide variety of enquiries coming into Customer Service and Playbooks could be really beneficial to them, but at the moment I would either have to create multiple playbooks or have questions in there that are irrelevant for certain enquiries.
This could also be useful to sales reps as well, particularly if there are product-dependent questions they need to ask.
Hi @matheusjiranWRS, thanks for reaching out! We're still early in development for Process Guides, but we will be starting the the beta process soon.
We're breaking things down into several milestones and it sounds like your use case of Conditional if/then branching or queued conditional sections (think similar to Marketing Forms' queued progressive fields) might be a good fit for you which we're targetting for May.
We won't have feature parity with Playbooks to start, so I'll reach out and see if any of our milestones will be a good fit for you. I'll send you an email with some more details.
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 activelyexploring a new featurewe'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 outthe loom linked in this survey to see a demo of an early proof of concept and and help us out byfilling 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!
Agreed, we have questions in our playbook about how a person heard about us, often the property is already filled in so the question could be skipped. Would we cool to show/hide content based on property values.
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 activelyexploring a new featurewe'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 outthe loom linked in this survey to see a demo of an early proof of concept and and help us out byfilling 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!
We are also looking at this function, it would make the books much more organised being able to follow an if/then branching system instead of showing all the properties/questions required. It goes well with a post I made a while back on creating conditional properties and once completed they remain in place instead of dissapearing to the background. https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Dependent-Properties-Remain-on-the-Objec...
It would help with classifying customers immensley.
I came here looking for Conditional Logic for Playbooks as well. I'm aware of the Conditional properties, they're good but don't cover everything.
Example: a Sales Rep is on a discovery call. If they identify the main pains our prospect is facing (this is selected in a property), I want to be able to display in the same playbook the questions related to the pain selected, hiding the questions related to the pains that were not selected.
For the number of questions is big and they're all open text, having them all as properties to require based on conditional property logic would make our hubspot dirty.
I submitted the Survey Form. Looking forward to see what you have cookin'
Hi @matheusjiranWRS, thanks for reaching out! We're still early in development for Process Guides, but we will be starting the the beta process soon.
We're breaking things down into several milestones and it sounds like your use case of Conditional if/then branching or queued conditional sections (think similar to Marketing Forms' queued progressive fields) might be a good fit for you which we're targetting for May.
We won't have feature parity with Playbooks to start, so I'll reach out and see if any of our milestones will be a good fit for you. I'll send you an email with some more details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
