Skip to main content

Hi,

Looking for some advice and guidance for appointment bookings via PSO.

We use FSM and request appointment bookings from PSO. 
Some appointment requests are what we refer to as 'Rebook'. This is when a task is already scheduled or fixed committed and we look for new appointment bookings.
When we do this all the scheduling data is reset. This therefore means any current scheduling data is removed and is causing a few issues, when customers then want to keep the existing appointment.

Is there a way of searching for new appointment bookings, retain the existing appointment data and only update when a new booking has been accepted?

It might be worth adding we're be using a customised version of the perform_threesixty_appt_request MPM. 

Any advice will be welcomed.

Ady

Hi Ady,

This sounds like it might be a bug, can you please raise a support case under FSM?

Thanks

Phil

Hi @Phil Lamerton,

I have also processed a task using the baseline MPM’s and I get the same outcome when requesting appointments that’s been accepted.

Happy to raise as a bug though.

 

Ady

Actually this is the baseline behavior since -1 is sent as the activitystatus id for appointment requests. Further clarifications sent through the Support case. 

Hi @Sajith Anushan,

 

Thank you for picking it up.

Working through the next steps with the our processes now.

 

Ady

Terms & ConditionsCookie settings