MineTickets: Ticketing and Booking Platform Development

What MineTickets is for

MineTickets is a booking and ticketing system that a business runs as its own website, not as an account on someone else's service. WeebPal builds it, deploys it and extends it for organisations that sell tickets or take appointments, and each deployment is set up around the kind of booking that business takes:

• Admission tickets for museums, zoos and theme parks. Visitors book online and, where the venue offers it, choose a specific seat or viewing area.
• Event tickets with seat selection for concerts, sports matches and cultural events. Before the event, attendees pick and reserve the seats they want.
• Appointments with doctors, dentists, spas and beauty salons. Patients and clients choose their provider, a service or treatment, and a date and time that suit them.
• An agency whose client sells tickets or takes appointments. We deploy MineTickets together with the agency, under the agency's name, as described further down.

Room booking for hotels is a different job, with rooms, check-in and housekeeping to run. We build that on a separate platform, MineRooms.

Where MineTickets runs

MineTickets runs live at mineticket.com, with a solution for each kind of booking it covers: event tickets with seat selection, admission tickets, and appointments for doctors, dentists, spas and beauty salons.

What is already in MineTickets

The platform is made of the booking site customers use and the tools the organiser uses to run it. Both work on a mobile phone as well as on a computer.

For the people who book

• Online booking of tickets and appointments. The booking flow is built to take changes, so details, dates, times and the service booked can be adjusted after the booking is made.
• A choice of payment methods, with more than one payment gateway connected.
• A PDF ticket, ready to download and print as soon as the booking is complete.
• QR codes for purposes such as event entry, which cut down on paper tickets.
• Several tickets or booking confirmations combined into a single organised document.

For the organiser

• Tickets created for each event and tailored to it.
• A view of the tickets, seats or slots still available, to keep an eye on capacity, and of the tickets already booked, which can be tracked and changed.
• Event details and scheduling.
• For clinics, spas and salons: services, treatments and packages, a calendar of appointments, and customer contacts for reminders, offers and feedback.
• Orders and customers, with reports on orders, income and schedules, and promotions.
• News and announcements published on the site.
• The layout, content and design of the PDF ticket, and the settings of its QR codes, adjusted to the event and the brand.

How we deploy and extend MineTickets

A MineTickets project starts from the version already in production, not from a blank build. Before anything is signed we walk through it with you from both sides, the customer making a booking and the organiser running tickets, events and appointments, so you decide against something real rather than a feature list.

What usually changes from one business to the next: the kind of booking you take, whether admission, seated events or appointments; your ticket types, services, treatments and packages; the payment gateways; the layout of the PDF ticket and what its QR codes are used for; the news and pages on the site; branding and domain; and connections to systems you already run, such as a newsletter service. Customisation is kept apart from the platform core, so a core upgrade does not overwrite it. For an organisation commissioning ticketing and booking system development, that work is a development project that starts from working software; the order of the work and the fit report are set out in how a platform implementation runs.

Attractions, events and tourism operators are covered with hotels and restaurants on the hospitality and tourism page.

Why run a booking system of your own

Many businesses take bookings through a service they share with other businesses. MineTickets is set up the other way round: each deployment is a separate system that belongs to one business.

• Independence. Your system does not depend on any other business or service. What runs on it, and when it changes, is your decision.
• Your data on your own server. Bookings and customer records are kept on a server you control, out of reach of anyone you have not authorised.
• Changes that affect no one else. A change to your booking rules, your tickets or your pages applies to your system alone, so it does not have to suit anyone else's business first. As the business grows, the system is extended with it.

For agencies

If your agency's client sells tickets or takes appointments, we deploy and adapt MineTickets together with you, under your name, and your client receives the running system and its source code. You keep the client relationship; the partner programme sets out how a platform partnership works.

Hosting, source code and warranty

MineTickets runs on your own servers or cloud account, or on infrastructure we operate under a managed hosting agreement, and nothing proprietary runs on it, so you can move later. You receive the whole running system and its source code; what we build for you on top of the platform is a development project, and its source code is assigned to you: what you own.

Development work carries our warranty: one year by default, up to three, agreed in the contract before work starts, with the team that built it doing the fixing. Ongoing updates sit in a separate support and maintenance agreement. The guides below give an overview of the platform for the people who run it and for the people who book through it.

What it costs

A MineTickets deployment is placed in the project tiers on the pricing page like any other build, by what the finished system has to do: the kinds of booking, the integrations, the records to move and the languages. What already runs in the platform is not charged as if it were written again; the price is for the part built for you, fixed once the fit report is agreed. The tiers run from Micro to Strategic, and the fit report says which one your deployment is in.

Questions about MineTickets

Can customers change a booking after it is made?

Yes. The booking flow is built to take changes, so details, dates, times and the service booked can be adjusted after the booking is made, and the organiser can track and change the bookings already taken.

How do customers receive their tickets?

As a PDF ticket, ready to download and print as soon as the booking is complete, with a QR code for purposes such as event entry. Several tickets or confirmations can be combined into one document.

Can the ticket carry our own design?

Yes. The layout, content and design of the PDF ticket, and the settings of its QR codes, are adjusted to the event and the brand.

Can a clinic or salon use it for appointments?

Yes. Patients and clients choose their provider, a service or treatment, and a date and time; the organiser works from a calendar of appointments and keeps customer contacts for reminders, offers and feedback.

Where are bookings and customer records kept?

On a server you control: your own servers or cloud account, or hosting we operate for you. Each deployment is a system of its own, not an account on a shared booking service.