Zendesk's feature removal process includes several key milestones to ensure users are well-informed. The first milestone is the announcement, where Zendesk creates an article in the Announcement section of the Help Center and may use other communication methods like alerts. After the announcement, no new improvements are made to the feature.
The next milestone is the end of development, where Zendesk stops resolving most bugs but continues to address major functionality issues. The final milestone is the removal date, when the feature is either removed or users are migrated to new functionality.
Zendesk provides varying notice periods for feature removal based on the effort and impact of the project. For low effort and impact projects, a 3-month notice is given. Medium effort and impact projects receive a 6-9 month notice, while high…
Zendesk uses multiple communication methods to inform users about feature removal. Initially, an article is published in the Announcement section of the Help Center. Additionally, alerts may be sent directly to your account or within the feature…
Yes, there are exceptions to Zendesk's feature removal timelines. Features in early access programs or betas may not follow the standard notice periods. Additionally, if a feature's removal is necessary for security reasons or due to externally…
After Zendesk announces a feature removal, no further improvements or new functionalities are added to the deprecated feature. The focus shifts to resolving major breakages and maintaining documentation. Support is limited to issues related to the…