Skip to main content
Submitted

Rename default statuses for Agents

Related products:Freshservice
  • Nov 17, 2026 5:45 PM UTC
  • 2 replies
  • 8 views

Medic1334
Top Contributor ⭐
Forum|alt.badge.img+10

In working on a tenant that I was brought in to stand up, there’s a request to change the status of “Pending” to “Pending user” for agents. This is prohibited from being changed (although you can change what appears to requesters) currently. Similar restrictions apply to Open (and I believe resolved/closed). Many agents are having problems learning/understanding that Pending isnt to be used for “Pending further action” or whatever similar (we have automatic closure set to happen after 50 business hours in pending to avoid nonresponse on tickets).

On the backend, these statuses are correlated to a digit. Why we cannot change the string value that is presented is beyond me. Changing the string value to “Pending response” would help reduce training time on our side (and make transitions from other ITSM tools into FS simpler as the experience will be more familiar)

2 replies

Trevor Cooper
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • Nov 18, 2026 9:54 AM UTC

Upvoting, as I agree that people should be able to use whatever wording their company desires.

 

As a workaround, could you use a global business rule to hide “Pending” and then create a new status option?  This doesn’t help for resolved/closed though as the built in filters for “All Unresolved” are hard coded to exclude those two status options.


Medic1334
Top Contributor ⭐
Forum|alt.badge.img+10
  • Author
  • Top Contributor ⭐
  • Nov 18, 2026 12:08 PM UTC

Exactly.

And of course during the build out all automations and such were setup to use that status so converting means going through every workflow and swapping it out then doing a bulk update on hundreds of open tickets.  Of course some of this is “training” but when migrating tenants, less is definitely more from a user experience standpoint.