Implementing Zendesk for Rapid Deployment of Helpdesk Support and Guides

Originally published March 8, 2024.

Background

As a Technical Project Manager, I encountered a critical challenge in one of our projects. Our web application urgently required a robust helpdesk support feature, along with comprehensive user guides, and the solution needed to be implemented quickly.

Building an in-house helpdesk centre and content management system was estimated to take approximately two to three months. Our client could not accommodate such a lengthy development cycle because of time and budget constraints.

Balancing the need for rapid deployment with budget limitations became our primary objective.

Objective

The primary objective was to identify a solution that could be deployed within a week, remain cost-effective, and integrate easily with the existing web application while providing both helpdesk support and user guide functionality.

The project presented two key constraints:

1. Time constraints: The business required immediate action. Waiting for an extensive development cycle was not an option.
2. Budget constraints: Developing a custom solution from scratch could incur significant costs and potentially exceed the client's budget.

The solution: leveraging third-party helpdesk software

To address these challenges, we explored third-party helpdesk software providers. Our evaluation criteria included ease of use, feature coverage, scalability, customization, and cost-effectiveness.

The main contenders were:

• Zoho Desk: A comprehensive solution with a user-friendly interface.
• Freshdesk: A platform recognized for its support features, integrations, and scalability.
• Jira Service Management: A service management solution suited to structured support workflows.
• Zendesk for Service: A customer support platform offering helpdesk and knowledge-base capabilities.

After researching and comparing the available solutions, Zendesk emerged as the preferred option. The evaluation considered functionality, cost for a single agent, usability, and customization capabilities, particularly in comparison with Freshdesk and Zoho Desk.

Zendesk offered tools for building a customer service portal, knowledge base, and online community experience. Its configurable interface and customizable portal themes made it suitable for integrating the support experience with the existing application.

Freshdesk was considered for its affordability and scalability, while Zoho Desk offered another cost-conscious alternative. The final decision focused on finding the best balance between the client's immediate requirements, budget, customization needs, and future flexibility.

Implementation of Zendesk

Implementing Zendesk involved several steps to align the platform with the client's requirements.

1. Evaluation and setup

We assessed Zendesk's capabilities against the project requirements and configured the platform to support the client's helpdesk operations.

I was directly involved in the configuration, including setting up the initial help centre pages and support questions. This helped establish the structure needed for users to access assistance and find relevant information.

2. Integration with the existing web application

The configured helpdesk was prepared for integration with the existing web application. I handed over the relevant setup and requirements to the developers so they could carry the integration work forward and align the support experience with the product.

The objective was to provide a consistent experience without building a separate helpdesk system from scratch.

3. Customization of the web portal

The help centre needed to reflect the client's branding and visual identity.

Using Zendesk's configurable themes, we customized the portal's presentation, including colours, logos, and layout preferences. This helped the support experience feel more consistent with the existing application.

4. Training and configuration

The client's administrators received training on managing and publishing user guides through Zendesk. I also supported the configuration of the helpdesk's custom domain so that users could access the support portal through the client's chosen URL.

Configuring a custom domain

The original implementation included the following general configuration workflow.

Step 1: Add a custom domain

In Zendesk, navigate to the account's domain settings and add the intended custom domain, for example:

help.mycompany.com

Step 2: Configure the required DNS records

Use the exact record type and value shown in the current Zendesk account and follow the current vendor instructions. DNS requirements depend on the product configuration. Do not copy generic TXT or SPF records from an unrelated example; SPF records are for email authentication and are not a universal helpdesk-domain verification method.

Step 3: Verify domain ownership

Add the verification record provided by Zendesk to establish domain ownership, following the instructions displayed in the account.

Step 4: Update Zendesk settings

Return to the domain settings and configure the custom domain as the primary domain where supported.

Step 5: Test the configuration

Open the chosen custom domain and verify that the helpdesk is accessible and behaving as expected.

Technical note: This article was originally published in March 2024. Zendesk's current interface and domain-verification requirements may differ, so verify the latest official instructions before following these steps in a live environment.

Benefits and business value

Choosing Zendesk provided a practical way to introduce helpdesk and knowledge-base functionality within the project's constraints.

1. Cost considerations

Using an established platform avoided the need to develop and maintain a custom helpdesk and content management system. This reduced the amount of new development required and aligned the approach with the client's budget constraints.

2. Time efficiency

The solution was selected to meet an urgent deployment objective, avoiding the estimated two-to-three-month development cycle associated with building the equivalent functionality in-house.

3. Improved support experience

The helpdesk and knowledge base provided a dedicated location for support requests and user guides, making assistance and self-service information more accessible.

4. Better use of engineering resources

By leveraging a third-party platform, the engineering team could remain focused on the core product rather than allocating significant development effort to supporting functionality.

5. Flexibility for future growth

The configurable platform provided room to adapt the support portal and knowledge base as the application's requirements evolved.

Conclusion

This project demonstrates the value of strategic decision-making in technology project management. Faced with tight timelines and budget constraints, we evaluated existing solutions, selected a suitable third-party platform, configured Zendesk, and coordinated the work required to integrate it with the existing application.

The experience reinforced the importance of flexibility, careful planning, and making informed build-versus-buy decisions.

The central lesson: Effective technology delivery is not always about building more software. Sometimes, the best outcome comes from selecting the right existing platform, configuring it to meet the business need, and delivering the required capability without diverting resources from the core product.

For the project scope and my role, see the Zendesk helpdesk case study.