Bookings Workflow
This is a configuration page for the Bookings. If you wish to configure the layout of the Bookings system, please refer to Bookings Layout.
Your organisation will have its own sales/booking process, procedures and structure, and the Bookings Workflow configuration lets you create these processes, procedures and structures through:
- Stages, which represent the progression of the Booking
- Steps, which are the processes related to the Stages
- Transitions, which determine the relationship between Steps
- Entry & Follow Ons, which define which Step an Booking should start on, and up-sell Bookings
Stages, Steps and Transitions Illustrated
Stages
Stages represent the phases of progression of an Booking. These are high level categories that show up in high level reporting, like the Sales Funnel diagram in the Sales Pipeline. Think of a Stage as the word you’d use to describe to an outsider the sales process it’s concerned with. Some common stages are terms like Proposed or Reconsider .
Stages in the Bookings System have a Status of either ‘Open’, ‘Archived’, ‘Lost’ or ‘Won’
The naming of Stages is entirely your own choice, whatever is suitable for your organisation and workflow ;however, their status must reflect either Open or Archived, Lost or Won.
To add a Stage:
- Make sure you’re in the Stages tab (if you’re not already)
- Click
- Name your Stage (this will be displayed on your Sales Pipeline)
- Select the Status for this Stage
- Click
- Click
to save the overall configuration
Open Stages
Open Stages are the points in which the Booking is active and can be won. At a high-level, Open Bookings are those which you’re working on and should be concerned with at present, because they can be ‘Won’. Bookings that are in the Open Stage will feature as a statistic in the ‘funnel’ diagram when you load the Sales Pipeline (the main page of the Bookings).
Drag and drop the Open Stages in the preferred order you want the funnel to display them.
Reorder your ‘Open’ Stages to reflect your Sales Funnel on the Sales Pipeline Page
Other Stages
Stages that are not Open can either be:
- Archived - Booking has not been won, but is not dead, it may be revisited at a later date
- Lost - Booking is dead, and there’s no further action that can be taken
- Won - Booking has been successful
Once a Stage is no longer Open , it won’t feature as a statistic on the funnel diagram on the Sales Pipeline as there’s no further action to be taken.
Steps
Within Stages there are Steps, which are more detailed processes than Stages, and are typically used by the sales team to internally enforce their own procedures and provide more transparency. The Steps represent the various actions that a sale or booking may take along its path to completion. For example, the Steps Proposal Sent, Proposal Accepted, and Payment Details Confirmed might all be part of the Proposed stage. From a high level perspective, knowing the Proposed Stage is enough, but the Steps within this Stage allow the sales team to have a detailed view. See how Steps are illustrated in the Workflow.
As such, each Step must have a Stage assigned to it.
To create a Step:
- Make sure you’re in the Stages tab (if you’re not already)
- Name your Step: this will be the name of the processes as displayed on your Workflow
- Select which Stage this Step belongs to
- Select which Attributes you wish for this Step to display for every Booking record
- Click
- Click
to save the overall configuration
Creating a Step
Assigning Attributes will determine what Attributes, as defined and laid out in the Bookings Layout, will appear for this Step in the Bookings System, i.e. what fields will appear.
How Attributes in Steps work and are displayed
Transitions
Once the Stages and Steps have been defined, you’ll have the building blocks of your sales process. Now you need to link them together, which is what Transitions are for. Transitions create relationships between Steps, determining the criteria in order to progress through the Booking.
In the Workflow, Transitions are displayed by straight line connections between Steps, illustrating they have a connection with each other. The current Step, Booking, is in green, and current Steps it can make a Transition to are highlighted by green Transition lines. Using the mouse pointer to hover over a Step, you can see the Transitions between those Steps with the blue lines. Steps that cannot be progressed to from the current Step are greyed out.
Steps are connected through Transitions: blue lines are only mouse-over operations
Note:
Each Transition determines the relationship between two Steps only; however, multiple Transitions may be configured for each Step. This can be seen in the example above: Proposed has 3 Transitions which lead from it to the Steps Won, Lost and Archived.
To create a Transition:
- Make sure you’re in the Transitions tab (if you’re not already)
- Click
- Name your Transition
- Select the From Step (from where the Transition starts)
- Select the To Step (to where the Transition ends)
- Select the Required Attributes , to enforce information recording
- Select the appropriate Triggers for creating entities
- Click
- Click
to save the overall configuration
Creating Transitions between Steps
Required Attributes
Attributes checked here indicate that these fields need to be satisfied before this Transition can be actioned, e.g. if you select First Name to be an Attribute, then the Transition won’t let the User progress to the next Step unless the First Name field is filled out. The system will feedback an ‘Incomplete’ message and highlight which field requires attention - in this case, the First Name field. This must be resolved before the Booking record can be progressed (with this Transition) and saved.
This is useful if certain information must be recorded before the next Step can be realised, thus enforcing your organisation’s workflow processes.
Required attributes illustrated, using ‘value’ as an example
Triggers
Triggers (not to be confused with Communication Triggers) can be activated through Transitions to automate the creation of appropriate records in your database using the information already populated in your Booking’s record. This saves you time and eliminates errors introduced from manually inputting the details yourself. For example, early Transitions in the workflow can automatically set up an Account for the business and a Contact for it, and later Transitions (like when the Booking has been won) can create a registration and an appropriate Invoice for the Events the Booking had Interests in. This is configurable by you so that you can dictate where and what in your workflow you want to populate your database with the appropriate details.
Check the boxes to activate any of the Triggers:
Trigger | Behaviour |
---|---|
Create Account | Create a new Account in your database using the record from the Bookings System. |
Create Contact | Create a new Contact in your database using the record from the Bookings System. |
Create Invoice | Create a new Invoice in your database, generated from the Interests and Quotations of the Booking. Once this Transition goes through, the invoice generated will appear in the Details section (see screenshot below). |
Create Registration | Create a new registration record in your database, generated from the Interests for all the assigned students, and Quotations of the Bookings. Once this Transition goes through, the registration generated will appear in the Details section (see screenshot below). |
Create Token Issue | Create a new issue of Training Tokens in your database, generated from the Interests. You can check issued tokens in the Training Tokens tab of the Account screen. |
Registration and Invoice Transition Triggers: automatically generated records will appear in the Details section
Communication Triggers
Communication Triggers can be set up for your Bookings to send an email or SMS when a specific transition is done. Please refer to this page for more information.
Entry & Follow Ons
Entry
As your Workflow expands, you may find that you wish to start your Bookings on another Step. This first Step, from where all Bookings will start from, is called the Entry.
To designate the Entry:
- Make sure you’re in the Entry & Follow Ons tab (if you’re not already)
- Click ★ New Booking or ★ New Booking - Existing Account if the Booking refers to an existing Account (see below)
- [Optional] Rename the Entry: this is for your reference only
- Select the From Step from which all new Bookings will start
- Click
- Click
to save the overall configuration
All new Bookings will now start from this designated Step.
Difference between ★ New Booking set to ‘Lead’ and ‘Booking’
★New Booking - Existing Account is used for Bookings with existing accounts that are already on your CRM, e.g. you may have an Account and Contact set up already. You may wish to have this set to a Step later in the workflow than ★New Booking . For example, earlier Transitions may be configured to create CRM records, so you won’t need to do this again to avoid potential duplication.
Follow On
Perhaps your sales representative has managed to up-sell more Events, or the prospect has come back to you wishing to add more students as an Interest. In this situation, do you create a new Booking and re-enter all the details again? There’s no need, as this is what the Follow On feature is for!
To create a Follow On, just click , and give it an intuitive name, e.g. perhaps the Step that it will start on, or a representative’s code so they know which one to use. Then, define which Step this sub-Booking should start from.
Once a Follow On has been created, the button will appear on your record on the Bookings System. All Follow Ons created will appear as such on the parent or child Booking, making sure that you can keep track of them.
The Follow On button will appear on the Bookings System once Follow Ons have been created
To use the Follow On, just click on on your Bookings record and click on the Follow Up you wish. This will start a new Booking, starting on the Step defined earlier, prompting you to name the new Booking. The Bookings System will identify this Booking as a Follow On (child) to the parent Booking.
Follow Ons are confirmed by a message and start on the Step previously defined
Similarly, the parent Booking will display its Follow On (child) Bookings when viewed, so that you can always refer to them or know that they are there.
Comments
0 comments
Article is closed for comments.