Playbook Actions - Mark Done ✅ / Disqualify ❌
Streamline lead management with playbook feedback actions.
There are two out of the box actions that come in your Pocus setup.Mark Done and Mark Disqualified, are essential components of the lead management process within Playbooks. These actions, available exclusively in the Inbox and Playbook Overview pages, facilitate efficient lead handling by removing them from the playbook and implementing a cooldown period to prevent immediate re-qualification. Here's a breakdown of their functionalities:
How do these actions work?
There are two actions that come out of the box in Pocus––Mark Done and Mark Disqualified. Both of these are used as a feedback loop for leads that have been surfaced in Playbooks and are therefore only available in the Inbox and Playbook Overview pages.
When an end user clicks on one of these it immediately removes the record from that playbook for all users across the workspace and puts a cooldown on the record so that it can't re-qualify for a set period of time.
Mark Done
Use this to indicate that you have taken action on the record. You've reached out the lead, you've updated the required fields, etc. Whether you did that behavior in Pocus or a 3rd party tool.
Playbook admin's can set certain actions in the inbox (e.g., enroll in sequence) to automatically count as mark done. This way when the action succeeds the entry gets removed from the inbox without the rep having to click multiple buttons.
Mark Disqualify
See a lead that isn’t qualified? Click the X to disqualify. This removes the lead from the playbook for the whole workspace for the set duration just like Mark Done.
Use the dropdown arrow to provide additional reasoning behind the disqualification. Clicking the X sets the disqualification reason to Default, clicking a dropdown item marks the reason as whatever is selecting, and clicking other allows you to type a custom input.
This feedback is incredibly helpful to workspace admin as they make iterations on playbooks.
Customizing Settings on Mark Done / Disqualify
There are two custom settings for these actions that are set within each playbook by admins, which means that the behavior can vary from playbook to playbook.
- Duration: For how long should the cooldown last? Pocus will wait until that record qualifies again and the cooldown duration has passed to resurface that record in that playbook.
- Cross-playbook: Should marking done in one playbook mark that same record done across the workspace goal? When enabled, clicking Mark Done on
Acme IncinPlaybook 1will also removeAcme IncfromPlaybook 2
How can I see what I've marked done or disqualified?
Action History
If you quickly want to see what you did and undo any actions, you can open up your action history drawer by clicking on the toast that appears in your left sidebar. If you miss the toast, no stress, open your user menu and navigate to action history drawer from there.
Playbook Overview
Visit the playbook overview page for a given playbook. On this page there are two tabs, one for those that have been marked done, one for those that have been disqualified. These are slightly different than action history in that they let you see records you own that may have been marked done by another rep (i.e., if you share a book). This lets you sort by when it was actioned, by who, and the disqualification reason.
Mark Done/Disqualify actions can also be undone from these tabs.
Common Questions
Q: Why can't I mark done on a list?
- A: Mark Done actions are designed for actively surfaced leads in the Inbox. Lists function differently and are more for ad-hoc discovery, hence there's no concept of marking them done. Use the snooze action to hide items in a list temporarily.
Q: I only want to mark it done for myself.
- A: Utilize the snooze action to hide records individually for personal use. Mark Dones affect the entire workspace.
Q: Can I sync the disqualification reasons to a 3rd party tool?.
- A: The report on Playbook Overview is downloadable for those with CSV download permissions. For those with data share access, both actions are considered suppressions, with "Mark Done" and "Mark Disqualify" categorized accordingly. The disqualification reason is recorded as metadata.
Q: Can I customize disqualification reasons?
- A: When selecting a disqualification reason, reps can select “Other” and write in a custom disqualification reason. The ability to configure custom disqualification reasons coming soon!
Updated 11 months ago