Bikubo offers you the possibility to integrate forms with or without payment gateways, so that an attendee to your event, after filling out the form and making the payment (if the event is paid), receives a Bikubo ticket/credential with QR/barcode that can be validated with our app.
You can see an example of the form you can create from your intranet in the following Test Form.
Through the intranet, with your username and password, you can register the form for your event, and add the different categories of tickets or credentials.
When you add a form for your event, keep in mind that you first add a ticket or credential category, and with that you already have the form available for your event. Later you can add the remaining categories, if you consider it appropriate.
To add a category to your event form, you must follow these steps: you must click on Menu => Events => Active => Title of the event in question => List of ticket categories / List of credential categories => Registration forms.
Below are the data that you can configure in the form.
-
Website name: the website url will have the format name-X-Y-html, where you can choose the name to include. Choose the name you consider appropriate and try not to change it for the rest of the configurations you make again for the form.
-
Header image: you can upload an image of your event poster if you consider it necessary, and indicate its dimensions in pixels of height and width. Later you can change or delete it if you see it necessary.
-
Informative text about the event: you have a text editor to indicate what you consider appropriate, which will be located below the header image (if you have uploaded a header image). In this text you can add images, links, tables,...
-
Sale price: For a price other than 0, the commission is shown below, and you must select whether the attendee is shown the final price and the commission separately, or a single price that includes the Bikubo commission in it.
-
For forms with payment, it is mandatory to indicate the event organizer, which will be shown in the terms and conditions that ticket buyers must accept. The buyer will be shown the checkbox to accept the privacy policy and legal conditions according to what the following link indicates. If you consider that this privacy policy and legal conditions do not adapt to your event, or you need to make some modifications, you can send an email to admin@bikubo.com indicating what you consider appropriate in this regard, and we will respond as soon as possible.
-
Maximum number of tickets allowed to add to the shopping cart: is the maximum number of tickets that the attendee can add to the shopping cart, adding all those added from the different ticket categories. Once this number is reached, the attendee will not be able to add more tickets to the cart.
-
Maximum total number of tickets allowed through this form: It is the maximum number of tickets to generate to attendees through the form for this category. Once this number is reached, if the user selects this category it will be shown as unavailable to attendees.
-
Maximum number of tickets allowed per purchase: It is the maximum number of tickets to add to the cart of this category from the dropdown (you can select from 1 to this number).
-
Initial sale date: corresponds to the first day enabled for the sale of the ticket/credential category you are configuring. Before this day, this category will not be shown in the form.
-
Maximum sale date: Corresponds to the last day of sale for the ticket/credential category you are configuring. After that day, this category will not be shown in the form.
-
Maximum time to complete the purchase (minutes): When an attendee selects one or more tickets from a category that includes a payment, they are temporarily reserving those tickets for themselves, to avoid an oversale of the number of tickets with respect to what was established above. Therefore, it is advisable to establish a sufficient period of time so that they can complete the payment, but not too excessive so that the temporary reservation leaves those tickets disabled for too long for sale, in case they finally do not choose to make the payment. 15 minutes may be enough, but it's your choice. After that time, the reserved tickets are released.
-
Password protect the form: When a form is password protected, when the attendee enters the form URL in the browser, the information associated with the event is not shown, but the access password is requested, so that if it is not correct, the ticket or credential categories are not shown to the attendee, nor the information associated with the event (image or informative text).
-
Generate access codes to the form: The codes allow you to control the number of data collections for the forms. So for example, if you create 100 codes with a value of 2 as the number of data collections per code, the attendee to the event, when selecting the ticket/credential category, for the form to be shown, must enter a valid code and that data has not been collected from that form a number of times equal to 2.
Once you have configured the form and clicked on save data, you can later modify the entered data. You will also be shown a URL that you can share for ticket/credential sales, and also a code in case you want to incorporate the form into a web page other than Bikubo's.
Click on the 'Advanced form editing' button to add different elements to the form. To do this, click on 'Add field', and you can add to the form short text fields, long text, dropdowns, single option, multiple options, dropdowns with multiple options, date or time fields, the option to add an image selector for credentials or cards, or add informative texts with or without images.
For each of the field types reflected above, you can select the label that accompanies the field, as well as specific values for each type of selected field to add.
You can also select the destination of the value entered by the attendee, so that if for example you select field 2, the values entered will be shown in the credential if when creating the credential category it includes showing field 2.
Each ticket or credential category has its own advanced configuration, but once you have configured a form for a type of category, for any active event you have, the other categories can use this previous configuration. To do this, on this advanced configuration screen, select the event, then the category to copy, and click on 'copy configuration'. After this action, the form is configured in the same way as the copied category was configured.