We're Moving to a New Support Platform – Starting June 1st!

We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.

You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.

While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.

We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.

Thanks for your continued support and trust – we’re excited to bring you an even better support experience!

Okay
  Public Ticket #2713835
Employee email notice is wrong time!
Closed

Comments

  •  2
    Tod started the conversation

    When a client books a session with me, Amelia notifies by email.  It sends out an email to the client which has the correct appointment time.  But for the employee, it sends out an email notification and it always has the wrong time on that email and in the appointment dashboard. I have to go in to update the appointment time every time.  Please help me fix this. 


    Tod

  • [deleted] replied

    Hello Tod, 

    The timezone applied to Amelia is the one you choose in your WordPress General Settings, so please check there if you have set your City timezone, as if you haven't there can be a mismatch in the times on the front and in the back. For the front-end, customers can see times in their own timezone or the back-end timezone, depending on if you enable or disable this option in Amelia -> Settings -> General. So, if you enabled this customers saw the correct timezone but your back-end is not set to the proper (your)timezone.