I've installed the pro version of this plugin for the booking system on GlowUpKnox.com. I've ran across multiple issues that I've listed below. Some of these I would classify as critical and appear to be actual bugs preventing users like me from using the plugin properly, potentially affecting a new client base.

Note - updated to v7.3 on 12/27. Running on Divi with all associated themes and plugins fully up to date.

Critical Errors

• **** This is the biggest one - it makes the site look broken on smaller browser widths or with any custom copy entry.**** PopUp Window - words break in the middle and unable to edit responsive breakpoints. Behavior can be seen as you resize a browser window with a line of text that needs to wrap. All words in all areas can break in the middle of the word. This does not appear to happen if the module is embedded within the window.
• Since Updating to the latest version (7.3 from 7.2), when I go into edit my Step Booking Modules, if you have “Preselect Booking Parameters” selected, all instances now say “The above custom field is not fully supported and has been rendered as a standard input." and the shortcode area is now a string of code.
• Upon update, all my custom email notifications were changed back to the default messages with no way of recovering the edited messages.

High Priority Bugs/Site Errors

• With an embedded window module, there is no way to alter the margins/padding from what I see, which can be quite large.
• Within the module, there is no way to edit the phone number display. It is always displayed with the country code and is all together as one word rather than parenthesis and dashes (or any other custom option).
• Customer Panel email notification as displayed in the “Notifications” setting area does not send to the new user even when “Automatically Create Amelia Customer user” is selected, and “Enable Customer Panel” is selected.
• The only email a new user will receive is a link from Wordpress where they are able to create a password and there is the ability to login to Wordpress via an “Amelia Customer” role where they can edit their info on the backend. We do not want that ability, or at least, for them to be readily aware of it. It would be cleaner for them to only interact with the front end Customer Panel.
• When viewing the Customer Panel page, this is the only page that shows that the page has a language translation available. When I allow it translate, it changes the “FAQ” navigation item from “FAQ” to “FAQ’s”. This is a global header/menu and does not happen on any other page.
• If requiring a password is selected for the Customer Panel, there is no intuitive way for the new user to know how to get to it or create their password or even use a “Forgot Password” link.

Suggested New Features

• Edit all settings in “developer” panel or spreadsheet so some apply globally instead of the tedious task of entering each service, package, category individually.
• Developer mode to see changes in real time instead of having to save, reload site, go through process.
• Allow for a package to have single upcharge amount for multiple services. Example: I want to create a package that includes one of our base services, but with the option to add multiple people to receive that charge (all multiplying for each additional person), but have only one flat upcharge fee across the entire package, regardless of the amount of people chosen.
• Extras have to be added manually per service. In our case, the same Extras apply and they each have a cost associate with them. It would make sense that those could be listed/edited as a section within the “Services” area next to “Resources”, then each service could choose which extras are available to them. Also, could be a way to apply a mandatory upcharge for a specific service.
• Extras costs multiply for each additional person option only per service. So if I need to change this across multiple services, I need to go into each service, then into each “Extra” and select the toggle for “The price will multiply by the number of people” for each one.
• Allow for multiple locations to have custom pricing. Example: We have a “You Come to Us” and “We Come to You” option for location. We would like the “We Come to You” option to have an embedded upcharge for that option.
• Allow for title of Service when a specific service is selected for a pop-up window. Example: I have multiple service offerings, if I open the booking module with one of the services pre-selected, there is no way for the user to easily know which service they are booking
• Allow for cancelling a booking mid-process. Example: User clicks to book an appointment, chooses a service, some options, then closes the window. It they click to book again from the same parameters, they are still at the same place in the process. Either, cancel progress upon closing popup window, or offer a “Cancel” button in the footer that clears selections instead of having to use the arrows at the top.
• Allow for a user to edit the image in the Congratulations window easily instead of the party hat image.
• For the step where a customer enters their data, allow for the custom fields to span columns, or allow for alternate layouts. If I add a text column for info or further instruction, it is forced into a column which looks like a site layout error.

I will reply to the top issue since you have screenshots here for the window resize/word breaking problem. I know the popup window is responsive and will eventually get to that size, but it does not break into smaller ratios in the same manner as the embedded window does. Thus, if a window is opened on smaller browser widths that are still above the smallest breakpoint, the text issue shows up. You need to go past the step one of the process to see what I'm referring to. The word break problem also shows up when I have a Custom Text Field as part of the customer information step. I've attached multiple screenshots so you can see exactly what I'm talking about.

The main issue isn't that the responsive breakpoints don't appear to be the same as the embedded (it's still an issue however) but that because of this word breaking is unpredictable. I can't imagine a scenario where you want words to break in the middle like this.

** As for the other issues, I will create separate tickets for each one as you requested.