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 #2728180
Scheduling appointment problems
Closed

Comments

  •  1
    Jordan started the conversation
    March 22, 2021 at 4:27pm

    Hi, I run an online music lesson studio that uses Amelia booking to manage our schedule. We have options for students to take lessons both at a half-hour or one-hour long lesson. I have two issues going on that I can't figure out how to resolve on my own. Please refer to the URL https://thelessonfoundry.com/register for these questions.

    1. When a student wants to select an hour-long lesson, the option to begin a lesson on a half-hour slot is not available. For example, if I wanted to take a one-hour long voice lesson, my only option would be to sign up at the top of the hour. So I could sign up from 1:00-2:00pm but not 1:30-2:30pm. Is there a way to fix that so that's a possible solution? I have a customer that needs this kind of solution very soon.
    2.  I have had certain students leave and come back. When they want to sign back up for lessons, I have had to handle registering them on the back end, because the registration calendar only allows for new users to make appointments. If someone with an existing email address in our system tries to sign up the scheduler says that email is already taken and won't let them advance, even if they're already logged in under that email address. How can I fix this? This one is less urgent because it happens less frequently, but is definitely a bottleneck.

    Thank you, looking forward to hearing back

  • [deleted] replied
    March 24, 2021 at 11:36am

    Hi Jordan,

    thank you for reaching out to us!

    I will be happy to assist:

    1. Please advise if the employees who work on these services, which you want to start at a half an hour mark, have their shift starting at a half hour mark? For example, and employee who has a shift starting at 9am, and has no Buffer Time Before set on 30 minutes, will have their shift start at 9am. The employee who starts working at 9:30 does not need the Buffer time, and the appointments will start at 9:30. Also please check in Amelia > Settings > General Settings, if the option Use service duration for booking a time slot is on, so if your service duration is 30 minutes, the appointments will start every 30 minutes.

    2. You can go to Amelia > Settings > Roles > Customers, and check if the option Check customer's name for existing email when booking is enabled, because in that case, it will try to disable using a different name with an already registered email, triggering the Already Exists error. You can also enable Automatically Create Amelia Customers here if that option is convenient for you (Amelia will register a customer immediately upon the first booking they make, they just need to use the same credentials every time).

    I hope this helps!

  •  1
    Jordan replied
    March 24, 2021 at 1:38pm

    Hi Ivana,

    Thank you for your reply.

    1. "Use service duration..." was on, that resolved my issue!
    2. That option was checked, hopefully that resolves that problem as well. Thank you again!

    Hopefully this can help someone else that might have a similar issue in the future!