Every agent in your helpdesk can configure their own signature under the profile settings page.
Alternatively, we would also be able to set up a common signature for all the agents which appear when they reply to the ticket by navigating to Admin-->Email Notifications-->Agent Reply Template.
The common signature would be placed on top of the individual signature.
If you navigate to Admin-->Support Channels-->Email, you would see the option to toggle on the option of “Use Agent Names for Personalised Email replies”. Toggle this On if you need the replies to be triggered with Agent name rather than the Helpdesk name.
The error message occurs when the email address has already been associated with another user who can either be an agent/requester. In order to proceed further on this, please ensure the following checks are done:
Try searching the email address on the global search bar.
If the search does not yield results, the email address is probably associated with a deleted requester. To find this, please navigate to Admin-->Requesters-->Deleted and check if the email address has been associated as a primary or secondary email to the requester profile.
If it exists, please restore the user and convert the requester to an agent.
Privileges to an agent account is provided based on the role that has been assigned to the agent profile. To change the privilege an agent has, please try editing the agent and provide a role that is needed.
When a new agent profile is created, an activation email would be sent to the agent email address which can be used to set up a password. Should the agent wish to reset the password anytime in the future, the ‘Forgot my password’ button on the login page can be used to trigger a password reset email.
Please check to see if the password reset email is in the spam/trash folder of your mailbox, if the email is still not available in the spam/trash folder you can reach out to us at email@example.com for further assistance.
The activation email can’t be turned off and we would advise agents to set a password for their accounts individually.
Freshservice has agent email notifications that can be used to notify the agent. To notify the agent regarding new ticket assignments and ticket updates, you can enable the ‘Ticket assigned to agent’ and ‘Requester replies to ticket’ notification which can be found under Admin-->Email Notifications
Since you are an Occasional agent, your account would use day passes to login to the system, you would not be able to login if there are no day passes left. You can reach out to our support team at firstname.lastname@example.org for purchasing additional day passes.
Occasional agents would have to login to the instance before accessing the API. If the user tries to access the system without logging in it would throw a message asking them to login to the system.
You can check the day passes consumed by an Occasional agent by navigating to Admin-->Agents-->Occasional Agents. Here you would be able to see the number of day passes consumed by each agent next to their profile.
We would not be able to delete an agent from freshservice. If you need to remove the agent from your agent list, you can choose to ‘Deactivate Agent’ profile. In order to deactivate an agent profile, please navigate to Admin > Agents and click on the Agent profile. Now on the far right click on the ellipsis (three dots) and choose ‘Deactivate Agent’.
In order to deactivate an agent profile, please navigate to Admin-->Agents and click on the Agent profile. Now on the far right click on the three dots and choose "Deactivate Agent".
For more information on deactivating agents, please refer to the solution article here.
This would move the agent to the list of deactivated agents.
The agent will not be able to log in to freshservice. In case of activation, the admin can navigate to Admin > Agents > Agent Name > Activate.
You will not be able to assign entities (such as tickets, problems, assets and projects) to them.
All tickets assigned to the agent with Open, In Progress or Pending statuses will automatically become unassigned.
All tickets assigned to the agent with Resolved and Closed statuses will remain as it is.
The agent will automatically be removed from all account level configurations except workflow automator, in which users will have to manually remove the agent from the associated workflow.
If the agent is deleted in AD, the agent will be automatically deactivated in freshservice.
If you click on forget user,
All incidents and notes (Public and Private) created by this Agent will be deleted
All Service Requests which were requested for this user will also be deleted
The “Forgot Agent” action will be recorded under the Activities tab
The previous actions performed by the forgotten agent (including name) will be listed under Audit Logs
When we delete an agent from the system they would be converted to a requester and all the tickets that were assigned to the particular agent would go unassigned.
If you delete an agent account, all the tickets assigned to the agent will be moved to "unassigned." To avoid this, edit the agent account and provide a dummy email address to the profile and save the profile. Now, convert the agent from Full Time to Occasional agent. By doing this, you won't be charged for that account, the agent won't be able to login to your system and you'll also continue to have all the data relevant to that agent.
This happens when the agent whom you are trying to assign the ticket is not part of the group in which the ticket is assigned to. Try changing the group for the ticket and you should be able to find the agent under the right group.
You would be able to associate one of your helpdesk support emails to an agent group. To do so, navigate to admin -> support channels -> email, click on the edit icon next to the helpdesk email and here you would be able to choose the group association for the email address.
When we delete an agent group from the system, any tickets that were assigned to the group would be having the group field as unassigned.
It is not possible to display certain fields based on the group in which the ticket is assigned to. However, please reach out to our support team at email@example.com if you need further information regarding portal customization for the same.
Yes, you would be able to configure agents in multiple groups.
The agents would have access to tickets assigned to all the groups that they are a member of.
The status is default across all tickets in your helpdesk and we would not be able to setup statuses based on specific groups.
Agent groups can’t be merged into a single group, it would be added as a single group in the system. We don’t have the option of creating Sub Groups etc in the system.
If the assigned agent’s role provides the user the privilege to edit ticket properties, then the agent would be able to reassign the ticket to another agent. We would be able to provide an agent restricted roles for editing ticket properties which would make sure that they’re not able to edit any ticket property.
Also, we can set up workflow automation within Freshservice to send emails to Supervisors when an agent reassigns the ticket. Please reach out to firstname.lastname@example.org for further information on this.
You can enable/disable email notifications from Admin-->Email Notifications, however the notifications which are marked as System notifications we wouldn’t be able to disable them.
Please navigate to Admin-->Email Notifications and enable the “New Ticket Created” notification for Agents. Once you enable the notification, please add the agents who have to receive notifications into the “Notify Agents” list.
Please add the Agents to the “Notify Agents” list in Admin-->Email notification-->New Ticket created notification for Agents. Once we add the agent to the list, we would be able to trigger notification for the agent once the ticket is created.
Under Admin-->Email Notifications we have a User Activation email available for requesters which would be triggered to the requester when they sign up for an account from the portal. You can disable this if you don’t want this to be triggered when they sign up for an account.
Automated emails that are sent from Freshservice can be edited from Admin-->Email Notifications.
We have two notifications available under Email notifications in Admin and you can enable them as per your requirement.
For ticket Resolution - ‘Agent Solves the ticket’
For ticket Closure - ‘Agent Closes the ticket’
When we close a ticket, if you try closing the ticket by using the Keyboard shortcut (Alt+~) or you can press Shift and click on the close button on the ticket to skip Closure email notifications.
You can set up the notification for first response and resolution SLAs under Admin-->Email Notifications. The notifications that you have to edit are “First Response SLA Notification” and “Resolution time SLA Notification”. However, these notifications would be triggered only if the SLA policies have been configured, you can check this from Admin-->SLA Policies.
We have an email notification available under Admin-->Email notifications called ‘Agent adds comment to Ticket’, please enable the same for notifying the requester when there is a public note added by the agent to the ticket.