Freshservice 3.0 is not a reskin. The information architecture, form rendering engine, and admin panel layout all changed. Rolling it out without a plan triggers a wave of “where did X go” tickets from your own agents.
Week 1: Sandbox and gap analysis
Clone production into a sandbox tenant. Run your top 10 most-used workflows and document where each clicked element moved. Pay attention to:
- Ticket properties panel collapsed by default
- Custom object fields rendered via the new Crayons form engine
- Approvals merged into a unified inbox
Week 2: Workflow regression
Workflow Automator rules that depend on field IDs will keep working, but rules that scrape the DOM via custom Marketplace apps will not. Audit installed apps for any using the legacy client.interface.trigger patterns.
// Old (3.0 may render but deprecate)
client.interface.trigger("showModal", { title: "Approve" });
// Preferred in 3.0
client.instance.modal({ title: "Approve", template: "modal.html" });Week 3: Agent enablement
Agents resist redesigns when surprised. Send a 90-second Loom showing five things that moved, host one office hour, and pin a “What changed” article in the agent help widget.
Week 4: Phased cutover
Use the Freshservice early access toggle per agent group. Roll out to internal IT first, then a friendly business unit, then everyone. Monitor the agent satisfaction pulse for two weeks post-cutover.
Don’t skip these
- Re-test SSO redirect URLs (the post-login deeplink format changed)
- Verify mobile app version compatibility (3.0 needs v9.4+)
- Re-export any saved analytics dashboards; layout serialization changed
What to do this week
Spin up a sandbox, run your top-10 workflows in 3.0, list the moved UI elements, and book the early-access toggle calendar with your agent team leads.
