Handling inconsistent services VS service items
Services, service items, and reservation slots are specified with code numbers in a Clarity URL.
It is possible to have a URL containing the number for a service, but a service item under a different service. In other words, a URL can contain a number for Service A but a service item under Service B. When this happens, the page will direct to the Service Item that is being specified (under Service B, in this example).
It seems strange that the system doesn't recognize a potentially ambiguous request is being put to the server. An error or warning message that the user is sending an inconsistent request to the server might be more useful that just sending the user to the service item's page.
Xander
shared this idea
As part of our ongoing efforts to build the best feedback platform for you, ideas that have not received a vote or comment in the past year have been set as “Archived.” Please feel free to resubmit this idea using this submission guide.