Playbook reccomendations feel like spaghetti against the wall.
I’d like to have the ability to filter what playbooks show for certain object types. For instance-- It’s great that we have the ability to reccomend playbooks. But the frequently used playbooks also show at the worng times.
Supression filters would be handy.
Yes, this seems like such a basic feature for this functionality. The idea of a Deals playbook showing up on a Contact object is just silly.
Couldn’t agree more - why create a wicked feature and limit it to one object?
I agree 100% - this should be a basic function.
Yes this is essential. We use playbooks to update object properties which is crucial to handing information over between departments. If playbooks are completed on the wrong object it cretes a lot of manual work
This is a massive pain for me as well, just gives the whole feature a messy vibe
I fully agreed with you, having all playbooks available all time is not very handy for the teams. It is more that gets them very confused, which one should I use?.
I have just mentioned this to the support person with who I have talked!
Hi everyone,
I’m Winnie, the Product Manager for HubSpot Playbooks.
Thank you for taking the time to share this idea. We genuinely read and consider everything submitted on the communtity forum.
After review, we don’t have plans to build this right now. This is actually something we find interesting, but we have higher-priority work in flight that we need to see through first. It’s on our radar for future consideration.
What I’m interested in learning is: do you want to both a recommendation filter list & a suppression filter list (e.g. a range of Playbooks can match), or is it sufficient to have a really specific criteria for when a Playbook should appear e.g. same as the recommendation filter, but hide everything else that doesn’t match?
That said, we revisit our roadmap regularly, and customer ideas like this one do influence what we prioritize. Please continue to leave comments and upvotes. I usually reach back out on the Community Forum and will DM folks that have commented to jump on calls to learn more about the use case, or to recruit for early beta testing.
Thanks, Winnie