The survey itself is free to configure. Satisfaction reports, though, sit on Freshdesk Growth and above — on the free plan you can collect ratings and barely see them.

That mismatch is worth knowing before you spend a week on survey design.

How does Freshdesk CSAT actually work?

When an agent resolves a ticket, Freshdesk can send an email with a question and a rating scale. The response is stored on the ticket and aggregated into a satisfaction score. The default scale has four faces — very unhappy to very happy — and by convention anything at the top two counts as positive.

Configure it under Admin > Productivity > Email notifications or the CSAT section, depending on your tenant version. You can edit the question text and add an optional comment box.

Step 1: Delay the survey instead of firing on solve

The default sends on resolve. Change the trigger to send a few hours later — 3 to 4 hours is a good starting point for email support, longer for anything with a shipping or deployment step.

Why: on resolve, the customer has read a message but hasn’t confirmed the fix worked. They rate the interaction, not the outcome. A few hours of delay means they’ve either used the product successfully or hit the same bug again, and both produce a more honest score.

Step 2: Keep one question and make it concrete

The default “How would you rate the support you received?” gets answered on mood. A better wording: “Was your issue resolved?” with the same faces. It’s answerable, and it produces data you can act on.

Add the comment box but don’t require it. Required comments drop response rates hard. The comments you do get will skew negative — that’s normal and still useful.

Step 3: Skip the survey where it’s noise

Not every ticket deserves a survey. Configure the CSAT to skip:

• Tickets resolved automatically by a rule with no human reply
• Tickets tagged spam or internal
• Tickets resolved within 10 minutes of creation (usually simple how-tos)

Every survey sent to a ticket nobody worked on lowers your average and tells you nothing.

Step 4: Read the score correctly

A 85% satisfaction rate on 40 responses a month has a wide error margin. Treating month-to-month swings as signal produces pointless panic. Look at rolling three-month windows, and look at the response count alongside the percentage.

Low response volume is itself the finding. If you send 400 surveys and get 18 responses, the sample is unrepresentative — usually unhappy customers are over-represented, because happy ones don’t bother.

What’s the realistic plan requirement?

If CSAT matters to your reporting, you’re on Growth ($15-19/agent/month) or above. Collecting data you can’t read is a common and avoidable trap on the free tier.

Does a bad CSAT score mean bad support?

Often it means slow first response, not bad agents. Split the data by first-response time before drawing conclusions. Teams I’ve looked at usually find that tickets answered within an hour score double those answered the next day, regardless of whether the answer was good.

That reframes the fix: it’s a staffing and routing problem, not a training problem.

When should you not run CSAT at all?

If you’re a two-person team with ten tickets a week, talk to your customers directly instead. A survey at that volume adds process and produces statistically meaningless numbers. Also skip CSAT if you’re not going to act on it — asking for feedback and ignoring it costs more goodwill than never asking.

Quick Summary

• Delay CSAT by 3-4 hours after resolve; the default timing inflates neutral scores.
• Ask “Was your issue resolved?” rather than rating the interaction.
• Exclude auto-resolved and spam tickets or your average is polluted.
• Satisfaction reports need Growth; on Free you collect data you can’t analyse.
• Judge scores on rolling three-month windows and response counts.

That’s the short answer. The interesting part is where the gap narrows.

How do the two pricing models actually differ?

Freshdesk sells seats on a per-agent basis, tiered by features. Zendesk sells Suite bundles at a per-agent rate that includes support, chat, voice and knowledge base from the first paid tier. Neither charges per ticket, and neither charges for end customers.

Prices move every year and Zendesk quotes enterprise deals privately, so treat these as list anchors, not invoices. Still, the ratio stays roughly 3:1 at entry level.

Worked example: what does 5 agents cost per year?

Five agents on Freshdesk Growth at $15 runs $75/month, or $900/year billed monthly. The same five on Zendesk Suite Team at $55 is $275/month — $3,300/year. Difference: $2,400 a year, which is one junior support hire in a lot of markets.

At 15 agents the gap grows to roughly $7,200/year. Freshdesk Pro at $49 for 15 seats is $735/month; Zendesk Suite Growth at $89 is $1,335/month.

Numbers alone don’t decide it. Look at what you’re buying with the extra money.

Where does Zendesk actually earn the premium?

Customization. Zendesk’s ticket forms, custom objects, views and triggers are more granular, and its API is the one every marketplace integration targets first. If you’re building internal tooling around support data, Zendesk gets you there with fewer hacks.

Voice is the other one. Zendesk Suite bundles Talk from the base tier; on Freshdesk you either buy Contact Center separately or stitch in a third-party telephony provider.

Reporting is the third. Zendesk Explore ships prebuilt dashboards for CSAT, agent workload and first-reply time that a manager can read on day one. Freshdesk’s canned reports are adequate and its custom report builder sits on higher tiers.

Who needs this: teams with 10+ agents, a support operations person, and a contact center. Who doesn’t: a startup answering 40 tickets a day.

What are the hidden costs on both sides?

Neither vendor hides fees, but both route you through add-ons.

• AI features. Freshdesk Freddy and Zendesk AI both bill separately or sit on higher tiers. Budget for it explicitly or your agents will write every reply by hand.
• Onboarding. Freshdesk partners quote setup projects in the low four figures; Zendesk’s implementation partner ecosystem is larger and pricier. A 5-agent team can self-serve Freshdesk in a week and will struggle to self-serve Zendesk in the same time.
• Migration away. Exporting tickets is possible from both, but attachments and custom field history degrade. Plan the exit before you import.

Which one should you pick in 2026?

Pick Freshdesk if: you’re under about 20 agents, you handle mostly email, you want to be live this week, and price matters to the board. Its free tier also makes it a low-risk test.

Pick Zendesk if: you run phone support, you need custom objects, or you already have a Zendesk-shaped integration roadmap. The premium buys operational depth, and at 30+ agents the per-seat difference is noise next to headcount.

The mistake I’d avoid is choosing Zendesk because it’s the brand everyone names. A three-person team paying $165/month for Suite Team is paying for customization it will never open.

Can you mix them?

Yes, and some teams do — Freshdesk for email and chat, Zendesk or a dedicated tool for phone. It works, but you pay twice for knowledge bases and reporting, and agents juggle two inboxes. Only worth it if voice volume is genuinely separate from digital volume.

Quick Summary

• Freshdesk entry paid tier is around $15 per agent per month; Zendesk Suite Team around $55.
• For 5 agents the annual gap is roughly $2,400; for 15 agents around $7,200.
• Zendesk’s premium buys custom objects, bundled voice and stronger reporting.
• Freshdesk’s free tier for 2 agents is permanent, Zendesk’s is a 14-day trial.
• Under ~20 agents handling email, Freshdesk is the safer default.

What does the Freshdesk free plan actually include?

The free tier is a real helpdesk, not a trial. It ships with the Agent Desk, email and web widget channels, unlimited ticket history, canned responses, and a knowledge base you can open to customers. The hard limits: 2 agents, 1,000 solution articles is fine but reporting is cut to a few canned views, and every workflow automation is locked behind paid plans.

That last one bites. A free Freshdesk account can’t auto-assign tickets, can’t trigger emails on status change, and can’t escalate breaches. You’ll do that by hand or with tags.

Who this fits: a founder and a co-founder splitting support, a two-person agency, a side project. Who it doesn’t: anyone with a third teammate, or a team drowning in 200 tickets a week.

Step 1: Create the account and skip the tour

Go to freshdesk.com, pick Sign up for free, and use your support email address as the login. The signup wizard asks for a portal name — that becomes your subdomain, like yourcompany.freshdesk.com, and you cannot change it later without contacting support. Same for the email address on the account, so use a real shared mailbox, not your personal Gmail.

Close the onboarding checklist as soon as it appears. You’ll set things up directly.

Step 2: Forward your support mailbox, don’t create a new one

Freshdesk works best when it reads an inbox you already have, like support@yourdomain.com. In Admin > Channels > Email > New Email, choose Forwarding and copy the Freshdesk forwarding address. Then set a rule in Google Workspace or Microsoft 365 that forwards every incoming message to it and keeps a copy in the original inbox.

Keep the copy. If Freshdesk ever misses a thread, or you outgrow the free plan, you still have the raw record. I’ve seen teams lose an entire month of invoices this way.

One gotcha: Freshdesk detects loops by the From address. If your forwarder rewrites the sender to your own address, replies bounce. Test with one real email before telling customers.

Step 3: Fill in the ticket form fields people actually use

Default fields are Subject, Description, Priority, Status, Source. Add Type and rename it to match your world — Bug, Billing, Feature Request is fine for a SaaS, Delivery Issue or Refund for e-commerce. Two custom fields is plenty.

Expected first-week setup time: 5 minutes. Skip the rest. Teams spend hours building 14 fields and then never read them.

Step 4: Set an SLA you can actually keep

Admin > Workflows > SLA Policies. The free plan allows one SLA policy with multiple targets. Set first-response at 8 business hours and resolution at 48, then define business hours as Monday–Friday, 9:00–18:00 in your timezone.

Here’s the honest problem: without automation rules, Freshdesk will color a breaching ticket but nobody gets pinged. Treat the SLA as a visual reminder, not an alarm. Check the Overdue filter in the ticket list every morning — that’s your real alerting until you pay.

Step 5: Write 10 canned responses, not 100

Canned responses live under Admin > Productivity > Canned Responses. Create folder Common, then add replies for: order status, refund policy, how-to-login, feature request acknowledgement, and closing a ticket cleanly.

Use placeholders like {{ticket.requester.name}} so they don’t read like form letters. Ten solid replies covers roughly 60% of a typical small-team queue; the other 40% is where you want a human typing anyway.

Step 6: Add the web widget and a help article or two

The support widget is under Admin > Channels > Widgets. Paste the snippet just before the closing body tag on your site. Set position bottom-right, hide it on the checkout page if you have one.

Then write three knowledge base articles answering your three most common questions. It’s the cheapest deflection you’ll ever get: every read is a ticket you didn’t answer.

Freshdesk free vs paid: when to switch

Move to paid when a third person needs a login, or when you’re manually reassigning more than a few tickets a day. Before then, the free plan is genuinely enough.

Is Freshdesk free plan really free forever?

Yes. It’s not a 14-day trial and there’s no time limit or credit card requirement. Freshdesk only bills when you add a third agent or upgrade the plan. If you sign up for a trial of Growth and let it lapse, the account drops back to the free tier rather than locking you out.

Quick Summary

• Freshdesk free = 2 agents, unlimited email tickets, no time limit, no card.
• Setup order that works: forward existing mailbox → ticket fields → SLA → canned replies → widget.
• The free plan has zero automation rules, so no auto-assignment and no escalation emails.
• Paid plans start near $15 per agent per month for automations and custom reports.
• Add a third teammate and you’re forced to upgrade; plan the budget for it.