Hi, omid

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

The synchronization with Google Calendar, if I understood correctly what you described, doesn't work this way. Amelia doesn't pick up if you create an appointment in Google Calendar.

If you set a Busy slot on Google Calendar, that time span will not be available for booking on the Amelia side.

Any appointments you create in Amelia will synchronize on Google Calendar, but it is not vice-versa, Amelia can not pick up appointments created from the Google Calendar - I hope i explained this correctly.

-

If I didn't understand what you meant, please correct me.

And in case that I did, if you need us to log into your WP-Admin and investigate the issue in more detail, that will go beyond the scope of what Pre-Purchase support covers, I would ask you to make a new ticket in the Amelia category, because only customers with an active licence have access to full support.

Thank you.

Hi, omid

Thanks for reaching out to us

- Can you please tell me did you do this step in Amelia?

Remove Google Calendar Busy Slots

Enable this option if you want to remove the time slots of the Busy events in your employees’ Google Calendars from their work schedules in Amelia. When enabled, time slots in the Amelia Calendar will be removed whenever there is a Busy event in the Google Calendar.

Please note: In order to use 2-way Google synchronization properly your employees should set statuses of the events in their Google calendars as Busy. That way, time slots occupied by those events will be removed from Amelia calendar.

-

More details on this page, in case you didn't go through it yet.

If you already did all of this,

we will have to take a look remotely at your WP Admin setup of Amelia.

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.