Hello again Konstantinos

For the broken view - do you have SG Optimizer plugin installed? It has a front-end setting "Combine CSS files", so it never loads Amelia's styles. You can disable that and the form should look fine.

If you don't have that plugin installed, it could be some other (similar) plugin doing that, or your wp-content folder isn't writable.

As for default appointment status, that can be set per Service individually, so can you access your Service and go to the Settings tab? Under General settings, see how the default status is saved.

Of course, Konstantinos

Please provide me a temporary WP-admin login for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course we do not provide login data to third party. 

You can write credentials here just check Private Reply so nobody can see them except us.

Hello Konstantinos

I'm glad to hear you were able to resolve the other two issues.

The thing about mobile devices - are you maybe using an iPhone? I booked a test appointment with AMELIA TEST customer, and it came through normally, without having to click twice.

The double-clicking is the default behavior of iPhones, and it's got something to do with the zooming feature on those devices.

Can you please check our demo sites to see if it works normally on iPhone?

You can try adding this to the booking page, and see if that helps:

<meta name="viewport" content="width=device-width,initial-scale=1,user-scalable=no">

Hello again Konstantinos

Unfortunately, that's the default behavior of iOS. You can read more about it on this link.

When you touch an item on a webpage, it first triggers a hover state and then triggers the “click”. The end result is that you end up seeing styles applied using :hover for a second before the click interaction happens.

There is some advice as to how this can be addressed. The info is also forwarded to our developers, so hopefully they'll be able to fix it for one of our next updates.