Ticket

Available with the module Octopus Guest

 

Functionality found in the Access > Tickets submenu designed to issue access codes, with the predefined rates in the Location configuration > Access methods section. Depending on the configuration, several options for ticket issuance will appear, always in an intuitive and fast way. The steps for code generation are listed below.

 

Ticket creation

To create tickets, go to the Access > Tickets > Create ticket submenu and follow the steps below:

Select a ticket type

There will be several formats and within each format, there may be several types. The formats can be:

  • Single Ticket: Intended for individual use, although the number of simultaneous devices that can use the generated ticket can be configured, since the same user can use several devices. They are of fixed time and are also ideal if the rates have a price associated with them. It will be necessary to configure the user ID.

  • Variable Ticket: Also for individual use, but have the particularity that you can choose the validity time of the ticket in a certain range of dates. You can set a price per day on these tickets.

  • Special Ticket: In this case the ticket is fully customizable (including access credentials) and is ideal for special cases such as events or similar.

Option extra fields in ticket issuance

For the three types of ticket, there is the option to request extra fields when issuing the ticket from the platform (configurable in access methods). The user who validates with this ticket, will be registered on the database with the information that has been added in this section.

 

Confirmation of generated ticket and shipping channel

It can also be configured in the Locations configuration section:

  • Print the Ticket.

  • Via Email.

  • Via SMS.

 

Tickets Issued

From the Accesses > Tickets > Ticket issued submenu you can view the list of sessions of the tickets or passcodes issued and perform operations on them, in particular canceling, printing or exporting them.

 

In the list you can see the following information:

  • Unique serial number of the ticket.

  • Date and time of creation.

  • User ID.

    • In the issued tickets will be a field filled by the user. If the option to send by email is chosen, it will be the recipient's mail.

    • Through PayPal, it will be the email associated with the business paypal account.

    • Through Wifi sponsored, it will be the guest's mail.

    • Through sending SMS it will be the guest's mobile.

    • Through API Rest, it will be a parameter of the request (in case of e-mailing, the recipient's mail).

  • Type. There will be the following types:

    • Individual ticket

    • Variable ticket

    • Special ticket

    • Paypal

    • SMS

    • Sponsor

    • PMS

  • Status. There will be different status, once the ticket is generated.

    • No use

    • In use

    • Expired

    • Cancelled

  • Connections. A number corresponding to the number of connections made with that ticket will appear. That same number will have a hyperlink to be able to observe all the connections in detail.

  • Additional common information. You can see in the icon to expand information:

    • Access credentials.

    • Date First Login, if the case has occurred.

    • Expiration date.

    • Number of simultaneous devices.

    • Accumulated session time.

    • Accumulated upload traffic.

    • Accumulated download traffic.

  • Individual Operations

    • Print credentials

    • Cancel ticket

It is possible to filter the list by serial number, creation, user ID, type, status, connections, first login, user name and number of devices.