HaloITSM Guides
Documentation to assist with the setup and configuration of the HaloITSM platform
Agent Forwarding and Email Updates
Within Halo there are options to forward end-user emails sent directly to your ticket queues from your agents' personal emails. There are also settings to customise their behaviour once forwarded in.
By default agent forwarding is enabled, so any communication through personal email can be copied into Halo.
Ensuring Agents can Interact with Tickets Outside of Halo
- Go to the configuration and head to email.
- Ensure the option is enabled to 'Treat forwarded Emails from Agents as End-User emails'This setting is on by default it means, when checked, emails forwarded from agent addresses to your mailbox(s) will ignore the forwarded email details & only consider the details of the original email, as if it was sent directly. So if an agent forwards an email from the end-user to the assigned agent, the update going to the ticket will only include the details the end-user added, not the forwarded message
- Forward incoming updates to all recipients: When checked, this will send an Email containing any ticket updates to those currently in the Email Recipients list for that ticket. This can be viewed by hovering the three dots at the top right of a ticket view, and clicking "Edit Email Recipients". For more settings descriptions for emails, checkout the admin guide on emails.
- Scrolling down to outgoing email you find the following option 'Forward Agent updates Via Email to End-Users'
- This option will enable your agents to update end-users/tickets from their personal email. Choose whether to enable this.
- Combine this with a notification to update agents when their tickets are updated to enable your agents to work on tickets when accessing Halo is not possible.
The tickets that are now updated in this way will contain a record of all email interaction between any agents and the end-user.
Setting found in Configuration > Email - "Emails from Co-managed Agents are treated as Users":
When this setting is enabled if the agent has the "Co-Managed IT" setting enabled (found within Configuration > Teams & Agents > Agents > *Click into the Client Restrictions Tab*) and they aren't in the team that the ticket is assigned to then the system will treat the email as an end-user's. If this "Co-Managed IT" agent has forwarded on an email from another end-user, it will log the ticket as the other end-user. The benefit of this is that the Co-Managed IT agent can email in to update the ticket as an end-user update if needed.
Popular Guides
- Asset Import - CSV/XLS/Spreadsheet Method
- Call Management in Halo
- Creating a New Application for API Connections
- Creating Agents and Editing Agent Details
- Departments and Teams
- Halo Integrator
- Importing Data
- Multiple New Portals with different branding for one customer [Hosted]
- NHServer Deprecation User Guide
- Organisation Basics
- Organising Teams of Agents
- Step-by-Step Configuration Walk Through
- Suppliers