# Business Case: Migrate Customer Support to Zendesk Decision owner: VP of Customer Experience Decision horizon: First 90 days First-year budget cap: $15,000 Success metric: Reduce average first-response time from 8 hours to under 2 hours within 90 days. ## 1. EXECUTIVE SUMMARY The customer support team should migrate from email-only support to a dedicated helpdesk platform, Zendesk, to reduce response delays and improve operational visibility. The recommended path is a phased implementation using existing staff, with the first-year investment kept within the $15,000 budget cap and no additional headcount. This approach addresses the limitations of email-based workflows while allowing the team to adopt the new process without disrupting service. Success will be measured by reducing average first-response time from 8 hours to under 2 hours within 90 days. ## 2. SITUATION ANALYSIS ### Current state Customer support is managed through email, which limits visibility into incoming requests, ownership, priorities, and response performance. As volume grows, manual triage and follow-up create delays and make it difficult to identify unresolved work. ### Pain / opportunity The current process creates three business problems: * Slow customer response: An 8-hour average first-response time creates avoidable customer friction. * Limited operational control: Leaders lack a consistent view of workload, backlog, and team performance. * Inefficient use of existing capacity: Agents spend time organizing and tracking requests rather than resolving them. A dedicated helpdesk can centralize tickets, establish clear ownership, and automate routine workflows. The opportunity is to improve response speed without increasing headcount. ### Why act now The team is already operating at the limits of an email-only workflow. Delaying the change preserves the current response-time gap and makes future migration more disruptive. Acting now creates a measurable improvement opportunity within the 90-day target. ## 3. OPTIONS CONSIDERED | Option | Outcome | Effort level | Primary risk | | --- | --- | --- | --- | | A — Do nothing (baseline) | Retain the current email process with no implementation cost. Response performance is likely to remain constrained by manual workflows. | Low | Continued slow responses and limited visibility into support operations. | | B — Proposed initiative: Zendesk migration | Centralize support requests, introduce ticket ownership and prioritization, and establish reporting against the first-response target. | Medium | Adoption and implementation may temporarily reduce team capacity. | | C — Scaled-down alternative: Email process optimization | Improve the existing workflow through shared inbox rules, templates, manual triage, and basic reporting. | Low–Medium | Limited scalability and a lower likelihood of achieving sustained response times under 2 hours. | Constraint: All options must operate within the $15,000 first-year budget cap and use existing headcount. Option B should therefore prioritize essential functionality and phased adoption rather than a broad, high-cost rollout. ## 4. RECOMMENDATION Recommend Option B — Migrate to Zendesk through a phased implementation. This option provides the strongest path to achieving the success metric because it addresses the underlying workflow limitations rather than only optimizing the existing email process. A focused rollout can improve response speed, create measurable accountability, and establish a scalable support foundation while respecting the budget cap and no-additional-headcount constraint. ## 5. IMPLEMENTATION ROADMAP | Timing | Action | Expected outcome | | --- | --- | --- | | Week 1–2 | Confirm requirements, support categories, current response-time baseline, and budget allocation. | Agreed scope and measurable starting point. | | Week 2–3 | Configure Zendesk, including email intake, ticket routing, priorities, and essential reporting. | Core helpdesk workflow ready for testing. | | Week 3–4 | Pilot with a small group of agents; test routing, escalation, and customer communications. | Key workflow issues identified before full rollout. | | Month 2 | Train the full team and transition support operations in phases. | Team adoption with minimal disruption to service. | | Month 2–3 | Monitor first-response time, backlog, and adoption; refine workflows and staffing allocation within existing capacity. | Performance improvement and operational stability. | | Day 90 | Review results against the target and confirm the next phase of optimization. | Decision on whether the initiative has met its success criteria. | ## 6. RISK & MITIGATION | Risk | Likelihood | Impact | Mitigation | | --- | --- | --- | --- | | Team adoption is slower than expected. | Medium | High | Use a phased rollout, provide focused training, and establish clear ownership for new workflows. | | Implementation exceeds the budget cap. | Medium | High | Prioritize essential features, approve scope before configuration, and track first-year costs against the $15,000 limit. | | Response time does not improve enough within 90 days. | Medium | High | Establish a baseline, review performance weekly, identify bottlenecks, and adjust routing and priorities using existing headcount. | ## 7. DECISION REQUEST Approval is requested to proceed with the phased Zendesk migration, with a first-year budget not exceeding $15,000 and no additional headcount. Early approval will allow the team to begin configuration and pilot testing immediately, creating a clear path to the target of under 2 hours average first-response time within 90 days.