Events

Welcome to Ottu's Event Plugin, a comprehensive and powerful tool designed to elevate your event management experience. This plugin seamlessly integrates into the Ottu Dashboard, providing you with a suite of features to organize, promote, and manage your events effortlessly.

From creating and customizing events to monitoring bookings, transactions, and attendee check-ins, Ottu's Event Plugin offers a robust set of functionalities. Let's embark on a journey through the various sections of this plugin, exploring how each feature can be harnessed to streamline your event management workflow.

Whether you're a seasoned event organizer or new to the field, Ottu's Event Plugin is here to enhance your capabilities and ensure a seamless event planning process. Let's dive into the details and unlock the full potential of Ottu's Event Plugin for your event management needs.

In Events section, you can explore details about your created events and easily add new ones through Events section. Access crucial information such as the event title, start and end dates, event URL, and activation status.

Whether reviewing past events or planning new ones, this section serves as a central hub for comprehensive event analytics.

  • To access the Events section, navigate to the Events Tab on the Ottu Dashboard and select the Events section.

To create new event, access the Events section. Once there, click on "ADD EVENT" Subsequently, you'll be prompted to provide the following essential information:

Populate general event details such as the event name, date, location, and more.

  • Is Active: Yes/No, indicates whether this object is currently active and can be utilized and displayed on the site.

  • Title [en]*: Event Title in English

  • Title [ar]: Event Title in Arabic

  • Display Title: Yes/No, display the title on the event details page.

  • Description [en]*: Event Description Summary in English

  • Description [ar]: Event Description Summary in Arabic

  • Show Ticket Details in Event's Description: Yes/No

  • Short Description [en]: Brief event description in English, visible in social media previews in English.

  • Short Description [ar]: Brief event description in English, visible in social media previews in Arabic.

  • Slug: URL-Friendly Event Title. A text string used in a URL, to create a readable and SEO-friendly link. (Automatically populated by the system)

  • Event Type: It provides a high-level overview of the event's format or purpose. Examples include Conferences, Webinars, Workshops, Concerts, Exhibitions, and Networking Events.

  • Categories: It facilitates additional refinement and detailed classification within the overarching categories of event types. Examples include Technology Conferences, Music Festivals, and Comedy Shows. To learn how to add a new event category, refer to the Add Event Category section.

  • Currency Code: It represents the specific currency used for financial transactions and ticket pricing associated with the event.

  • Is Online Event: Yes/No

  • Is Free: Yes/No

  • Venue Name*: The name of the location where the event is taking place. It helps attendees identify the specific place hosting the event.

  • Google Maps Embedded Code*: It's an HTML snippet from Google Maps that enables event creator to embed an interactive map, displaying a specific location, directly into a webpage.

  • Google Map Link: It is a hyperlink that takes users directly to a specific location on Google Maps, making it easy to view and navigate to that place.

  • Banner: is a graphical representation used for promotion. It's an image with a minimum width of 6200px and a minimum height of 600px.

  • Background Image: It is a graphical element chosen for visual impact, subject to the same conditions as the banner image: minimum width of 6200px and minimum height of 600px.

  • Calendar Image: It is a graphical element subject to the same conditions as the banner image: it must have a minimum width of 6200px and a minimum height of 600px.

  • Event URL: It is the web address that leads to the dedicated webpage providing information about a specific event. (Automatically populated by the system).

  • Feedback URL: It is the web address that directs users to the designated webpage where they can provide feedback or reviews about a specific event. (Automatically populated by the system).

  • Registration URL: It is the web address that guides users to the dedicated webpage where they can register or sign up for a specific event. (Automatically populated by the system)

  • Start Date*: It refers to the specific date when the event begins.

  • Time*: The commencement time of the event.

  • End Date*: It refers to the specific date when the event ends.

  • Time*: Event's end time.

  • Tickets Available From: It indicates the date and time when attendees can begin securing tickets for the event.

  • Tickets Available Till: It marks the deadline (date and time) for securing tickets for the event.

  • Display Listing: Yes/No to determine whether the event should be displayed in the list within the Events section.

  • Extra: The area for including additional information, notes, or details that may not fit into specific predefined fields but are relevant to the event. (* required)

Where merchant communicates important conditions and rules related to the event.

Upload and manage images associated with the event.

This section allows merchant to add tickets and furnish them with comprehensive information. This includes details such as ticket names, pricing, availability, and any specific conditions or benefits associated with each ticket.

When clicking on “Add new event ticket details” the merchant is required to complete the following information.

  • Is active: Indicates whether the ticket is currently active or not.

  • Ticket Name [en]*: The name of the ticket in English.

  • Ticket Name [ar]: The name of the ticket in Arabic.

  • Price: The cost associated with purchasing or registering for the ticket.

  • Abbreviation [en]: An abbreviated form or acronym for the ticket name in English. Displayed next to price.

  • Abbreviation [ar]: An abbreviated form or acronym for the ticket name in Arabic. Displayed next to price.

  • Ticket Quantity*: Determine the overall number of tickets available for the associated event.

  • Quantity Label [en]: This label, displayed in English, indicates the quantity of tickets in the frontend dropdown menu.

  • Quantity Label [ar]: This label, displayed in Arabic, indicates the quantity of tickets in the frontend dropdown menu.

  • Choose Date: Indicates the dates on which the event will occur.

  • Event Time: This refers to the time slot or duration allocated to the event linked with the ticket. You have the option to select from a predefined drop-down list or include a new time slot by selecting "+" next to the drop-down, enabling you to specify both the start and end times of the event. Multiple time slots can be selected.

  • Max Tickets: The maximum number of tickets a user can purchase or register for in a single transaction.

  • Min Quantity: The minimum number of tickets required to be selected or purchased.

  • Sell Ticket Individually: If selected, each ticket is sold individually rather than as part of a group. 1 ticket per user.

  • Show Remaining Tickets Publicly: If selected, the remaining quantity of tickets is displayed publicly.

  • Allow Ticket Booking Till End of Time of Event: If selected, allows booking or registration for the ticket until the end time of the event.

  • Apply Tickets Limitation to Each Day: Choose whether to set the maximum available tickets for each day.

  • Lower Barrier: Displays the available quantity if the remaining quantity falls below this specified number.

  • Background Image: An image associated with or representing the ticket. The minimum image width should be 6200px, and the minimum image height should be 600px.

  • Description [en]: Additional information or details about the ticket in English.

  • Description [ar]: Additional information or details about the ticket in Arabic.

  • Checkin Time Limit: The designated time duration for check-in associated with this ticket. For example, if the event starts at 2 PM and you set a 20-minute check-in time limit, guests can check in from 1:40 PM onwards.

  • Subtickets associated with this ticket: Any additional subcategories or related tickets associated with this main ticket. To learn how to add a Event sub-ticket, refer to the Add Event Subticket section. (* required)

Tailor and set up extra fields for either the “From” or “Order Description” sections on the checkout page to be filled by customer.

When clicking on “Add new field” the merchant is required to fill in the following details.

  • Type: The type of the added field can be categorized as either “Custom” or “Builtin”.

  • Itinerary Display: If checked, the new added field will be shown in the “schedule table” or “planning table” (itinerary table) within the invoice PDF.

  • Display Section: It determines the placement of the newly added field on the checkout page. Available options include “From” , “Order Description”.

  • Is active?: It allows for the control and management of the newly added field on a site or platform, providing the ability to enable or disable its usage and visibility.

  • Required?: It determines whether a newly added field is mandatory or optional.

  • Validator: It imposes constraints or rules on the new field's value. It ensures that the provided value meet certain requirements or conditions specified by the validator.

  • Field: A drop-down list of predefined fields. It is presented when the Builtin type is selected in the Type parameter.

  • Order: It determines the display positioning of the fields within the same section.

  • Placeholder [en]: It provides guidance or an example of the expected input, helping users understand what information is required or the format it should take. (Should be In English).

  • Placeholder [ar]: It provides guidance or an example of the expected input, helping users understand what information is required or the format it should take. (Should be In Arabic).

If the Type is marked as “Custom”, the Field parameter will disappear, and the following fields will be displayed for filling:

  • Name: HTML field name utilized solely for backend validation. It will not be visible anywhere.

  • Label [en]: Custom field's label in Arabic.

  • Label [ar]: Custom field's label in Arabic.

Proceed to save the provided information above. Once saved, a new event will be added. Access details for this event by navigating to the Events Tab on the Ottu Dashboard and selecting the Events section.

In this section, we will explore the process of adding a new event category within Ottu. Event categories serve as a valuable tool for effectively organizing and classifying various types of events. As you embark on creating a new event category, several essential parameters come into play.

  • To access Add Event Category section, navigate to the Events Tab on the Ottu Dashboard and select the Add Event Category section.

To create a new event category, navigate to the Add Event Category, then fill the following parameters:

  • Event Category Name *: Specify the name of the event category

  • Event Category Name [en]: Specify the name of the event category in English.

  • Event Category Name [ar]: Provide the name of the event category in Arabic.

  • Image (optional): Include an image to visually represent the event category. (* required)

In Ottu, merchant can expand his event options by introducing subtickets, offering attendees more detailed choices, and providing them with diverse options and enhancing the overall event experience.

  • To access Add Event Subticket section, navigate to the Events Tab on the Ottu Dashboard and select the Add Event Subticket section.

To create a new event subticket, navigate to the Add Event Subticket, then fill the following parameters:

  1. Sub Ticket Name*: Provide a name for the subticket.

  2. Sub Ticket Name [en]: Specify the name of the subticket in English.

  3. Sub Ticket Name [ar]: Provide the name of the subticket in Arabic.

  4. Price*: Set the price for the subticket.

  5. Abbreviation: Include an abbreviation for the subticket.

  6. Abbreviation [en]: Specify the abbreviation for the subticket in English.

  7. Abbreviation [ar]: Provide the abbreviation for the subticket in Arabic.

  8. Ticket Quantity*: Specify the quantity of subtickets available. (* required)

The optional parameters allow you to customize the subticket details further, tailoring them to meet the specific preferences and needs of your audience.

In the Bookings section, you have comprehensive tools to monitor and manage all completed bookings.

  • To access Bookings section, navigate to the Events Tab on the Ottu Dashboard and select the Bookings section.

Through the Bookings section, merchants gain valuable insights into the following key information:

  1. Number of Bookings: Keep track of the total number of bookings made.

  2. Attended: Monitor the count of attendees who have participated in the booked events.

  3. Not Attended: Track the number of bookings where attendees did not show up.

Additionally, each booking is detailed with the following information:

  • Event: Identify the specific event associated with each booking.

  • Quantity: Displays the number of tickets booked for the associated event.

  • Full Name: The full name of the customer who made the booking.

  • Purchase Type: Displays whether the booking is for a paid or free event.

  • Email: Retrieve the customer's email address.

  • Event Date: Know the date of the booked event.

  • Created: Understand when the booking was created.

  • Customer Phone: Access the customer's contact number.

  • Action: Utilize the action feature to share booking details with the customer via email.

All the listed bookings can be filtered based on the following criteria:

  • Event

  • Email

  • Customer Phone

  • Full Name

  • Event Creation Date

  • Start and End Event Date

All bookings can be exported in CSV or XLS format.

To book a slot for an event, there are several methods available. Merchant can either send the event link to the customer and have them fill in the necessary details. Alternatively, merchant has the option to create a payment link for the event and share it with customers for payment. The following sections will elaborate on each of these booking methods.

To book by sharing the event URL with customers, follow these steps:

  1. Go to the Events section.

  2. A table will be displayed, showcasing all created events with details such as start and end dates, event URL, and event status (active or not).

  3. Share the Event URL with customers, enabling them to access the event's checkout page.

  4. Customers can then fill in the necessary details to proceed with the booking.

To book by creating a payment link for customers, follow these steps:

  1. Navigate to the Ottu Dashboard.

  2. Under the Events Tab, select the Create section.

  3. A dropdown list will appear, featuring all the created and activated events.

  4. Choose the desired event from the list.

  5. Fill in the ticket details associated with the selected event.

  6. Provide the necessary information.

  7. Once completed, a payment link for event booking will be generated.

  8. The payment link will be sent to the customer via email.

  9. Access the created booking payment link from the Transaction table, where all booking payment links are listed.

  10. Share the generated link with the customer, enabling them to proceed with the booking.

Subsequently, the customer accesses the event checkout page and completes the payment process.

Ottu empowers merchants with the capability to effortlessly edit or cancel any customer booking. Within the Bookings section, merchants can simply click on any booking, and the booking page will be displayed. Here, the merchant can modify the booking details or choose to cancel it.

For Example, by clicking on the "test" booking, as depicted in the figure above, the merchant will be redirected to the corresponding booking page. Here, the merchant can either edit or cancel the booking, as illustrated in the figure below.

Ottu provides merchants with the capability to monitor every transaction related to an event.

  • To access Transactions section, navigate to the Events Tab on the Ottu Dashboard and select the Transactions section.

All transactions are listed there with informative details, including payment date, transaction ID, state, gateway, and more.

The Fulfillment section empowers organizers or merchants to effortlessly verify bookings by scanning the unique QR codes generated for each person upon completing their booking.

Upon reaching the event, customers can present their tickets to the merchant. Merchant can navigate to the Fulfillment section, select the relevant event, and the scanning process will be automatically initiated, ensuring efficient verification.

  • To access Fulfillment section, navigate to the Events Tab on the Ottu Dashboard and select the Fulfillment section.

  1. Navigate to the Events section in Ottu.

  2. Click on "ADD EVENT" to initiate the event creation process.

  3. Fill in essential details such as event name, date, location, and other required information.

"Is Active" indicates whether the event is currently active and can be displayed on the site. Choose "Yes" to make the event live.

Events can be categorized by type and further refined with specific categories. Use the "Event Type" and "Categories" parameters during event creation.

"Display Title" determines whether the event title will be shown on the event details page. Choose "Yes" or "No" based on your preference.

Yes, Ottu allows you to add custom fields for either the "From" or "Order Description" sections on the checkout page. Please refer to fields.

  1. Navigate to the Bookings section in Ottu.

  2. Click on the specific booking you want to modify or cancel.

  3. Edit the booking details or choose to cancel it.

For more information please refer to Editing Customer Booking section.

The Fulfillment section allows merchants to verify bookings by scanning QR codes generated for each person. It streamlines the event check-in process.

Customers can book an event by either accessing the event URL shared by the merchant or by using a payment link provided for the event. For more information please refer to How to Book section.

Yes, Ottu provides the option to export all bookings in CSV or XLS format for convenient data handling. This can be performed from Bookings section.

These FAQs aim to provide a quick reference for common queries. For more detailed assistance, refer to Ottu's user documentation or reach out to Ottu's support team.

Last updated