How to set up a help desk for your small business
Seven steps from blank account to a measured support workflow. Total time around two weeks of part time work, no technical expertise required.
The seven steps
Choose your help desk and create the account
Use the requirement matcher on the homepage. Decide between free and paid based on team size and channel mix. Sign up using your shared support email so the trial is on the account that will own it long term.
- Run the requirement matcher and pick a top 3
- Sign up for free trials for two of them in parallel
- Use a generic admin email like ops@ rather than a personal address
- Invite a second team member as admin for redundancy
- Bookmark the vendor pricing page so you can reference exact tier limits
Sign up for two trials in parallel for the first 48 hours. You will know within a day which one feels right for your team.
Connect your support email and channels
Forward your existing support@ inbox into the help desk. Verify SPF and DKIM so outbound replies do not land in spam. Connect any chat, social, or phone channels you actually plan to use.
- Set up email forwarding from [email protected]
- Add SPF and DKIM records pointing to your help desk's mail server
- Send a test email from a personal account and verify it creates a ticket
- Add chat widget code to your site if using chat
- Verify Facebook, X, or Instagram if you handle social tickets
Test the full round trip: customer email in, agent reply out, customer receives the reply, customer replies back, ticket reopens correctly. Most setup bugs hide in step four of that loop.
Invite agents and set roles
Add every agent who will reply to tickets. Assign roles thoughtfully. Most help desks distinguish between admin (settings access), agent (reply access), and light agent or collaborator (read only or internal note only).
- Add each agent with their work email
- Assign at least two admins (you plus one backup)
- Set timezone per agent so reporting works correctly
- Configure default signatures for each agent
- Set business hours for the team
Use light agent or collaborator licenses (often free) for engineers or product managers who comment internally but do not reply to customers. This saves money on per agent fees.
Seed the knowledge base with 20 articles
Pull the 20 most common questions agents currently answer manually. Write each as a 200 to 400 word article with screenshots where helpful. Publish the public ones, keep policy articles internal.
- Audit your sent items folder for the top 20 repeated answers
- Write each article in plain language, no marketing fluff
- Add screenshots, GIFs, or short videos for steps with UI
- Tag articles consistently for search relevance
- Link from your help desk auto reply email so customers see them
Knowledge base ROI is non linear. The first 20 articles cut tickets the most. Article 21 onwards is incremental. Do not over invest before you see real deflection data.
Configure automations and SLAs
Three automation rules pay for themselves immediately: assign by topic, auto acknowledge on creation, escalate when overdue. Set SLA targets that match your real capacity, not aspirational targets.
- Auto acknowledge on ticket creation with expected response time
- Auto assign by tag, channel, or category
- Escalate when first response SLA is at 80% breach
- Set business hour aware SLAs (do not measure against weekends)
- Add a satisfaction survey on resolution
Set your initial SLA at first response under 8 business hours, resolution under 3 business days. Tighten only after you have hit those for two weeks straight.
Train the team and run a soft launch
A 90 minute workshop covers most of what new agents need. Run a soft launch where one or two agents handle live tickets for the first three days while others shadow. Capture friction in a shared doc.
- Run a 90 minute walkthrough with the whole team
- Cover ticket lifecycle, internal notes, macros, and reassignment
- Pair one experienced agent with each newer agent for shadowing
- Document friction points in a shared issues log
- Schedule a 30 min retro at end of week one
Do not let an agent reply solo until they have observed at least 10 tickets being handled by a peer. The cost of a bad early reply outweighs any saving in onboarding time.
Go live, measure, and iterate
Switch your support email forwarding to the help desk and turn on customer facing channels. From day one, watch first response time, resolution time, and CSAT. Run a weekly review for the first month.
- Update support@ forwarding to point at help desk only
- Add help center link to your site footer and product UI
- Announce new help desk to customers via email or in app banner
- Set up a weekly reporting digest emailed to admins
- Schedule a 30 day retro to decide on next features
Do not turn on AI features in the first month. Establish a baseline of human response times first. AI deflection rates only become meaningful once you know what you are deflecting from.
Week one metrics to watch
Five mistakes to avoid in your first month
Aspirational SLAs that the team cannot hit, leading to demoralised agents and gamed metrics. Set realistic targets first.
Skipping the knowledge base because it feels like extra work. The first 20 articles deflect 30 to 50% of repeat tickets.
Turning on every channel at launch. Start with email, add chat in week two, add social or phone only when demand is real.
Running the team without internal notes discipline. Make it a rule that every customer reply has at least one internal note above it.
Ignoring CSAT data because the sample is small. Even 20 ratings tell you a lot if you read the comments.