Freshdesk Tutorial for New Admins
This Freshdesk tutorial is four steps, in this order. Most bad Freshdesk setups are bad because somebody did step three first.
Before this Freshdesk tutorial changes a single setting
Decide one thing: which email address is support. Not three addresses, one. If you currently have help@, support@ and info@ all going to a shared mailbox, pick the one you'll publish and forward the others into it.
Everything downstream depends on this. Statuses, automations, reporting, all of it assumes there's one front door.
Step one: connect email
Freshdesk gives you a system address in the form yourcompany.freshdesk.com. You don't publish that. You set up a support email address you own and forward it in.
That last check is the one people skip. Do it. Broken threading is the single most common cause of a queue that fills up with the same conversation three times.
Step two: one pipeline of statuses
Resist the urge to build a taxonomy. Start with what Freshdesk gives you: Open, Pending, Resolved, Closed. Then add exactly one thing if you need it, a status that means you're waiting on the customer.
Why that one matters is covered in ticket statuses, but the short version is that it stops customer delays from counting against your response times.
Do the same restraint exercise with priorities. Four levels exist. Write down, in one sentence each, what qualifies for Urgent and High. If you cannot, everything becomes High within a fortnight.
Step three: your first three automations
Only three. You can add more in a month once you know what actually happens in your queue.
Freshdesk splits automation into rules that fire on ticket creation, on updates, and on a time schedule. Build each of the three above in the right one of those and test with a real ticket before you trust it. More patterns in the automations guide.
Step four: your first five articles
Last, not first. You can't guess what to document. After two weeks of live tickets you'll not have to guess.
Sort your resolved tickets by subject, find the five things you answered most, and write those. Short. One problem per article, with the actual steps and the actual error text so search finds it.
Then wire them in: link them from the auto-reply, surface them in the portal, and paste them into canned responses so agents send the article rather than retyping the answer. That's when a knowledge base starts paying rent.
What to leave until month two
SLA policies, business hours, custom fields, round robin, integrations, the customer portal theme, reporting dashboards.
None of that's wasted work. All of it's easier when you have a month of real tickets telling you what your queue actually looks like, rather than a month of assumptions baked into settings nobody remembers configuring.
Frequently asked questions
Is there a Freshdesk getting started path for beginners?
Yes. Freshdesk for beginners starts with the email channel, then one pipeline of statuses, then three automations. Freshworks Academy has free Freshdesk training that follows roughly that order.
How long does this Freshdesk tutorial take to work through?
Email connection and a working queue takes an afternoon. The first automations take another hour. Articles take as long as writing five short pages takes you.
Should I import my old tickets?
Usually no, or only the open ones. Historic closed tickets rarely get read, and importing them is where duplicate contacts get created.
Do I need the paid plan to start?
Not to start. The free tier gives you ticketing, a knowledge base and basic reporting. SLAs, business hours and automation depth sit on the paid tiers, which is what most teams eventually upgrade for.
What breaks most often in a new setup?
Email threading and DNS records. Test both with a real message from outside your organisation before you go live.
One thing no setup guide fixes
Roughly a tenth of every support queue is the same request more than once. Ticket Merger spots those and merges them from day one.
Start free trial14-day free trial. No credit card required.