Brendan O'Driscoll

I'd like to add my name to the list of requests for redirect functionality.

We recently migrated to Zendesk and, having accepted that links would break as a result, put in the work to update those across our digital assets. This is not something that we could afford to do twice.

We also implemented the solution indicated here to a small extent: https://support.zendesk.com/hc/en-us/articles/217958367-Redirecting-traffic-from-deleted-Help-Center-articles (it's a temporary fix for some URLs but is certainly not scalable). What happens when the URL strings in the .JS get to 100+ or more? I image the pressure that might put on page loads.

Going forward, there's a more pressing matter: we need the ability to redirect users to new updated articles that have replaced older content. These articles are referenced everywhere (in our blogs, nurture campaigns, and even our product's code!). Our customers also bookmark a lot of this same material for reference in internal wikis, etc.

Article versioning (while great) does not address the need to replace a set of documents wholesale. We need the ability to manage links more broadly.