I would like to deploy AMELIA booking application for a friend who has her own salon (hairdressers). It will be my first integration and not all employees are comfortable with new technologies. So, I try to identify the frictions with AMELIA booking system because except if I am wrong, if we depoy AMELIA, then all employees will have to use AMELIA to plan a new appointment. No paper will be allowed.
(1) Hairdressers now make new appointments by phone and write down appointments on paper. The customer calls, schedules the appointment and then give just his firstname. After AMELIA implementation, do you confirm that the salon owner and each employee will have to ask to the customer the firstname + lastname + email in order to create first a new customer and then be able to plan a new apointment ?
Not all employees are comfortable with new technologies. So I think there might be some friction for the employee and for the end customer if they have to ask for the customer's first name + last name + email.
I think it's fine to ask for the customers who decide to book online; but for the customer who still books by phone it is a pain from my perspective. How is it possible to keep these fields mandatory online but not ask for them on the phone (at least in a first period)?
(2) When an employee receives a call, she should be able to make the appointment for herself; but also for another employee if the customer on the phone wants an appointment with her colleague.
Is the only solution to use the AMELIA WordPress interface? Or is it possible to plan a new appointment from the employee panel for instance. It seems not to be possible because the employee panel seems to have a specific access for each employee. Is it correct? What yould be your recommendation please?
(3) Some employees give a haircut in 35 minutes and other employees do the same service in 45 minutes. How is it possible to offer the same service with a different duration depending on the employee selected?
Dear Amelia Support, Dear all,
I would like to deploy AMELIA booking application for a friend who has her own salon (hairdressers). It will be my first integration and not all employees are comfortable with new technologies. So, I try to identify the frictions with AMELIA booking system because except if I am wrong, if we depoy AMELIA, then all employees will have to use AMELIA to plan a new appointment. No paper will be allowed.
(1) Hairdressers now make new appointments by phone and write down appointments on paper. The customer calls, schedules the appointment and then give just his firstname. After AMELIA implementation, do you confirm that the salon owner and each employee will have to ask to the customer the firstname + lastname + email in order to create first a new customer and then be able to plan a new apointment ?
Not all employees are comfortable with new technologies. So I think there might be some friction for the employee and for the end customer if they have to ask for the customer's first name + last name + email.
I think it's fine to ask for the customers who decide to book online; but for the customer who still books by phone it is a pain from my perspective. How is it possible to keep these fields mandatory online but not ask for them on the phone (at least in a first period)?
(2) When an employee receives a call, she should be able to make the appointment for herself; but also for another employee if the customer on the phone wants an appointment with her colleague.
Is the only solution to use the AMELIA WordPress interface? Or is it possible to plan a new appointment from the employee panel for instance. It seems not to be possible because the employee panel seems to have a specific access for each employee. Is it correct? What yould be your recommendation please?
(3) Some employees give a haircut in 35 minutes and other employees do the same service in 45 minutes. How is it possible to offer the same service with a different duration depending on the employee selected?
Many thanks in advance for your help and support.
Hi, Frederic!
I've just noticed that there were two tickets with the same question.
I guess there's no need to duplicate the same information, therefore I will close this one.
Best Regards.