CloudQR Software Usage Guide

Transcription

1 CloudQR Software Usage Guide 1 Document Release 17/09/ Document Tracking Version ID User Changed By Dated Comments 1 David Morrison 18/01/2014 Initial draft created. 2 Thomas Morrison 27/01/2014 Initial draft reviewed. 3 David Morrison 11/02/2014 Added new functionality documentation see section & David Morrison 14/03/2014 CloudQR Release 5 David Morrison 17/09/2014 CloudQR 2.1 Release

2 Table of Contents.1 - Document Tracking Introduction Software Installation Requirements Ticketing Disabling a ticket Reactivate a ticket New Ticket Stunning Pie Chart HLO Report Events Event Ticket Designer Adding a new Event View Orders Deleting an Event What happens to the tickets? Manage s Manage Automated s Disable s Enable s Customize s Variables Triggers Purchase Update Cancelled Disable Active Delete Complete Refund Scanner Identifying a valid ticket Identifying an Invalid Ticket Account Settings Auto Archive From Pagination Row Limit Theme Shopping Cart Refunding a payment Rules to allow automatic setup

3 Introduction CloudQR was developed by MorriGroup LTD, a small family run IT Business founded in January 2013 by Thomas and David Morrison. Congratulations on purchasing CloudQR. You are now in possession of one of the most advanced digital event ticketing system. Your software is both flexible and highly adaptable and it provides you with everything you need to create digital tickets for events that you host. It can help small software businesses grow into large ones, and it automates a very important part of the process Software Installation 2.1 Requirements You will need a web-cam and laptop/pc to check tickets in.

4 Ticketing Whenever you login to the system you will always be presented with the ticketing screen, which looks like this: There are two tabs giving access to each part of the ticketing module. The tickets tab lets you see a list of all tickets that have been setup automatically via the built-in PayPal shopping or entered manually to the system Disabling a ticket A ticket can be disabled by clicking the green button marked Active from the above screenshot. When you do this, the button will turn grey and read Disabled Reactivate a ticket A ticket can be re-activated by clicking the grey Disabled button. When you do this it goes green again and reads Active You can also edit and delete tickets using the icons situated under the Actions header from the screenshot above. To view a ticket simply click the little eye icon and the ticket will be launched in another window.

5 5 3.1 New Ticket Whenever you need to manually create a new ticket you can click the New Ticket tab and the following page will appear: On this page you can enter information for the new ticket you are creating. The only mandatory fields are the customer s name, address and the event on which the ticket will be issued to, the rest of the information such as ticket type and ticket expiry date can be pulled from an event s configuration. This will work if they are left blank, however should you wish to override the events configuration you should fill out all available fields. For example, an event is configured with a default ticket type of standard, but the ticket type for the new ticketing being created is VIP, you would set the ticket type on this screen to VIP. The only field that would rely on the event configuration would be the expiry date this would get set as the event date.

6 3.2 Stunning Pie Chart CloudQR was released with a stunning 3D pie chart that shows the amount of tickets issued per event. 6 You can click on sections to expand them out further. 3.3 HLO Report This report stands for High level overview and shows details of how many tickets an event can, a count of all tickets per status and a total of all tickets sold.

7 Events The event manager shows you a complete list of all the events that you have setup within the software. You can see at a glance, the event name, the date of the event, how much it costs, what currency it is in, how many tickets you can sell, if PayPal is active and the date of when it was created. You can also edit or delete an event using the icons located under the actions header. By editing an event, it will update all associated tickets with the event date entered this ensures all underlying tickets are updated. A ticket update trigger would also be sent to the customer, unless it was disabled. For example, event A was originally set up with the event date of but was changed to all of the tickets associated with event A would automatically be updated to contain this new date. 4.1 Event Ticket Designer Warning this feature should be used by advanced HTML users.

8 You can edit the ticket design associated per event by clicking the highlighted icon below. 8 When you click on this icon the HTML designer window will open in a new window which will load the default ticket type that you will be able to edit. There are a list of variables and a definition of what they return if used. These can help build a unique ticket design. Once you have completed the design of your ticket, press save so that the design can be committed back to the database. We recommended testing the new design by adding a new ticket and viewing it (Section 3.1) before going live.

9 4.2 Adding a new Event When adding a new event, you are presented with the below screen, all fields are mandatory as tickets may rely on this information, see section 3.0 for more information. You need to enter an event code and full name, the event s price, the maximum number of tickets to sell, date of the event, the default ticket type and whether it should be made available for purchase through the shopping cart 9 You also need to enter a currency using the correct international currency code (eg: US Dollars should be entered as USD and not simply as $. Likewise Euro is entered as EUR and British pounds as GBP and not ). Next, you need to enter your PayPal address to which payments should be sent on checkout. Whenever a customer pays using the shopping cart and PayPal; there ticket is automatically created and a link is ed to them. By setting the customer name and validation it will ensure the scanner returns additional information that you can use to verify customers upon a successful scan result. See Section 6.1

10 4.3 View Orders This tab shows you a list of all orders made using your shopping cart. You can also view transactions that have been refunded and those that have been charged back. 10 Whenever you make a refund to a customer there ticket will automatically be disabled, although you can re-activate it again if required. See Section You can also edit the ticket associated with an order by choosing the white pencil icon on the right hand side. 4.4 Deleting an Event Whenever you delete an event, there is no notification or rollback. Once it has gone it has gone, although MorriGroup support will be able to help you retrieve all your data back, we perform daily backups to make this process easier What happens to the tickets? Whenever you choose to delete an event, all tickets under that event have their status updated to cancelled. You will see them on the front screen but their status will show as cancelled, the event is also updated to a system default that holds all deleted event tickets. An example is below;

11 Manage s CloudQR communicates with customers throughout the full event life cycle. This is configured and maintained within this screen. When you launch the screen you will always be presented with the newsletter. This allows you to send an ad-hoc to a group of customers. You can use the variables within section 5.3 when sending .

12 5.1 Manage Automated s This section allows you to manage and update the templates sent when a ticket reaches a specific trigger, the triggers are defined in section Disable s You can disable triggers from being sent by pressing the green tick under the status header. The status icon will turn red and this will ensure whenever a ticket reaches the trigger an will not be sent Enable s You can re-enable triggers, simply click on the Red Cross icon, which will turn it back to a green tick. Whenever a ticket reaches the trigger an will then be sent.

13 Customize s You can edit s by clicking on the icon under the edit header. The below screen will appear, where you will be able to update the subject and message of the Variables The below variables allow you to edit the templates to suit your needs. 1. #event# a. This will map to the event the ticket is set to. 2. #customer# a. This will map to the customer name of the ticket. 3. #ticket_url# a. This will map to the URL of which the customer will receive their ticket. 4. #ticket_type# a. Returns the type of ticket the customer holds. 5. #event_date# a. Returns the date of the event. 6. #customer_ # a. Returns the customers address. 7. #event_prce# a. Returns the current price of the event. 8. #currency# a. Returns the event currency code.

14 5.4 Triggers triggers are controls that the system will use and identify which to send. A ticket may reach one of the triggers throughout its cycle. The trigger definitions are listed below, but they will only be sent if the trigger is active Purchase This trigger sends an to the customer, whenever you manually create a ticket or an order is placed using the PayPal Shopping cart. Section Update This trigger will send an to the customer when you edit a ticket Cancelled This trigger will send an to the customer, when the status of their ticket is set to cancelled. See section Disable This trigger will send an to the customer when the status of their ticket is set to disabled. see section Active This trigger will send an to the customer when the status of their ticket is set to active. See section Delete This trigger will send an to the customer when their ticket is deleted Complete This trigger will send an to the customer when their ticket completes. See section Refund This trigger will send an to the customer if the PayPal transaction id associated with the ticket is refunded. 14

15 Scanner The scanner allows you to check tickets in. To start scanning you first need to choose an event. You should select from the drop down list and select the step 2 button, when the scanner loads you need to allow flash access to your web cam.

16 6.1 Identifying a valid ticket If a ticket is valid, the Scanned results will show here. text is replaced with a green header saying ticket approved. 6.2 Identifying an Invalid Ticket If a ticket is invalid, the Scanned results will show here. text is replaced with a red header saying ticket declined with a small description as to why Account Settings This tab allows you to modify the system settings Auto Archive Auto archive was introduced in version 3 of CloudQR, it will automatically move all tickets to another table the day after any event s date. This keeps the system clean and tidy for current or live and upcoming events. The data still exists but is no longer reportable From The from setting is utilized when sending s to your customers, when set the value is passed to the function which sends all from it Pagination Row Limit This setting controls the number of rows returned per page Theme This setting allows you to control which color you wish the application to be in. The themes available are: Default Blue Red Lime Hot Pink Purple Silver Orange

17 Shopping Cart CloudQR is integrated with PayPal, and has its own shopping cart that allows your customers to visit. You may visit it to integrate your website to it once you are logged in by clicking the view public cart link. A list of all events that have been enabled to purchase through paypal (see section 4.1). The customer can click continue on their selected event to see a small overview of the price etc. When they press continue the following screen is shown. The customer can select multiple tickets from this screen, and when they have selected the amount of tickets they wish to purchase, the cart is automatically updated. The overall price payable is also automatically carried over to PayPal so that the customer makes 1 payment for many tickets. Once the customer successfully pays through PayPal all tickets are automatically created, and they are then redirected to a checkout complete page.

18 Refunding a payment When you refund a payment via PayPal all the tickets associated with the PayPal transaction ID are cancelled. And an Refund trigger is sent. See section Rules to allow automatic setup The following rules are required from the customer to enable a smooth transaction and so that they receive their ticket automatically. The first rule is 1. The customer must have a valid PayPal account (Fraud Prevention). 2. The customer must pay to the event s address (Tamper check). 3. The payment amount must be equal to or greater than the events price (Fraud Prevention). 4. The payment status must be complete (Ensures all funds are cleared before creating any ticket).