Freshdesk Product Expert for Admins study materials
Freshdesk Product Expert for Admins study resources

Freshdesk Product Expert for Admins study plan

Freshdesk Product Expert for Admins · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Ticket Lifecycle, Workflows and Automation (Dispatch'r, Observer, Supervisor)

  • Map the full ticket lifecycle states and transitions, and configure at least three statuses in a trial account.

  • Create two Dispatch'r rules that route tickets by priority and requester domain, and verify them with test tickets.

  • Build an Observer rule that notifies a supervisor when a ticket remains unresolved beyond a set threshold.

  • Configure one Supervisor rule that escalates based on a time condition, and document the trigger logic.

  • Compare Dispatch'r, Observer, and Supervisor execution order and list three scenarios where each is the correct tool.

Your checkpoint

A one-page workflow map showing ticket statuses, rule types, and the exact conditions used in your test rules, with screenshots of triggered outcomes.

Week 2

Ticket Lifecycle, Workflows and Automation (Dispatch'r, Observer, Supervisor) & SLA Policies, Escalations and Time-Based Rules

  • Design a multi-stage automation chain that combines Dispatch'r assignment with an Observer notification and a Supervisor escalation.

  • Create an SLA policy with at least two targets (first response and resolution) tied to priority levels.

  • Configure an escalation rule that fires when an SLA target is breached, and test it with a backdated ticket.

  • Audit automation conflicts by listing rules that could fire on the same ticket event and resolving overlaps.

  • Document the difference between time-based Supervisor rules and SLA escalation rules with concrete examples.

Your checkpoint

A tested automation and SLA design document containing rule definitions, SLA targets, escalation thresholds, and evidence of each rule firing in a trial account.

Week 3

Admin Account Setup, Agent Roles and Permissions & Groups, Skills, Business Hours and Assignment Logic

  • Create three agent roles with distinct permission scopes (full admin, team lead, restricted agent) and assign them to test users.

  • Configure two groups with different business hours and verify how business hours affect assignment and SLA timers.

  • Define a skill set, attach it to agents, and build an assignment rule that routes by skill.

  • Test round-robin and load-balanced assignment modes and record the observed distribution across agents.

  • Document the interaction between group membership, skills, and business hours in the assignment decision.

Your checkpoint

A role and assignment matrix listing each role, group, skill, and business-hours profile, plus a test log showing how five sample tickets were assigned.

Week 4

Email, Portal and Multi-Channel Inbox Configuration & Canned Responses, Solution Articles and Self-Service Content

  • Configure two support email addresses with distinct routing and verify inbound ticket creation for each.

  • Set up portal branding, a custom support portal URL, and at least two portal languages.

  • Create a canned response folder structure with five responses using placeholders, and share them with a group.

  • Publish three solution articles in a category and link them from a canned response.

  • Test the self-service flow by submitting a ticket through the portal and confirming article suggestions appear.

Your checkpoint

A channel configuration checklist with screenshots of both email inboxes, the branded portal, canned response folders, and published solution articles, plus a test transcript of the self-service flow.

Week 5

Custom Fields, Forms, Ticket Templates and Data Hygiene & Reports, Analytics and Admin Dashboards

  • Create five custom fields across ticket and contact forms, including a dependent dropdown, and validate them in the portal.

  • Build a ticket template that pre-fills custom fields and canned responses for a common request type.

  • Design a data hygiene rule set to identify stale custom field values and document a cleanup procedure.

  • Create three reports: ticket volume by group, first response time by priority, and SLA compliance by agent.

  • Build an admin dashboard combining the three reports and schedule a weekly export.

Your checkpoint

A custom field and form specification document plus a dashboard export showing the three reports with at least one week of test data.

Week 6

Integrations, Apps, API Keys and Webhooks & Security, Audit Logs, Sandbox and Data Governance

  • Generate an API key with least-privilege scope and perform a read-only ticket query using the API.

  • Configure a webhook that posts ticket creation events to a test endpoint and verify the payload.

  • Install and configure two marketplace apps relevant to your workflow, and document their permission requirements.

  • Review audit logs for the past week and identify three configuration changes with their actors and timestamps.

  • Document a sandbox promotion procedure covering configuration export, validation, and rollback.

Your checkpoint

An integration and governance runbook containing API key handling rules, webhook payload examples, app inventory, an audit log excerpt, and a sandbox promotion checklist.

Week 7

Admin Account Setup, Agent Roles and Permissions & Email, Portal and Multi-Channel Inbox Configuration & Integrations, Apps, API Keys and Webhooks

  • Reconfigure agent roles to enforce least privilege across all test users and verify access boundaries.

  • Audit email and portal settings for security gaps such as open tracking or unverified domains.

  • Rotate the API key, update the webhook secret, and confirm integrations still function.

  • Run a mock security review using the audit log to trace a simulated unauthorized change.

  • Document a data retention and export policy covering tickets, contacts, and attachments.

Your checkpoint

A security hardening report listing every change made, before-and-after settings, and a completed mock audit trace.

Week 8

Ticket Lifecycle, Workflows and Automation (Dispatch'r, Observer, Supervisor) & Groups, Skills, Business Hours and Assignment Logic & SLA Policies, Escalations and Time-Based Rules & Custom Fields, Forms, Ticket Templates and Data Hygiene & Reports, Analytics and Admin Dashboards

  • Complete a timed 60-question practice set weighted by domain percentage and score each domain separately.

  • Rebuild the two weakest domain configurations from memory in a fresh trial account.

  • Explain aloud the decision tree for choosing Dispatch'r versus Observer versus Supervisor in five scenarios.

  • Review all deliverables and consolidate them into a single reference binder with an index.

  • Write a personal list of ten facts you missed during practice and schedule two spaced reviews.

Your checkpoint

A scored practice exam report with per-domain results, a rebuilt configuration for the two weakest domains, and an indexed reference binder.

Milestones

Week 2: You can build a Dispatch'r rule, an Observer rule, a Supervisor rule, and an SLA escalation from scratch without notes, and explain when each fires.

Week 4: A test requester can email support, receive a canned response, and find a relevant solution article through the portal without agent intervention.

Week 6: You can authenticate to the API, trigger a webhook, and locate a specific configuration change in the audit log within ten minutes.

Week 8: You score at least 80 percent overall on the weighted practice set with no domain below 70 percent.