How to Set Up a Help Desk from Scratch (Free Template Included)

When your support volume is 5 emails a day, your inbox works fine. You read the email, reply, and move on. But somewhere between 10 and 30 tickets per day, the inbox model breaks. Emails get buried. Follow-ups slip through the cracks. Two people accidentally respond to the same customer with conflicting answers. A customer who emailed three days ago gets forgotten because a flood of new emails pushed their message off the first page.

A helpdesk fixes all of this. It is not just a fancy inbox -- it is a system that ensures every customer request is tracked, assigned, prioritized, and resolved within a defined timeframe. This guide walks through setting one up from scratch, with specific configurations you can copy.

Ticket categories determine how requests are routed and prioritized. Do not overcomplicate this -- start with 5-8 categories and add more as patterns emerge. Here is a template that works for most small businesses:

Billing & Payments -- Invoice questions, payment issues, refund requests, subscription changes Technical Support -- Product issues, bugs, error messages, how-to questions Account Management -- Password resets, account access, profile updates, permission changes Sales & Pre-Sales -- Product questions from prospects, pricing inquiries, demo requests Feature Requests -- Customer suggestions for new features or improvements General Inquiry -- Everything else that does not fit the above categories

For service businesses, add categories specific to your industry: Scheduling -- Appointment changes, cancellations, rescheduling Field Service -- Job status inquiries, on-site issues, follow-up requests

Each category should have a default assignee or team. This automatic routing eliminates the biggest bottleneck in most support workflows: figuring out who should handle each request.

Priority levels define how urgently each ticket needs attention. SLA rules put time limits on those priorities:

Urgent (P1): Customer's business is down or blocked. First response within 1 hour. Resolution target: 4 hours.

High (P2): Significant impact but workaround exists. First response within 4 hours. Resolution target: 24 hours.

Medium (P3): Normal business request. First response within 8 business hours. Resolution target: 48 hours.

Low (P4): Nice-to-have, no business impact. First response within 24 business hours. Resolution target: 5 business days.

The critical metric is first response time. Research consistently shows that first response time has a larger impact on customer satisfaction than resolution time. A fast acknowledgment that says 'we are looking into this' is better than silence for 24 hours followed by a complete resolution.

Canned responses are pre-written replies for common questions. They are the single highest-ROI setup task for a helpdesk. Start with these 10:

1. Acknowledgment: 'Thanks for reaching out. We have received your request and are looking into it.' 2. Password reset: Step-by-step instructions for resetting their password. 3. Billing question redirect: 'I have forwarded your billing question to our accounts team.' 4. Refund confirmation: 'Your refund of [amount] has been processed.' 5. Feature request received: 'Thanks for the suggestion. I have logged this as a feature request.' 6. Bug report received: 'Thanks for reporting this. I have escalated it to our engineering team.' 7. Resolution confirmation: 'This issue has been resolved. [Brief explanation].' 8. Scheduling confirmation: 'Your appointment has been [booked/rescheduled] for [date/time].' 9. Follow-up check-in: 'I wanted to follow up on your recent support request.' 10. Close ticket: 'It looks like this issue has been resolved. I am closing this ticket.'

Each canned response should include merge fields for customer name, ticket number, and relevant details.

A customer portal lets customers submit tickets, check status, and find answers without emailing you. This deflects 20-40% of support volume.

Your customer portal needs three things:

Ticket submission form: A simple form with fields for subject, category (dropdown), priority (optional), and description. Do not make customers fill out 10 fields.

Ticket status tracking: Let customers see their open tickets, the current status, and any responses. This eliminates 'just checking in' emails.

Knowledge base: Even 10-20 articles covering the most common questions will deflect a meaningful percentage of tickets. Write articles in plain language, include screenshots where helpful, and keep each article focused on solving one specific problem.

Helpdesk automations eliminate repetitive manual work. Configure these from day one:

Auto-acknowledgment: When a ticket is created, send an automatic reply confirming receipt.

Auto-assignment: Route tickets to the right person based on category.

SLA escalation: If a ticket breaches its first-response SLA, automatically escalate to the team lead.

Stale ticket reminder: If a ticket has had no activity for 48 hours, send an internal reminder.

Auto-close after resolution: If a customer does not respond within 5 business days after resolution, automatically close the ticket.

CSAT survey: After a ticket is resolved, send a brief satisfaction survey (1-3 questions maximum).