Playbook
The Playbook enables you to create Events with (or without) Stage Auto-Progression, Events Dependencies and Checklist items.
Events are shown in the Event List view, in Gantt view and in the Kanban view.
Read the entire Playbook section carefully before you start to create Events for your template.
Playbook Layout & Navigation
Overview
Playbook Information
Event Count - Number of Events in the Playbook
Process Length - Duration of Playbook in Days
Mutual Plan - Indicates if a Mutual Plan is enabled
Event Contacts - Indicates if Event Contacts is enabled
Staging - Indicates if Staging is enabled and to which Sales Process the Playbook is associated
Settings - Opens modal to adjust Playbook Settings
Gantt - Switches to Gantt view
+ Event - Create a new Event
Sales Process Stages -
Subject - Event Name
Stage - Stage to which the Event is associated (If Staging is enabled)
Mutual - Indicates if the Event is Mutual
Party - Party responsible for the Event
Starts In - # of days from Day 0 the Event starts
Duration - Duration of the Event
Checklist Items - # of Checklist Items
Dependencies - # of Events on which this Stage is dependent
Event Sync Settings - Opens Event Sync Settings Modal
Delete - Deletes the Event
Playbook Settings
Playbook settings enable you to create Events with or without specific Sales Stages.
If you want to create Events without inclusion in a relevant sales stage, you can do so without any additional settings.
If you want to create Events within a specific Sales Stage, enable the Stage Auto-Progression, select Event Behavior and Sales Process.
Stage Auto-Progression Settings
Set an Event for a Stage specified in the selected Sales Process.
Set an Event behavior that affects the closing of Sales Stage.
Go to Playbook tab > click the Settings button
Toggle the button to enable Staging
Select Event Behavior (See descriptions of the Event Behavior below)
Select Sales Process
Save
Event Behavior
Setting Event Behavior can affect the User’s ability to advance through the Sales Stages in the Sales Process.
Block if Event is required - Playbook Events are set as required. Users will be prevented from moving to the next Stage until the required Event is set to Completed.
If the Event is in any status other than ‘Completed’, Users will be prevented from moving to the next Stage.
Example: Even if all Checklist items are ticked, but the Event is still ‘In Progress’, (or in any status other than Completed) Users will be prevented from moving to the next Stage.
Image below showing different Event Statuses: Completed (Green), In Progress (Yellow), Not Started (Blue)
Auto-Complete open Event - Indicates the Event is set as not required. Users can move to the next Stage even if an Event is not Completed
Block if Event is required, otherwise Auto-Complete Event - This setting allows for a combination of the 2 settings above.
If there is a required Event, Users will be blocked from moving to the next Stage until the Event is set to Completed.
If the Event is not required to move to the next Stage, Users are permitted to move to the next Stage regardless of the Event status.
Sales Process
The selected Sales Process is displayed as Sales Stages in the Playbook. Sales Stages contain Events.
A Sales Process must be active and selected from the Template list to create a ClosePlan.
The Sales Process contains Record Types. If the Opportunity has a different Record Type than the selected Sales Process in your Template, you will be prevented from uploading the template into the Opportunity until you change the Record Type on the Opportunity.
ClosePlan will allow Users to choose a Template only when the Sales Process is the same as on the Opportunity or when the Template Stage Auto-Progression settings are inactive on the Template.
To change the Record Type on the Opportunity > click the button right up > select Change Record Type > select the Record Type set for the Sales Process you have selected in the template > click Next and Save.
NOTE:
Event behavior also affects the dependency settings on other events and the checklist items settings.
Checklist items are set when you create or edit Events.
Dependencies are set only when the Event is created and in edit mode.
If a Dependency and/or a Checklist are set as required, the User will be prevented from closing the Event and/or the Stage until completed.
If an Event contains required Checklist items, the user must first complete the Checklist items before closing the Event.
If an Event contains required Checklist items, and also contains a required dependency on the another Event, the user must complete the Checklist first,
then the dependent Event. Only then can the mandatory event be closed by the User.
Example:
Create Events
New Event Template contain 3 tabs: Details, Checklist and Files.
NOTE: Previously created Events that are in edit mode also contain a Dependency tab to set dependencies on other events. Dependencies can also be set from Gantt view.
To create an Event, click on the button.
Details tab
In the Details tab, enter information about the Event you are creating.
Subject: Enter the Event Name in Subject field
Type: Select Type (if you created one in Event Types setting)
Starts In: Enter Starts In to indicate the # of days in which this Event will start
Duration: Enter Duration in # of days of the Event
If you enabled Stage Auto-Progression:
Stage: Select Stage
Require to complete Stage: On the basis of playbook events behavior settings, mark whether the event is required to complete the stage
Event Description: Optional description
Event Goal: Optional text that can describe the Goal
Code - Code is used for integration purposes. Assign a code if you want to reference the deployed event inside Process Builder. E.g. show event status in a Report
Checklist tab
Checklist items are tasks that Users complete. If you mark a checklist item as required, the User must complete the task before the event can be closed.
Note: Users are able to Add / Edit / Delete Checklists in Playbook.
Click
Enter the subject of checklist item
If required, tick the REQ. box
Click the
button and if needed, continue creating checklist items
Individual tasks can be edited, deleted or reordered
To reorder tasks, simply drag individual tasks to the desired position
Save the checklist
will delete the Event.
Files tab
Attach specific files or links to individual sales events.
To add a Link, click
Tao add a File, click
Click Save
Opportunity Fields tab
Sets data from opportunity fields that will be promoted to the Event = ability to link opportunity fields with playbook events.
Available Field Types: Picklist, Multi-Picklist, Lookup, Date, Date Time, Checkbox, Text, Long Text, URL, Phone, Email, Currency, Number, Percent. These fields allow to select the correct custom field or some of standards field from the Opportunity.
Some standard opportunity fields are eliminated from the selection = you will be not able to add these fields into the event opportunity fields.
Eliminated fields: Picklist - StageName, ForecastCategoryName
Text - Name
Checkbox - IsPrivate
Numbers / Currency / Percent - TotalOpportunityQuantity, Probability
Lookups - AccountId, RecordTypeId, CampaignId, Pricebook2Id, OwnerId, ContractId, TSPC__CPDeal__c
You can add max. 20 fields to each Event Opportunity Fields, or character limit. If is needed to include more fields then what app will allow, shorten API names for your fields so that more can fit in.
Click Add Field button
Select your data type field from the Opportunity and select the desired field
To add more fields click again Add Field button
To reorder fields click the Arrows buttons
To delete a field click the Remove button
Note: If you click red Delete button , you will delete the Event!
Example:
Setting in the event template
Result in the Playbook on the Opportunity
Dependency Settings
Set Events dependencies, where one event can be dependent on another event.
Dependencies can be set from the Edit Event Template view or from the Gantt view.
There are 2 types of Event dependencies:
Required = Event can be closed only after the Event upon which it is dependent is completed and closed.
Not Required = Event can be closed without completing or closing the Event upon which it is dependent.
Add dependency from the Event Template:
Click on the Event name to open the event
Go to Dependency tab and click on Add dependency
Select a target event and mark if the target event will be required as completed in order to complete this Event
Save
Add additional dependencies if needed and Save
Add dependency from the Gantt view:
Click the
button
Click the corner button of an Event, and drag the line to the start or end of the dependent event.
Note: Be aware of where you drag the dependency - it may affect the start or end of the event.
When you drop the dependency line, the new dependency window will appear allowing you to make the dependent event Required if needed.
Save
Change the start day or duration of the Event with set dependency:
Event dates and duration can be change direct from the Gantt.
If there are not dependecies, it will not influence another Events.
If there are dependecies, it will affect the dates of dependet Events.
Drag the event and move left or right to change the start day of the Event
Hover over event corner to see the arrow and extend or shorten the Event duration
Example:
Original setting
Event "Qualification" was moved to start on 9th day instead of 5th and it affected another dependet Events = were moved as well
Gantt View
The Gantt view lets you see created events in the Gantt before you deploy the template.
You can make changes (create, edit, delete event) and set event dependencies in the Gantt view.
Gantt Layout & Navigation
Toggle Sidebar - Toggles visibility of the Sidebar.
Switch view between days and months.
Scroll buttons - Scroll the Gantt area to Start, left, right or to the End
Export data as Excel, PDF, Image or MS Project
Add a new Event
Event Stage - click
to hide Events from view.
Dependency button - hover over the event corner > click the button and drag the dependency line to the desire event.
Event Bar - Double click to open the Event, hover over the event bar corner to extend or shorten the event bar, click 1x to move the event right or left
Not required dependency (grey)- to delete it click 2x on the dependency line and click Delete.
Required dependency (orange) - to delete it click 2x on the dependency line and click Delete.
Event Sync settings
Event Sync settings enable synchronization of data from the Playbook template with fields from the Opportunity or ClosePlan - specifically Event Status and Checklist progress.
Individual data can be propagated on the Opportunity layout or in the Reports.
Settings are made to the template from which you want to propagate data. If there are multiple active templates, you need to set up sync for each template from which data will be propagated.
To assign the sync, the custom fields on the Opportunity or ClosePlan Object need to be created. To propagate data to the Opportunity layout, the custom fields need to be created on the Opportunity Object.
Go to Templates > open the Template from which you want to propagate data.
Note: if there is more than 1 template activated, and would you like to have data from every active template, you must set the sync in each template.
Go to Playbook > click the Event Sync settings
icon
Target Object - select the object where you created the category fields (Opportunity or ClosePlan)
Summary Field - select to propagate Event Status and Checklist progress together (data type field "Text")
Status Field - select to propagate only Event Status (data type field "Text")
Checklist Progress % Field - select to propagate only checklist progress (data type field "Percent")
Save
Repeat steps to set sync for other events
Note: Event Status picklist found on CP:Event is a Custom Field Definition and is part of the managed package. Modifying the Status picklist can adversely affect the application, unless explicitly stated. In general, any field or picklist that can be modified is accessible through the ClosePlan Admin tab. If any changes are needed to the Status Picklist, please coordinate with Engineering by sending the request to Support@People.ai