Hi all! Just realized that storing playbook answers directly into properties requires an upgrade. I know this might be a bit of a bold question—but are there any clever workarounds if upgrading isn’t an option?
I’m still getting familiar with playbooks, so I’m also not sure where the data goes if it’s not mapped to a property. Any tips are appreciated!
If you have access to workflows, here’s a pretty good workaround! In this example I set the trigger to be when a lead object is created and associated with a contact, a note is created with predetermined text. It isn’t great for reporting but this should accomplish your immediate goal.
To map your properties, you can customize the object record to include the properties for the data you’d like to collect and fill it in on the left side of the object record while on a call.
It’s not the most perfect solution, but it should be a solid workaround if upgrading isn’t an option. Let me know if this works!
I totally get it — yep, storing Playbook answers in properties is a Pro/Enterprise feature. On Starter or Free, the answers just live in a note on the record. You can see them, but you can’t use them in reports or workflows.
Workarounds?
Not many native ones, but you could:
Manually copy key answers into properties after the call
Use an internal form instead of a playbook
(If you have Ops Hub) use custom code to pull from note content