Hi, Gerhard 

Sorry for the delay

We don't have a built- in way for this yet. 

We plan to create a Membership feature soon, that will be able to "restrict" pages only for members, amongst other things.

But i can't say an ETA on it.

Please feel free to search through our feature suggestion page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

The only way to currently achieve this is with a bit of a workaround.  I have two ideas.

1.

You can either create a WP page with a password, that contains Amelia booking shortcode, maybe only for this particular Service.

For example [ameliastepbooking service=1]  if you want to show the booking form for the service with ID 1.

But you would manually somehow have to send the password to the client who can then use it to view the page;

2.

Alternatively,  for example, you can set up a Membership plugin, 

Then, you could use the "User role Editor" plugin to create additional user roles, only for certain customers. With the Membership plugin, you could limit access to certain pages for certain user roles. 

For example, a custom role "VIP" would have access to page 1 where you can place a shortcode for a  service/package offered only for them. 

Then, another custom role "Level 1" would have access to page2 where [ameliacatalog package=2] is placed, which would have different prices, and so on...

-

Let me know how all that sounds. Thank you

Hi, Gerhard 

No problem at all.

Now i can see what your goal is, thank you for the clarification, i misunderstood a bit at first.

-

I might suggest another workaround for this.

What you could do is, you can create a specific service for this purpose.

Then you can make it invisible for the front end; so it can only be booked from back-end.

Then an Amelia manager, or Amelia employee, or Admin, can fill out all the necessary details at back-end, select time slot, employee etc;

-

Then you can create a custom notification specifically per service;

For example, for this service you can add description, and the guide for the customer, how they can pay;

Now, from the back-end , Amelia can only reserve the payment as "on-site";  you can't enter customer card details >

but as i said, you could send them instructions on how to pay in the notification;

such as a bank account number, or something similar;

Then they could maybe do a bank transfer or something like that.

-

You can also add custom HTML in notifications, to create certain design or to add a link, if needed.

-

Additionaly, you could choose to set default appointment status as pending > and once you confirm they paid, you can switch to approved. ( If needed)

That is the best i could think of with the current Amelia capabilities.

Let me know how that sounds. Thank you