How to Create an SOP in Freshdesk
Support quality depends on every agent handling the same ticket the same way. Merging duplicates, escalating to tier two and setting the right status are where new agents slip. An SOP recorded in your helpdesk keeps them consistent.
- 14-day free trial
- No credit card
- Viewers never pay
- Works on any web app
What does “Create an SOP in Freshdesk” mean?
An SOP for Freshdesk is a written procedure for one repeatable support task in your helpdesk, such as merging duplicate tickets. It names where to start, which ticket becomes the primary, which fields, groups and statuses to set, what note to leave and what the customer sees afterwards.
Why this matters
Helpdesks drift. Groups, statuses, custom fields and automations change, and new agents copy whoever sits next to them.
Where it goes wrong today
Training by shadowing
New agents learn from whoever is free, including their shortcuts and mistakes.
Knowledge base is for customers
Your public help articles do not cover internal agent procedure.
Docs fall behind automations
An automation or field is added and the agent guide is not updated.
The fix
How Michii handles it
Record the procedure once
Michii captures each click in Freshdesk with a screenshot.
Agents follow it live
The guide plays inside the agent view and rings the next button.
Shortcuts for common tasks
Name guides /merge or /escalate so agents start them in a second.
How to create an SOP in Freshdesk
Create two test tickets from a test contact before you record, so you can merge without touching real customers.
Pick one task
For example: merge a duplicate ticket into the original.
Decide the rules
Which ticket is primary, what private note to add, whether the requester is notified.
Open the ticket in the agent view
Start where an agent would start.
Click Record and merge the tickets
Michii captures each step, including the search and confirmation.
Add the reasoning
Explain how to choose the primary ticket and what the note should say.
Blur customer details
Requester names and emails come off the screenshots.
Share with the team
Add the link to your agent onboarding and give it a shortcut.
By hand vs. with Michii
| Doing it by hand | With Michii | |
|---|---|---|
| How agents learn it | Shadowing a colleague | Following the guide in the agent view |
| Consistency | Depends on who trained them | Same steps every time |
| After a helpdesk change | Update a doc nobody reads | Re-record the changed steps |
| Customer data | Visible in pasted screenshots | Blurred automatically |
What teams use this for
Checklist
- Use test tickets from a test contact
- Name the group and status rules
- State who gets notified
- Blur requester names and emails
- Describe the finished ticket state
Frequently asked questions
Do agents need a paid Michii plan?
No. Only people who create guides need a plan after the trial. Agents who only play guides never pay.
Can guides open from inside Freshdesk?
Agents start a guide from the Michii panel by typing its shortcut, such as /merge, on any page.
What if our Freshdesk layout changes?
Michii matches steps by label, role and position, so small changes usually do not break a guide. If one does, point at the new element once.
Give your agents one way to do it
Record the workflow once. Michii writes the steps, captures the screenshots, and gives you one link to share. 14 days free, no card.
Create an SOP in other tools
Related