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!
Hi everyone! My name is Hallie, and I'm an Associate Program Manager on the CXM team here at HubSpot. I wanted to share an update that this is now live for playbooks! You can read more about the feature in this product update. Attached is a screenshot showing more information about using conditional properties in playbooks (in addition to the screenshot in this comment) :
I would love to see HubSpot take Playbooks to the next level by introducing conditional sections, if/then logic branching, and multi-step flows. These additions would significantly enhance the flexibility and power of Playbooks across Sales, Service, and Onboarding teams.
Imagine Playbooks that adapt dynamically based on user inputs; guiding reps through smart, context-aware conversations or processes. For example:
If a customer selects “Enterprise” then show advanced qualification questions.
If a rep logs a technical issue, then automatically load the troubleshooting steps.
If onboarding step A is complete, only then show step B with relevant instructions.
This would turn Playbooks into truly interactive workflows, helping ensure consistency while saving reps time and reducing errors. A more intelligent Playbooks tool could easily become a central hub for guided processes in HubSpot.
This need has become even more clear from my experience using Playbooks internally. I created the questions in the order steps should be followed, but users often repeat steps or skip some by mistake. A recurring piece of feedback is that seeing the entire Playbook at once can feel overwhelming. On top of that, having to skip steps manually (as per instructions) based on previous answers can be confusing; especially when users are in a rush, which increases the risk of missing critical steps.
Hi everyone! My name is Hallie, and I'm an Associate Program Manager on the CXM team here at HubSpot. I wanted to share an update that this is now live for playbooks! You can read more about the feature in this product update. Attached is a screenshot showing more information about using conditional properties in playbooks (in addition to the screenshot in this comment) :
The rollout is for property based conditional logic. It does not include section based conditional logic nor if/then branching.
Ifconditional 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!
Absolutely critical to making playbooks worth using for live scenarios. When trying to convert a series of Yes or No questions into a playbook, it's difficult for teams to navigate where they should go next when they have to search through the playbook for the correct next step.