Easy sales landing page with Coconut Tickets

Posted on

Customers select the tickets you have on sale when they arrive at your sales landing page. Coconut Tickets has a simple tool for creating easy sales landing pages.

The quickest way to create a sales landing page is to accept the default page proposed by Coconut Tickets. Alternatively if you want something more customized then you can edit the the copied default landing page.

Vendor pitch (B2B) default sales landing pages are not the same as default public ticket (B2C) sales landing pages. That is because there are fields specific to selling vendor pitches that we don’t want to show to public ticket customers and vice versa. However, the tool is the same and the principles behind the use of the tool are the same.

This tutorial will create a quick sales landing page for public tickets, at the end of the tutorial there will be an explanation of how this may differ for selling vendor pitches.

From the main menu find the “Sales” menu, click on it then from the drop down menu select the “Define ticket sales landing” option. This will display a page like the screenshot here.

easy sales landing builder empty page

For this example let’s assume that this is our first ticket sales landing page and that we will have to create a new sales landing page from the beginning. To do that we would click on the “New Design” button. Next we would give the sales page a meaningful name that we can refer to later on.

Notice that in the screen shot before we started a new design the panels titled “available design blocks” and “blocks to be displayed” were empty, when when we clicked on “New Design” Coconut Tickets automatically created a default sales landing design and those two panels were filled with blocks as per the screenshot below.

drag blocks to design your easy sales landing page

The right hand panel “Blocks to be displayed” contains the blocks of information that will be displayed on our sales landing page. The order of these blocks is also the order in which they will be displayed, therefore the first block displayed right at the top of the page will be the header banner with our event company branding, immediately under that will be the breadcrumbs showing the sales sequence, etc.

At this point we could simply choose to accept the default page as it is and make no changes. This would be the quickest way to create our sales landing page. If that is good enough for you at this stage then click the “next button” and you will be taken to the event linking page which will be explained at the bottom of this tutorial.

Alternatively, for the next few paragraphs I will provide an overview of what is in the default landing page and how you can customize it.

When the sales landing page is displayed to your customers, every information block will be filled with information you already provided. For example, the header banner information comes from the logo you entered on the business profile page and the event description is the description you entered when you defined the event. Therefore the content of these blocks is dynamic and each will be fill intelligently when the page is displayed.

You may want to look through the list of available blocks and decide if there is anything in there that is really important for your sales landing page. If there is then you can drag that block from the available pane and into the display pane. Once in the display pane you can move it up or down until you have it in the order you want to display it.

Similarly if there are blocks in the display pane that you don’t want your customers to see then you can drag those blocks to the available blocks pane and they will no longer be displayed.

It is also possible to change the formatting of the whole page or the formatting of one block, these will be the subject of a separate tutorial.

Let us assume that we have made the changes we wanted, then we can click “Next” and move on to the next page which looks like the screenshot below.

dialog to define which events use this easy sales landing page

This next page allows us to define which events will use this sales landing page. That is to say that as many of our events as we want can use the same sales landing page, we don’t need to create a new design each time.

The events field in this example is empty, to get this sales landing page linked to our example “Darts” event we would click in the “Events” field and it will display a drop down list. Select the event you want to use this sales landing page and any selections you make will be displayed in the field. The screenshot below shows the result of our “Darts” example event having been selected.

Selecting a specific event to use the sales landing page

Next click “Save” and the new sales landing page for your event will be created and is ready for selling tickets.

When this example sales landing page is used for selling tickets for the example brand “Ticket Club” it looks like the screenshot below.

customer's view of the easy sales landing page

Notice how the blocks are displayed exactly in the order we saw when we accepted the default sales landing page: header banner at the top, then breadcrumbs, then the name of the event, then the date/address combination. These have all been filled automatically by Coconut Tickets.

To create a sales landing page for a vendor pitch, from the “Sales” menu select the option “Define vendor pitch sales page”. This loads the same sales landing tool that was used to create the sales landing page for the tickets, although when you create a new design and look at the blocks there will be some differences. For example, a vendor pitch sales landing page has a vendor description block and most importantly it doesn’t have a ticket quantity selection block but has a pitch selection block instead. Other than this the explanation above would be the same for vendor pitch landing pages.

 

For further information on the end to end sales process see Getting started with Coconut Tickets

Posted in: tutorial

Written by Clive.verrall

Leave a Reply

Your email address will not be published. Required fields are marked *

*