Hello Charles.
We’re sorry to see that you’re not satisfied with the way Amelia handles Customer roles in WordPress.
The plugin is being used by tens of different industries, and the majority of them do not want customers to have to log into WordPress in order to book, reschedule, or cancel the appointment. That’s why we created the Amelia Customer Panel which can be accessed by anyone who books an appointment with Amelia.
On the other hand, people that do want Amelia’s Customers to be linked to a WordPress role need to enable “Automatically create Amelia Customer user” in Roles settings. This allows the plugin to create an “Amelia Customer” WordPress user, which is linked with the customer that booked the appointment. At the moment, a customer that books an appointment must have the “Amelia Customer” user role created, and any other WordPress user role will not be linked to the customer.
You are correct that the Customer Panel provides a separate log-in for your customers, which is not linked to a WordPress profile, but this was developed in such a way in order for users who don’t want WordPress roles to limit the customers. Our developers do have a task to link the two, so a WordPress login would work for Amelia as well, and that will be implemented at some point in the future, we just don’t have an ETA on that.
If you have any suggestions about how we should approach this, please feel free to share them with us, as we value every suggestion and every feedback regardless if it’s a negative or a positive one.
As for the Amelia roles, we suppose that you have some User Role plugin installed (like “User Role Editor”)? If that’s the case, Amelia’s (and any other plugin’s) roles capabilities are being saved by that plugin, and they are being stored by it in the wp_options database table. In Amelia, you have an option to delete all database tables upon deletion of the plugin from your WordPress site, so these capabilities and roles are being saved elsewhere.
Our developers will look into this as well, and see if there’s a way to force the deletion of everything related to Amelia from the database.
Kind regards