|
A deal journey represents the sequence of sales stages that must be completed to close a deal. Each sales stage consists of a sequence of steps that must be completed to progress to the next stage. Deal journeys are depicted by sales pipelines, which can be tailored to the needs of a company.
For example, sales reps at an audio equipment company may use separate pipelines to sell home theatre systems and loudspeakers.
A deal Playbook allows you to define the selling process for a specific pipeline. Each template consists of a sequence of playbook tasks that sales reps must complete in each sales stage. You can add the following types of activities as playbook tasks.
Vtiger CRM creates a Playbook when a new pipeline is created by you. The Playbook has all the sales stages present in the pipeline. You can then add playbook tasks to the template.
Go to Main Menu > Sales > Playbooks to view all the Playbooks. Click the Related Deals tab on the top to see all the deals related to the pipeline you select.
Follow these steps to create a Playbook and add playbook tasks:
|
Certain playbook tasks are set up in a sequence. If a task is not completed, then the others following it in the sequence will not start. In such a case, you can set up a dependency between the tasks.
For example, a quote cannot be sent for e-signing without being approved by the sales manager.
|
Follow these steps to add a task dependency:
|
Task delays represent the time lag between two tasks. For instance, you can send a follow-up email to a customer one day after a demo meeting is held.
You can set up a delay for a task, based on either its parent task or the entry time of the current sales stage.
|
Follow these steps to add a delay:
|
In the case where a playbook task need not be performed, you can skip it.
Follow these steps to skip a playbook task:
Every Playbook is associated with a pipeline. When a pipeline is used by a deal, the Playbook associated with the pipeline automatically gets attached to the deal. Changes made to a Playbook are reflected in the deals associated with it.
|
The default start date and time of all the playbook tasks in a sales stage are set to the date and time when a deal enters the sales stage. However, the start date and start time can vary in the following two cases:
Case 1 - The task does not depend on any other task and a task delay is not specified. In this case, the start date and start time are set to the date and time when the deal entered the sales stage.
Case 2 - The task depends on another task. In this case, the start date and start time depend on the completion date of the parent task. When a delay is specified on a task, then it’s start date depends on the completion of the parent task and the delay.
|
The default duration of playbook tasks is one day (depending on the business hours). You can change the duration by manually changing the end date. You can change the end date from the task record under Main Menu > Essentials > Tasks.