Below are the frequently asked questions we've received about the bikubo platform.
Yes, only a valid email address and a password are required.
Yes. With registration and validation of the confirmation email, you can access the intranet to view the services offered to users.
Yes, each registered user is given a number of tickets and credentials to test the bikubo.com platform. Certain services require contacting our support team to enable testing (for example printed tickets, sending tickets via SMS or WhatsApp, the use of cards, ...).
From each user's administration panel there is an option to purchase electronic tickets and credentials which will increase your balance and can be consumed for your events.
Within each user's intranet (administration panel) you can create different events that correspond to a concert, congress, course, party or session to be controlled.
Credentials allow adding variable fields on entries such as name and company, or variable images (photos, logos, ...) in addition to a variable QR code, while tickets only allow variable QR codes and numbering.
That is the main difference, plus some more advanced features like setting different control points and assigning access permissions by category or individually, or sending reminder mailings.
Tickets are usually more oriented toward concerts or festivals, and credentials for corporate events.
Ticket or credential categories are used so that the tickets or credentials generated from these categories share the same design, changing only the variable data, and also inherit the access permissions to control for the same event, and other functionalities.
It is each element generated through our platform that has been sent, generated or printed and that an attendee holds for an event. This ticket, once validated with our app, grants access to the control points it is authorized for, and the configured information will be displayed after scanning.
Electronic tickets are those that are generated individually as a PDF and may be sent by email. Printed tickets are those requested to bikubo for printing, and also those generated by creating a PDF of tickets.
Yes. You can upload different ticket designs for the same event and validate each type of ticket differently if you wish, for example to distinguish VIP tickets, stays, or schedules.
Numbered printed tickets produced by ordinary printers provide no fraud protection (forgery, duplicates), do not give instant information to the event organizer (for example, number of sales per distributor) nor allow instant control (ticket voiding, associated information - attendee name, email, ID).
Printed tickets can be scanned using the bikubo app by following these steps:
1) Tap the distributors button to access the distributors menu.
2) Tap to open the scanner; the device camera is activated.
3) Scan the QR/barcode.
4) If the ticket is valid, a web page is shown in the app to enter name/ID if requested by the administrator, and then tap the 'Activate sale' button.
The administrator or distributors, from their web control panel, can send the electronic ticket to the event attendee by email. After each sending, the ticket is recorded as sold and the statistics are shown to the administrator.
Printed tickets can be scanned by the distributor and assigned to a specific person (name and/or ID).
Electronic tickets, at the moment they are sent to the attendee, can have the attendee's details added (name and/or ID).
Additionally, bikubo allows the event administrator to modify attendee data if appropriate (for example at the request of the person concerned or by administrator necessity).
When a ticket is validated at the entrance, the previously entered information is displayed, so if the person holding the ticket does not match the recorded data, resale has likely occurred.
The system allows you to know the number of tickets validated at the entrance in real time, by ticket category, showing the number of tickets generated for each category and the total validated for each category.
In addition, each event has a web page that displays attendance data and the list of attendees instantly.
Yes. The system allows voiding a specific ticket so that when attempting to enter the event and validate the ticket a red message with the notice VOIDED will be displayed. We also allow reactivation of a voided ticket.
If you know the numeric series of tickets to be voided, enter the initial and final numbers in the corresponding intranet module (for example void from 20 to 35 of the General category). Then, when validating a ticket within that range at the event entrance, a red VOIDED message will appear. We also allow reactivation of voided tickets.
Electronic tickets sent to attendees do not need to be printed, as the app can read them on screens (attendees' phones or tablets).
You can use the alphanumeric locator. In any case, the owner of printed or electronic tickets must maintain their integrity at all times.
In the administration panel you can assign or remove tickets from each promoter/distributor. Each distributor, when they sell a printed ticket and scan it as indicated above, or when they send an electronic ticket to an attendee, sales are counted.
In case of fraud, those tickets can be deleted, and when validated at the event entrance a red VOIDED message will appear.
Yes. Electronic tickets are prepared to be printed on a standard A4 sheet if the attendee prefers to have them printed.
The organizer may decide not to validate electronic or printed tickets at event access. BIKUBO notes that authenticity cannot be verified if tickets are not validated with our app.
On the other hand, unvalidated tickets may remain valid while the event is still active in the administrator's intranet.
This is very unlikely, since validation is allowed online and also offline (without an internet connection or dependence on server availability). In such cases you can use the alphanumeric locator.
For this purpose, the event access control will have an alphabetically ordered list of the last 4 letters of all locators (they are masked for security reasons). This list can be used to confirm ticket authenticity.
Electronic tickets are used daily by many platforms (RAIL, Hotels, ...), and in our case they represent a near-zero probability of duplication.
Much lower than printing physical tickets. Check our pricing.
Assigning tickets to a distributor takes very little time: simply select the ticket category, the distributor and indicate the number of tickets to assign. Compared to traditional distribution methods, you'll notice significant efficiency gains.
We do not store ticket price data internally; the administrator can create a new ticket category with a different price and send tickets associated with that category when desired.
They can download the bikubo app, log in as an administrator and scan the ticket to display its associated information (name/ID if applicable, event details and sale date).
No, only the first scanned ticket at the entrance is accepted. If a second or subsequent ticket with the same QR/barcode is scanned, an error message indicating the ticket was previously validated will appear.
Yes, you can provide the app username and password to as many validators or mobile devices as needed, so multiple people can validate simultaneously. You can also create validator accounts with permissions limited to specific control points.
Yes. The app allows downloading tickets to the validation device (phone/tablet) when you have internet, then validating against the device's local DB when on site. If you need more information about offline operation, contact us via chat, email or phone.
No, each administrator/validator has their own username and password.
Yes. However, this requires contacting us via chat, email or phone so we can configure the event accordingly.
This is configurable. By default, successful validations show a green message displaying the name and/or ID if entered and any observations. Invalid ticket validations show a message on a red background explaining why the ticket is invalid, along with the history of failed validations.
Color, sound and duration can be customized per event. To change the configuration, contact us and we will adjust it to your needs.
It depends on the number of tickets to validate, but in all cases it is very small and should not be a problem.
Given current mobile device technology, scanning a QR code is much faster than reading a barcode, so bikubo clearly recommends QR codes. However, if you pair mobile devices with affordable Bluetooth barcode/QR gun scanners, reading speed is very fast with either system.
No, you can use mobile devices without gun scanners using the device camera. We also provide an app that supports pairing economical gun scanners (for example https://www.amazon.es/Eyoyo-Bluetooth-tel%C3%A9fono-Escaneador-Smartphone/dp/B08YQVNW7C/...) via Bluetooth, making reading faster and even usable in low light (laser gun scanner).
To pair this gun with an Android device (not supported with iOS), follow these steps:
1) Enable Bluetooth on your device.
2) Scan the codes indicated in the pairing tutorial of the purchased gun.
3) Open the bikuboBT app.
4) The gun will be paired and data read by the gun will be input into the app, allowing direct validation.
Yes, when you create a ticket/credential category you can define different control points, e.g. Door A, Door B and Door C. A validator selecting Door A will only validate tickets authorized for that door.
BIKUBO administrators can see, among other data, the following in their intranet:
1) Number of active events.
2) Number of active ticket categories.
3) Electronic tickets available.
4) Electronic tickets used.
5) Electronic tickets sent by distributors.
6) Printed tickets sold after being scanned by distributors.
7) Tickets validated at access.
8) Sales by date.
9) Sales by distributor, by date and ticket category.
10) Voided tickets.
11) Tickets sold and validated by distributor.
12) Tickets sold and not validated by distributor.
13) List of event attendees with email, validation date and name and/or ID.
Yes. When an event is no longer active and you want to prevent further ticket distribution and validation via the bikubo app but still retain its statistics, archiving the event is recommended.
In short, archiving an event results in:
Distributors can no longer distribute electronic tickets for the event, nor can the administrator.
If a ticket is validated in the app, it will show an error.
Event statistics remain available.
The attendee list remains available.
The event is removed from the active events list and appears under archived events.
The event is not shown in the app for validation.
Yes. If you want an event removed from both active and archived lists and no longer shown in your intranet, you can delete it.
In short, deleting an event results in:
Distributors can no longer distribute electronic tickets for the event, nor can the administrator.
If a ticket is validated in the app, it will show an error.
The event is removed from active and archived lists.
Event statistics, generated PDFs and the attendee list will no longer be available.
This operation cannot be undone, so be certain before performing it.
Yes. If you want a ticket category removed from the event categories list and no longer shown in your intranet, you can delete it.
In short, deleting a ticket category results in:
Distributors can no longer distribute electronic tickets for that category, nor can the administrator.
If a ticket from that category is validated in the app, it will show an error.
The category is removed from the ticket categories list.
Category statistics, generated PDFs and attendee lists will no longer be available.
This operation cannot be undone, so be certain before performing it.
If a user account is inactive (no access) for more than 1 year, it may be deleted.
1 year.
No. BIKUBO does not participate in organizing events and is not responsible for any circumstance associated with them. BIKUBO only provides a technological access control service; the event organizer has final responsibility.
Administrator. The user who can create the other profiles. This is the user who registers on the platform as an event administrator.
Head of distributors. Added by the administrator, acts as a distributor and is authorized to add distributors. The administrator can grant operations to the head of distributors such as viewing statistics, attendee lists, uploading Excel files or managing waitlists.
Distributor. Added by the administrator or a head of distributors. With this profile they can have electronic tickets assigned which they can send by email, SMS or WhatsApp to attendees. They can also have printed tickets assigned which, once scanned by the distributor app, will be recorded as sold.
Validator. The user who can log into the bikubo app to validate event access. There is a general username/password with access to validate all control points and events, and the administrator can also create validator profiles with access limited to authorized control points and events.
Attendee. The person who holds a ticket or credential. They may have received it from the administrator or a distributor. Specific intranet access can be enabled for attendees in certain configurations.
Affiliate. A person or company with access to an intranet showing categories of tickets they are authorized to sell; by sharing the category link, when a sale is made through that link the affiliate receives a pre-agreed commission from the event administrator.
Yes. When an administrator registers on the platform, a set of default modules is enabled that are most commonly used. Many additional modules can be enabled based on client needs. For example:
- Cards. Used so an attendee with a card can access multiple events according to configuration.
- Intranet access for attendees so they can access content specific to each attendee.
- Communication tools: mass email, SMS or WhatsApp sending to attendees.
- Implementation of an advanced user chat (similar to Slack) with topic rooms and role assignment.
Other features available on demand.