This object is in archive!
Overbooked Items
Answered
I had an order 1242558 that had paid their deposit and was sending us a check for the balance. So, I had confirmed, scheduled and sent PL back in March. My co-worker made a changed on her order 1281169 and added 2 All Silver Confessional Chairs. We only have 4 in Silver total so this created an overbooking. However, it did not appear overbooked for her order but mine. I only noticed because the client made a change. Should it not create the overbooking for the order 1281169?
The same question
There is something in the system called "priority" when it comes to conflict checking. When a lead is booked first, it gets a higher "priority" than a new lead that comes along later and creates a conflict. We only flag the lead that created the conflict with lower priority.
Priority isn't just based on book date though. Making an edit to a lead can change it's priority. The issue is that in certain scenarios, the change you make may not lower the priority of the lead you are looking at (ex: edits to the setup window), and the conflict checking process that is run, runs as you save the lead, in the background. So the software has a background process that runs when you make certain changes, but it takes some time because it has to check a lot of different scenarios. It eventually catches the conflict with the lower priority lead and flags that lead.
We'll use this example you gave as a scenario to consider how to best improve this area of the software.
There is something in the system called "priority" when it comes to conflict checking. When a lead is booked first, it gets a higher "priority" than a new lead that comes along later and creates a conflict. We only flag the lead that created the conflict with lower priority.
Priority isn't just based on book date though. Making an edit to a lead can change it's priority. The issue is that in certain scenarios, the change you make may not lower the priority of the lead you are looking at (ex: edits to the setup window), and the conflict checking process that is run, runs as you save the lead, in the background. So the software has a background process that runs when you make certain changes, but it takes some time because it has to check a lot of different scenarios. It eventually catches the conflict with the lower priority lead and flags that lead.
We'll use this example you gave as a scenario to consider how to best improve this area of the software.
This bug has been fixed. It was affecting hold times for accessories in certain scenarios.
This bug has been fixed. It was affecting hold times for accessories in certain scenarios.
Replies have been locked on this page!