Okay
  Public Ticket #3395276
Feature clarification
Closed

Comments

  • James Cobalt started the conversation

    What if we don't want customers to pick the employee providing the service? The emphasis for our business is on the service, not the individual (or individuals) providing it. Some services need specific employees to operate, while others just need the front desk employee available. I saw a ticket that suggested hiding the employee selection with CSS, but from my brief testing it appears it just selects the first employee in the dropdown; meaning if two employees can do a service and two different parties try to book it for the same time, it won't work as it'll try to select the same employee on both.

    Any plans to add an abstraction layer on top of employees so you can use categories of employees instead? e.g. a service that needs 1 employee from Category A but it doesn't matter which employee

  •  1,499
    Uroš replied

    Hello James,

    Thank you for reaching out to us.

    On the first step of the booking form, the employee field can be hidden from the Amelia/Customize page as that is a native function. The other parts of the form (congratulations step) would require this to be done with CSS.

    Hope this helps you.

    Please let me know if you have any other questions.

    Kind Regards, 

    Uros Jovanovic
    [email protected]

    Rate my support

    wpDataTables: FAQ | Facebook | Twitter | InstagramFront-end and back-end demo | Docs

    Amelia: FAQ | Facebook | Twitter | InstagramAmelia demo sites | Docs | Discord Community

    You can try wpDataTables add-ons before purchasing on these sandbox sites:

    Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables