• Hi,

    In version 2.2.0 you report this as fixed, but I still see the same issue

    Updated the interaction between the “automatically confirm below party size” and “automatically confirm below seats number” settings, to allow them to work in an OR capacity, so they can be used together

    Use case
    – Basic » Automatically Confirm Below Party Size: 5
    – Advanced » Max Reservations: 5
    – Advanced » Max People: 15
    – Advanced » Automatically Confirm Below Reservation Number: 3
    – Advanced » Automatically Confirm Below Seats Number: 10

    Start with no reservations at all
    1) reservation for 4: it is auto confirmed (ok)
    – total seats: 4
    2) reservation for 4: it is auto confirmed (ok)
    – total seats: 4+4=8
    3) reservation for 4: it is auto confirmed (not ok)
    – because total seats: 4+4+4=12
    4) reservation for 2: it is auto confirmed (not ok)
    – because total seats: 4+4+4+2=14

    The should not be in an OR capacity but in an AND capacity.

    Only auto confirm if
    – Basic » Automatically Confirm Below Party Size: 5
    AND
    – Advanced » Automatically Confirm Below Reservation Number: 3
    AND
    – Advanced » Automatically Confirm Below Seats Number: 10

    Thanks
    JP

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support jaysupport

    (@jaysupport)

    It isn’t about should or shouldn’t. The fact is that it was updated to work in an OR capacity. So, in your case, it will automatically confirm if the party size is below 5 or the total number of seats for that time slot is at less than 10. This is to allow people more ways to set it up. For example, you can now set it up in such a way that you can say I want to stop automatically confirming at 10 people, unless the reservation is for 1 or 2 people, then I still want it to auto-confirm. Before you couldn’t do that.

    That being said, we can look into adding an option in the future that lets you switch between AND and OR functionality, should there be a reason that you’d want it to go back to working that way.

    Additionally, if you have questions specifically related to a premium feature, such as the automatically confirming below seats number, then you’ll have to contact us via email or our site (https://www.fivestarplugins.com/support-center/) as discussion of the premium version is not allowed in the forums (https://wordpress.org/support/guidelines/#do-not-post-about-commercial-products). The scope of your original question/comment involved the use of the auto-confirm functionality available in the free version, which we can discuss here, but anything directly about premium features would need to be via email.

    • This reply was modified 5 years, 5 months ago by jaysupport.
    • This reply was modified 5 years, 5 months ago by jaysupport.

    In the use case I provided, the behaviour is exactly the same as how it was before this update. The ‘Automatically Confirm Below Party Size’ always overruled all other auto confirm settings.

    you can say I want to stop automatically confirming at 10 people, unless the reservation is for 1 or 2 people

    This doesn’t make sense. If you have a capacity of 10, then that’s the point you want to stop auto confirming all together. There are simply no more seats/tables available, not even for 1 or 2 people.

    In a restaurant you work the other way around.
    – You want to stop auto confirming completely if you almost reached your capacity.
    – You do want to auto confirm reservations for 4 people or less, because that’s the number of seats at a table.
    – You do not want to auto confirm for larger party sizes, because that will involve moving seats/tables around, so you need to see if that’s possible.

    I know this is partially about a premium feature and I have created a premium ticket for this issue in the past. That ended in a very unpleasant and unprofessional support experience up to the point that I asked for a refund. After I saw in the release notes there was a change around auto confirmation I gave it a try again and found that nothing has been changed. I decided to create a ticket here because I am 99% sure you are not the same person as the person from premium support.

    Plugin Support jaysupport

    (@jaysupport)

    I understand your use case and where you’re coming from. This change was made to allow greater flexibility in using several of the available options together. However, I can understand why you would want it the old way. I think the way to get the best of both worlds would be to make it an option, as I referenced in my previous reply. I’ve already noted it as a feature suggestion, so hopefully that’s something that can be modified/added soon.

    And I apologize if you had a bad experience with any version of the plugin and/or with support. I can assure you that is definitely not the norm. If you have any issues with premium features, please do contact the email support and don’t fret about having a bad experience. I’ve never heard of any such issues, so I’m sure it was an isolated incident and something they would make sure to not allow to happen again.

    • This reply was modified 5 years, 4 months ago by jaysupport.

    I don’t want it the old way. That worked exactly the same way as I described and how it works now. Nothing has been changed for the example I gave.

    Plugin Author Rustaurius

    (@rustaurius)

    Hi @jpnl,

    We had a talk amongst our team about this feature before the previous update, and the consensus was that a booking should be confirmed if any of the confirmation conditions was met (OR logic, not AND). Again, this was to allow greater flexibility as some users could want to always allow bookings for small parties (if they have a bar area with some seating for small groups, for example, or if they’re a larger venue that can always fit a table of 2 in somewhere), and specific confirmation options can be left out if there’s a hard limit in play for a particular restaurant.

    We’re going to release an update later today with a filter (‘rtb_determine_booking_status’) specifically for the status field, so that users can create a function to change the status before a booking is created on their end if they would like the confirmations to work in a different way. If you send us an email (since this covers, in part, a premium feature), I’d be happy to help you set that up for your particular use-case.

    Call me stubborn, but I honestly don’t understand that decision. This is only about the automatic confirmation. Bookings can still be made when it reaches the limit, they only need to be manually confirmed.

    Did you get input from restaurant owners about that logic? I come from a hospitality background and I only work with restaurants. They don’t want to risk automatically getting overbooked in any way. They want to automatically confirm UNTIL ANY of the capacity restrictions is reached. They still might be able to fit in a table of two somewhere, but they want to check, be in control and manually confirm if it fits in.

    With maximum capacities, there is no ‘always’ fits in. The may be able to fit the first one, but what about the next one, or the next one, or etc.

    We deal with a maximum quantity for seats and tables (called reservations in premium). If either one of them is booked out, you have to stop selling. Both are equally important. You can’t simply leave one of them out because it increases the risk of getting over booked, either by seats or by tables/reservations.

    Example for a restaurant with:
    – 12 tables with 4 seats each (ie auto confirm below 12 reservations)
    – 48 seats in total (ie auto confirm below 48 seats)

    » When you reached 12 reservations for two, auto confirm needs to stop. Although you have 24 free seats, there are no more reservations/tables left
    » If you get 4 reservations for 12, auto confirm needs to stop. Although you have 8 tables/reservations left, there are no more seats.

    It’s nice that you are willing to implement a filter for users who want to change the behaviour, but I think that’s overly complex.

    In my opinion, it makes more sense to change the behaviour and stop auto confirmation when the capacity of either one of the 3 settings (in free AND premium together) is reached.

    That way, if there are users who never want to stop auto confirmations, all they have to do is increase the limits to a higher value then they really have. That way both options are possible without technical stuff.

    Thanks
    JP

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Automatic confirmation issue’ is closed to new replies.