First off, I don't intend this topic to be controversial, although I am certain it will be. Apologies in advance.
As we know, overuse of the GAC program led to the changes that introduced DAS. This brought with it the notion that users have to wait, just not in the harmful environment (i.e. queue).
Now the DAS is a digital proposition, I am wondering if the 'equal access' component should be taken a step further. Guests who physically wait in lines cannot wait in two lines at the same time (obviously) - but DAS users can; one virtual line, and one physical line.
Surely a simple solution to this would be to require a MB/ticket scan at the queue lines for Standby guests, which simply checks if the guest has an outstanding DAS return time and denies entry if so? The guest could then either cancel their DAS reservation and join the physical queue for the attraction, or cancel the DAS reservation and set up a new DAS reservation for that attraction.
Maybe it's a solution looking for a problem, and the implementation costs / inconvenience on other guests would be significant, but just wondered if anyone had thoughts on the idea ignoring those obvious overheads? To me, it seems like an obvious next step.
As we know, overuse of the GAC program led to the changes that introduced DAS. This brought with it the notion that users have to wait, just not in the harmful environment (i.e. queue).
Now the DAS is a digital proposition, I am wondering if the 'equal access' component should be taken a step further. Guests who physically wait in lines cannot wait in two lines at the same time (obviously) - but DAS users can; one virtual line, and one physical line.
Surely a simple solution to this would be to require a MB/ticket scan at the queue lines for Standby guests, which simply checks if the guest has an outstanding DAS return time and denies entry if so? The guest could then either cancel their DAS reservation and join the physical queue for the attraction, or cancel the DAS reservation and set up a new DAS reservation for that attraction.
Maybe it's a solution looking for a problem, and the implementation costs / inconvenience on other guests would be significant, but just wondered if anyone had thoughts on the idea ignoring those obvious overheads? To me, it seems like an obvious next step.