Couple of questions about Tickets

This topic contains 7 replies, has 2 voices, and was last updated by  Stephen Harris 9 years, 7 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #17195 Reply

    Hi

    I just have a couple of questions about the plugin.

    1. Does the plugin send an e-ticket out to the user once they have booked and the booking is confirmed (we’ll probably be using offline payments for now)
    2. Can the user submit a cancellation request?

    Thank you
    Rebecca

    Rebecca
    #17201 Reply

    One other question occurs, can visitors book more than one event at a time?

    Rebecca
    #17208 Reply

    Hi Rebecca,

    A confirmation e-mail is sent out once the booking is confirmed. For free events this is instantaneous, for events paid with an online payment gateway this is as soon as the user completes the checkout, and lastly for offline payments, it is when the admin user confirms the booking.

    (2) is possible if the user is logged-in when making a booking (or creates an account in the process of booking). You can use the shortcode [booking_history] to display the user’s previous bookings, and optionally allow them to cancel a booking.

    Lastly, no. Booking for a second event would require a separate booking.

    Stephen Harris
    #17229 Reply

    Cheers for that.

    In regards to making multiple bookings am I right in thinking if the user is logged in, it would be easier to book other events as they would have less to fill out? If they don’t have to fill the first part of the form out I’m thinking we could work with the fact you can only book one event at a time.

    Rebecca
    #17231 Reply

    Yes, the only fields at are on the booking form by default are name / email (logged out users only) and ticket selection (and that can be hidden if simple booking mode is enabled).

    So its possible a logged in user would simply need to click ‘Book’.

    However they would need to go through the chosen payment gateway for each booking.

    Stephen Harris
    #17232 Reply

    That last comment isn’t really relevant for free events / offline bookings.

    Stephen Harris
    #17271 Reply

    Fantastic, thanks for the reply.

    I have another question (sorry for all these questions we just want to make sure this is the right plugin for the client I’m setting this up for).
    She would like to know how the cancellations would work.

    You previously said we could optionally add a cancellation button on the Booking history page,
    I can’t see this in the admin demo so would this be something I have to add into the template?
    If that is the case
    1. would there be documentation / guidance on how to do this? (obviously after we have purchased.)
    2. Would this simply be a button that sends an email to the admin with the booking number and a message that they would like to cancel?

    If there is actually an option that I have missed could you tell me how the cancellation button works?

    Hopefully this is the last question.
    Thank you for all your help so far.

    Rebecca
    #17279 Reply

    Hi Rebecca,

    Yes the documentation can be found here: http://docs.wp-event-organiser.com/shortcodes/booking-history/

    The option adds a link to the booking history table that cancels the booking for the user automatically. Any refunds to be processed would have to be done so manually.

    Stephen Harris
Viewing 8 posts - 1 through 8 (of 8 total)
Reply To: Couple of questions about Tickets
Your information:




To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax


<a href="" title="" rel=""> <blockquote cite=""> <code> <pre> <em> <strong> <del datetime=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width=""> <p style=""> <span style="">