Playbooks need an upgrade!

:telephone_receiver: Playbooks should have the option to not log as a call, it should be able to be completed without associating it to an activity.
:sparkles: Playbooks should have the option to be required between stages (deal stages, ticket statuses, and lifecycle stages)
:repeat_button: Playbook questions should be able to copy to a property natively without having an enterprise hub. This feature is SO POWERFUL for SMB and Mid-Market sales teams but never gets used because the enterprise hub isn’t worth the upgrade to them.
:books: Playbook completion should be targetable with workflows. Spinning off automation from the playbook being completed OR not completed is a simple workflow that can hold sales reps accountable for accurate data tracking.
That is my playbook plea, sign below if you agree :palms_up_together:

+100…especially being able to log a playbook without it being a “call”

Yes, playbooks are the secret weapon to getting good data in - would be very useful on Pro level

You can log the playbook as a note, email or meeting under settings. I added a screenshot below.

I’m also looking for the following:

1. Conditional logic is needed. We want our teams to be able to use these playbooks to help qualify leads or gather information. Based on responses to a particular question, we want to gather more information or skip to a different section entirely. ex: if yes, ask second question for more info
Conditional logic is currently available in properties and forms - why not in playbooks?
2. Use of snippets in property responses. Currently you can only use snippets in the “Notes” field which does not save to a record, we want the ability to use snippets when responding in a multi-line text property (answer to property is only available in enterprise)
3. Save and skip to a new section or playbook. Would be nice to be able to more easily skip between sections.

4. Abilty to EXPORT the submissions to excel or pdf!

Hi, I’m the PM for Playbooks and we’re starting to explore a couple of new ideas with them.

We know Conditional Logic and Sections is a big ask and we are starting to think about it.

I’m currently doing research on mandatory Playbooks. If you’ve got feedback on requiring Playbooks at a certain stage or ensuring compliance, I’d love to chat. Send me a DM with your email and I’ll get a call scheduled. Thanks!

Hi, I’m Winnie the PM for Playbooks. I’m following up on this thread with an update. We’ve researched this more with the engineering team and a few of these requests will be difficult to implement in current playbooks. As a result, we’re actively exploring a new feature we’re calling Process Guides that will try to tackle this more holistically.

These are the features we’re actively looking at including in the new Process Guides:

:telephone_receiver: Playbooks should have the option to not log as a call, it should be able to be completed without associating it to an activity. <-- Flexible logging of Process Guides
:sparkles: Playbooks should have the option to be required between stages (deal stages, ticket statuses, and lifecycle stages) <-- Prompting and requiring Process Guides based on stages or events
:books: Playbook completion should be targetable with workflows. Spinning off automation from the playbook being completed OR not completed is a simple workflow that can hold sales reps accountable for accurate data tracking. <-- adding actions / triggers to each step of a Process Guide or to the completion of a Process Guide.

CTA request: We’re gathering input from customers on what the top processes they care about are. Check out the loom linked in this survey and help us out by filling out the survey by Dec 15th, 2024!

The survey is open to any HubSpot customer or prospect. Thanks in advance for the great feedback this community offers to us in Product at HubSpot!

-Winnie, PM of Playbooks and Process Guides

cc: @crispyGTM, @CSic, @CUrsu1, and @Jnix284 for your input and a preview into the new Process Guides.

Looking forward to see the Process Guides in action. Do we have a timeline?

@CUrsu1 , I’ll send you a DM about booking time to chat more about it. :slightly_smiling_face:

Very excited to see this idea has tractions! I’m hopping back into the platform after some time away, saw Playbooks, and thought, “This is exactly what we need!” …but was immediately cast back down to Earth when I saw that it can only be updated as a logged call. Would love it if the ability to disassociate Playbooks from logged activities rolled our ASAP, even if the other, more complex features take some time to implement.

We need to be able to make a playbook required when a ticket is a certain property - anyone know of a way to do this currently?

I would love to get more information about playbooks completion being required for automatic stage movement. Please advise on timeline of feature. thank you!

Playbooks are awesome as a tool. But we need more conditions on where and whom should we show them.

  1. For example, some Playbooks are valid only for the Deals, some for Custom Objects. I would really liek to see the optional setting not to “recommend” Playbook on certain stages, but show the Playbook on certain stages or at least Pipelines. So it would be a great boost if we could create many Playbooks for different objects and the team didn’t get overwhelmed with them on every Object, Stage and Pipeline, considering that different team can work with the pipelines, not not every of them needs to see that Playbooks.
  2. We also would like to see the possibillity to set the permission on who can see and use the Playbook by teams, not only Hubspot Roles or “specific employee”. That would also remove the noise for the people who don’t need it.
  3. Also tottaly agree with conditional logic in Playbooks, requirement before moving to stage.

Thanks!

Hi everyone!
This idea’s status has changed from ‘Being Reviewed’ to ‘Idea Submitted’. This change is due to our improvement project to update our Ideas Forum statuses in order to provide better transparency into how we are listening to your feedback.

“Idea Submitted” means that our product teams are aware of this feedback and are monitoring the need for this feature alongside other inputs that determine their priorities & roadmap.

For more details about the statuses we use on the Ideas Forum & what they mean, you can read this community post here.

Empty

Hey @WinnieHien - is there any update on this? Is the playbook data export on the horizon?

Hi all, thanks for continuing to share the feedback here. I spoke to several folks during our exploration for the Process Guides beta, and a lot of the feedback here influenced what we prioritized and built in that beta. We did sunset the beta in January 2026, and we’re not actively planning to work on these features right now so I’m moving this to Not Currently Planned. Thank you to folks that chatted with us when we were collecting customer feedback, and if this is still important to you please continue to upvote and leave comments. It’s a rich source of feedback for us when we circle back to working on the features again. Best, Winnie