Before you open Freshdesk to customers
Start by confirming which product you have. Freshworks describes Freshdesk as email-first and Freshdesk Omni as the multichannel option for email, chat, social and more. This guide follows the Freshdesk product and its public pricing table, not an assumed Omni configuration. Read the official getting-started guide, checked October 29, 2026, if your account uses Omni or includes additional channels.
Write down the support address, ticket categories, ownership rules, response targets, customer data fields and escalation contacts. Decide which requests should become tickets and which should be handled elsewhere. A small, clear first workflow is easier to validate than a large automation setup.
1. Connect and verify the support email
- Sign in with an administrator account.
- Open Admin, then Channels and Email. Add the support address your customers will use.
- Follow the product's instructions to configure forwarding from the mailbox to Freshdesk and complete any verification step.
- Send a test message from an external address and confirm it creates one ticket with the correct sender and subject.
- Reply from Freshdesk and confirm the customer receives the response from the expected address.
Menu labels can vary by product version and account permissions, so follow the official support-email setup guide, checked October 29, 2026, if a step differs. Do not route the public support address until both incoming and outgoing messages work.
2. Invite agents and define ownership
Invite only the people who need access at launch. Create groups that reflect real work, such as billing, account access or technical support, rather than mirroring every department name. Decide who can reassign tickets, edit rules and change account settings. Use roles and permissions to separate administration from daily support work.
Agree on an unassigned-ticket routine. For example, one person can review new tickets at set intervals, while a group owner handles items that need specialist help. The exact process matters more than the group names: every incoming ticket needs a clear next owner.
3. Set ticket fields and priorities
Define the minimum fields required to route and resolve a ticket. A practical starting set is issue type, product or service, priority, status and assigned group. Add custom fields only when the value is used in routing, reporting or follow-up; otherwise they increase agent work without improving decisions.
Choose what each priority means in your team. Write down the conditions for urgent work, who can change the priority and how it affects escalation. Test with real examples so that agents do not mark every ticket urgent. Keep the status workflow simple enough that every agent can explain when a ticket is open, waiting, resolved or reopened.
4. Add customer context without over-collecting data
Use customer or organization fields that help an agent resolve a request, such as account type or product plan. Avoid collecting sensitive details unless your policy and legal basis allow them. Limit access to fields that are not needed by every agent and agree on how long support data should be retained.
For recurring questions, create a short internal note or approved reply with the steps and escalation condition. Keep internal comments separate from messages customers can see. Review templates whenever a product flow or policy changes.
5. Build the customer portal and knowledge base
Freshdesk's public pricing table lists a customer portal and knowledge base on Growth, Pro and Enterprise. Start with the questions that generate repeated tickets. Give each article a specific task, such as resetting access or checking an order status. Use numbered steps, name the menu labels, show what success looks like and explain when to contact support.
Before publishing, test the article as a customer without agent permissions. Check whether the search result is clear, the links work and the answer still applies to the current product version. Link relevant knowledge content from approved replies so agents do not have to paste different instructions into every ticket.
6. Add one low-risk automation at a time
Start with a rule that is easy to verify, such as assigning a ticket to the billing group when the customer selects a billing category. Submit a sample that should match and another that should not match. Check assignment, priority, notifications and any customer-facing reply. Then check the rule against a ticket that already has an owner to avoid accidental reassignment.
Keep an exception path for incomplete or ambiguous requests. Do not create several overlapping rules before you know which one fired. Record each rule's purpose and owner, and review the list after the first week. Freshdesk's exact automation controls depend on product and plan; use the official setup documentation as the source of truth.
7. Check service targets and reporting
Review incoming volume, unassigned tickets, backlog age, first response and resolution patterns. A fast first response does not prove a ticket was solved, so compare several metrics. Look for repeated categories that could use a knowledge article or a better form field.
Freshdesk lists standard analytics and reporting on Growth, while custom dashboards and multiple SLA policies are listed on Pro. Confirm that the plan supports the reports and service targets you intend to use. Do not create a target that agents cannot realistically meet with the current staffing level.
8. Understand AI usage before enabling it widely
Freshworks' official AI add-on guide says new customers on Growth, Pro or Enterprise receive a one-time complimentary 500-session allowance. Additional packs cost US$49 per 100 and are valid for the current billing cycle. Email AI Agent sessions span 72 hours from the first customer email; Chat AI Agent sessions in Freshdesk Omni span 24 hours. Pro and Enterprise list Freddy AI Copilot at US$29 per agent/month as an add-on. These details were checked October 29, 2026 on the official AI add-on guide and official pricing page.
Test AI with a small set of known questions and review the answers for accuracy, privacy and escalation. Keep a human review path for account changes, billing issues or requests where a wrong answer would create a real cost. Measure both usage and the number of cases that still require an agent.
9. Test the full ticket path before launch
- Send an email from a new customer and confirm the ticket record.
- Check that the intended group and priority are assigned.
- Add an internal note and verify that it is not sent to the customer.
- Reply to the customer and confirm the sender address and thread history.
- Resolve the ticket, then reopen a test case and confirm the process.
- Search the knowledge base as a customer and open the most common help article.
- Review the report that shows the test tickets and remove or label test data according to your policy.
Use at least one test case for a missing field, a wrong category and an urgent escalation. This catches routing errors before real customers depend on the setup.
10. Export and migration checks
Freshdesk's official ticket export guide, checked October 29, 2026, describes filtered ticket exports and limits. Do not assume a CSV of a ticket list contains the full conversation history, archived tickets, every attachment or the configuration of automations. If you may leave Freshdesk later, test the account-level export path now and document what it includes.
Keep an inventory of ticket fields, groups, macros, rules, knowledge articles, users and reports. Export a sample, compare record counts and inspect attachments before treating the migration as complete. The Freshdesk alternatives guide includes a migration checklist, and Freshdesk vs Help Scout covers one supported import path.
Troubleshooting before launch
If a support email does not create a ticket, confirm that the address is configured and verified, the forwarding rule points to Freshdesk, and mailbox forwarding is active. Send a test from a different address because Freshdesk may reject messages where the sender and recipient are the same. If an automation fails, test one ticket that should match and one that should not, then review the rule conditions and order. If an export looks incomplete, check the official ticket export guide and test the account-level export path instead of assuming a ticket-list export is a full archive. The email setup and export guides were checked October 29, 2026.
Common setup mistakes
- Forwarding email before verifying both incoming and outgoing messages.
- Creating too many groups and custom fields before ticket ownership is clear.
- Building overlapping automation rules without a negative test case.
- Assuming a ticket-list export is a complete account archive.
- Treating the first 500 AI Agent sessions as a monthly allowance instead of a one-time grant, or ignoring add-on charges.
- Choosing Freshdesk when the team actually needs Freshdesk Omni's channel set.
Freshdesk setup FAQ
How do I connect email?
Open Admin, go to Channels and Email, add the support address, configure forwarding and complete the verification steps in the official setup guide.
Can I export every ticket conversation?
Do not assume so. The ticket-list export guide describes filtered exports and limitations; check the account-level export path if you need a complete history.
How should I test automations?
Start with one low-risk rule, submit sample tickets that match and do not match it, and verify assignment, customer replies and escalation before applying it to all incoming tickets.
How many AI sessions are included?
Freshworks says the first 500 Freddy AI Agent sessions are a one-time complimentary allowance for new customers on Growth, Pro or Enterprise. Extra packs cost US$49 per 100 and are valid for the current billing cycle.
Related Freshdesk pages
Use the Freshdesk hub for the product overview, pricing guide for plan and add-on costs, review for strengths and limits, and alternatives guide if the workflow is not a match. For more software discovery, visit Browse Tools by Niche.