Freshdesk Product Expert for Admins key terms

A named set of permissions assigned to agents that controls what they can view and act on across tickets, contacts, and admin areas. Roles are scoped further by group and scope settings.

A role setting that determines whether an agent sees all tickets in the helpdesk or only tickets belonging to groups they are a member of. Scope is evaluated together with role permissions.

A container of agents used to route and restrict tickets, often aligned to a team or product line. Groups drive assignment, visibility, and business-hour rules for tickets.

A labeled capability or attribute such as a language or product expertise that can be attached to agents and required by tickets. Skills enable routing to the best-qualified available agent.

Assignment logic that matches incoming tickets to agents who hold the skills the ticket requires, usually combined with availability and load checks. It is configured through automation rules.

An automatic distribution method that rotates new tickets among eligible agents in a group so workload is shared evenly. Eligibility can be filtered by skill, availability, or ticket load.

An assignment option that gives a new ticket to the eligible agent currently handling the fewest open tickets. It prevents one agent from being overloaded while others sit idle.

A named calendar of working days and hours, including holidays, used to calculate SLA targets and to decide when time-based rules and escalations should run.

The sequence of statuses a ticket passes through from creation to closure, such as Open, Pending, Resolved, and Closed. Transitions can trigger automations, SLA pauses, and surveys.

A field describing where a ticket stands in its lifecycle. Default statuses include Open, Pending, Resolved, and Closed, and admins can add custom statuses mapped to these categories.

The act of returning a Resolved or Closed ticket to an active state, typically when a requester replies. Reopen behavior and time windows are controlled by admin settings.

The automation engine that runs rules on ticket creation to set properties such as group, agent, priority, and status before an agent first touches the ticket. Rules run in a defined order.

The automation engine that runs rules when a ticket is updated, such as on status change or agent reply, to modify fields or trigger notifications. It complements creation-time rules.

The time-based automation engine that runs rules on a schedule, for example to escalate tickets that have been Pending too long or to remind agents about stale tickets.

The sequence in which automation rules are evaluated, where the first matching rule can stop or pass execution to later rules. Order determines the final value of a field.

A rule set that defines response and resolution time targets for tickets matching certain conditions, measured against a business-hours calendar. Breaches can trigger escalation and reporting.

An automated action that raises attention when a ticket approaches or breaches an SLA target, such as reassigning it, raising priority, or notifying a manager. Escalations are time-based rules.

A reusable reply template with placeholders that agents insert into ticket replies to answer common questions quickly and consistently. Canned responses can be shared or restricted by folder.

A knowledge base document published in the self-service portal to help customers resolve issues without contacting support. Articles can be organized in categories and folders and made visible per audience.

The customer-facing web area where users browse solution articles, submit tickets, and track their requests. Portal branding, languages, and access settings are managed by admins.

The consolidated agent workspace where tickets from email, portal, chat, phone, and social channels arrive and are handled. Channel-specific settings determine how each source becomes a ticket.

The configuration that turns messages sent to a support address into tickets, including forwarding rules, sender authentication, and reply threading. Misconfiguration causes loops or rejected mail.

Email authentication records that prove a sending domain is authorized and messages are unaltered. Correct records improve deliverability of notifications and prevent spoofed support mail.

An admin-defined field added to tickets, contacts, or companies to capture data specific to the business. Field type, visibility, and mandatory status affect forms and reporting.

A configurable layout of fields that requesters or agents see when creating or editing a ticket. Multiple forms can target different ticket types or customer segments.

A rule that shows, hides, or makes a form field mandatory based on the value of another field. Dependencies keep forms relevant and reduce invalid submissions.

A predefined set of ticket field values applied when creating a ticket, used to standardize common request types. Templates reduce manual entry and enforce data hygiene.

A dynamic token inserted into templates, notifications, or automations that is replaced with actual ticket or contact data at send time. Wrong placeholders produce blank or misleading messages.

A chronological record of administrative and agent actions such as settings changes, deletions, and permission edits. Audit logs support troubleshooting, compliance reviews, and accountability.

A credential that authenticates programmatic requests to the helpdesk API, carrying the permissions of the user it belongs to. Keys should be scoped, rotated, and never shared.

An outbound HTTP callback that notifies an external system when a specified event occurs, such as ticket creation. Payloads and target URLs are configured and must be secured.

A packaged connector installed from the marketplace or built as a custom app to link the helpdesk with external tools. Apps use API credentials and can add UI or automation behavior.

An isolated copy of the helpdesk environment used to test configuration changes, automations, and integrations before applying them to production. It protects live data from untested changes.

The policies and controls that determine how customer data is stored, accessed, retained, and deleted, including consent, retention periods, and export rules. It underpins privacy compliance.

A configurable view of reports and metrics such as ticket volume, first response time, and SLA compliance, used by admins and managers to monitor support performance.

The elapsed time between ticket creation and the first agent reply, measured against business hours for SLA purposes. It is a core metric in support performance reporting.