We’re looking to implement Playbooks as a way to support new employees and deliver a more consistent client experience. One of the ways we would like to do this is by using Playbooks to outline different types of calls, like training sessions, for instance. However, we’ve discovered an issue when attempting to use a single Playbook (i.e. “Training Session”) on the same Contact record multiple times.
For context - when a customer gets started with our service, they receive custom, one-on-one training sessions with their success manager. These sessions occur over a number of weeks and follow the same general outline, although the specific topics covered vary, of course. We would like to have a Playbook that could serve as a general guide through any given training session, however we’re finding that once the Playbook has been used for the Contact once, the info entered persists when we return to the Contact and attempt to use the Playbook again.
I’ve included a couple of screenshots for reference.
First, logged this training session
First, you can see I’ve successfully logged a training session about “how to create an Estimate.”
Now, I would like to use the Playbook again to log a training session about importing Contacts, but when I open the Playbook, all of the data from my “how to create an Estimate” call is still there!
Previously entered notes do not clear from Playbook
I was able to determine that you can delete/override the persistent data and enter new info, and this does save as a new/separate log to the Contact record. However, that’s not clear and I believe would be very confusing/disorienting for less seasoned HubSpot users.
In fact, we actually considered implementing Playbooks months ago until we ran into this very issue. It caused us to entirely abandon our exploration of Playbooks at that time because we didn’t realize that there was any way to use the Playbook more than once per record - and that was totally opposite of the functionality we needed.
I returned today in hopes that it had been updated…I want this to work so badly for our team, so I invested the extra time in really testing the functionality and was surprised to see how strangely it performs. Seems like a major glitch - or am I just missing something?


