Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
On the right hand side of the home page is the Team Bar.
If you are a Team Member, the Team Bar shows you your team and your unassigned work.
At the top of the Team Bar you can see the people in your team and, for each of them:
The amount of work they have outstanding (number in centre of pie-chart)
The due status of that work (i.e. Red/Amber/Green)
Their current availability status (available or offline)
You can see the availability status of your Team Members - so if they are online or offline.
The system tracks your active Enate browser session, and so is able to check if they are still logged into Enate.
Note: if you do not log out properly, i.e. shut down the browser or machine directly without logging out of Enate, the system will display you as still online for the duration of the standard system timeout (usually 30 minutes).
An important point is that this available / offline status is for informational purposes only – it is not taken into account as part of any allocation rules - i.e. the ‘Who does it go to?’ settings.
You can filter the display of your team to show available / offline / all users.
You can sort your team members by work item status criteria including:
Least / Most Work (Total)
Least / Most Overdue (Amber)
Least / Most Overdue (Red)
Least / Most On Target (Green)
You can use this to help identify resources which are stretched and other team member who you may be able to share work out among to help balance workloads.
Free text search also allows for you to search for individual users from the list.
Clicking on a team member from the Team Bar, will bring up their user profile. The grid filters down to show only work items currently assigned to that user.
The homepage bar chart will be replaced to show the amount of work that is assigned to the user (the number in centre of pie-chart), as well as the due status of that work (i.e. Red/Amber/Green), You will also see the user's profile picture, their role title, its description (if one has been added), and if you click on the 'More about this role' link, you'll see a list showing which features that the user has access to.
You can close the view and return to the standard bar chart view of all work items by clicking the 'X' icon.
At the foot of the Team Bar you can see the amount of work which is sitting unassigned in the Queues you manage, grouped by Queue. This includes information about the amount of work in each Queue that is unassigned (the number in centre of pie-chart), as well as the due status of that work (i.e. Red/Amber/Green).
If you have unassigned work which is overdue – i.e. any red items in this section – you should be looking to deal with that situation.
As a Team Leader (someone who has people reporting to them in Enate), the Home page needs to know who reports to you and what Queues you are in charge of. These settings can be adjusted in the Queues page, which you can open from the navigation section.
If you have no data set up yet, the page will open in Edit mode by default. Otherwise, it will show the Queues that you manage (along with the people who are working out of that Queue), and the list of people who report to you, i.e. your Team.
You can Edit these settings as follows:
Add a Queue. You are also able to add yourself as a manager to a Queue. This includes Queues which may already be managed by a different Team Leader (you will now both be managers of this Queue).
Remove a Queue, i.e. unset yourself as the manager of a Queue.
Add / remove Team Members to one or more of your Queues.
Add and remove Robots to your Queues. You can add/remove all the robots (or just those selected) in a farm to a Queue at one time.
Set a mixed resource Queue to ‘Strict mode’ - In Queues where there is a mixture of human and robot resources, switching on 'Strict Mode' sets any human users in the Queue as fall-back resources only, only receiving work from here if its robots are for some reason currently unable to carry out the work in the Queue.
Queues can be set to have more than one manager.
Example: Consider Manager 1 and Manager 2 as two team leads where Manager 1 needs visibility on the Queue of Manager 2. Manager 1 can simply add the Queue of Manager 2 to his Queues page to have the visibility of the same Queue.
Click on the edit option and add the specified Queue where it shows that the Queue is managed by Manager 2. This does not remove managerial responsibility from the current manager.
If a Queue is managed by multiple people then the users that report to you are filtered under 'Managed by me' and the other users who report to the other person are filtered under 'Managed by others'.
You can add and remove Users to 'My Team'. When you are adding users to your team, you do so by building up a list of the users who report to you.
A user can only report to one Team Leader, so when you add a user to a team, you may be resetting who they report to – if they previously reported to a different Team Leader that will now be wiped and reset to you. They will no longer have that user report to them, and will not have visibility of the user (unless they are still in Queues that the Team Leader manages).
You can use Quickfind to search for people, work items, communications and files.
By default, Quickfind will search against all four categories of people, work items, communications and files, but you can focus down to searching just one of these categories by selecting from the left-hand dropdown in the Quickfind header.
You can search for work items (i.e. Tickets. Cases and Actions) by entering key words relating to them into Quickfind.
If you have many results, then you can choose to filter your search down further by choosing to search by Ticket, Case or Action specifically.
Work item search results will display the reference, title, process name, work item status, due date (with Red/Amber/Green colour-coding), plus the name of the person to whom the item is currently assigned.
Additionally, you can filter the search by start date using the slider provided, from Today through to Past Year, plus specific date ranges.
Hovering over a work item row in Quick find will display a ‘Take It’ icon. Instantly assign this work item to yourself by clicking on this icon.
Clicking on the work item will open it in a new tab.
You can search for contacts by searching for first name, last name, company and email address.
Additionally, further people-extended properties can be added to the system and all text/string properties can be searchable within Quickfind. For example, you might have a 3rd party contact with the attributes ‘Country Name’ etc. which will be searchable in the Quickfind.
The criteria which can be searched against, e.g. ‘Employee Number’, are displayed as the records are returned in the Quickfind results, in the line underneath the contact name.
If you have many results, then you could filter it by clicking on ‘Contact’ or ‘Agent’. When you click on contact, the system will only show contacts with search criteria.
Clicking on a person will open the Contact Activity page where you can view current and historic activity - work items related to that person - all their communications, and start new work for them.
Note: You will only be able to see the email addresses and the Contacts belonging to the companies that you have access to. These settings are configured in Builder, click here for more information.
If you are searching for a new contact which does not currently exist in the system, you can create a new contact from Quickfind itself. Navigate to the people search function in Quickfind and click on ‘add a contact’.
When you click on ‘add a contact’, the system will decode and auto-populate the first name, last name and email address. Once you fill in all the information and click on create, you will be taken to the Contact Activity Page of the new contact.
Note: The contact email address must be unique in the system.
You can search communications (i.e. emails, notes and Self Service communications) by entering key words from the email subject, body text or contact details (To, From, Cc, Bc), or key words from the note or Self Service communication you are searching for.
You can choose to filter you results even further by selecting the communication type i.e. incoming email, outgoing email, note, self-service comment by clicking on top icons.
You can also use the slider to filter by received/sent date (from Today through to Past Year, plus specific date ranges).
Search results will be sorted by the date that the email was sent/received, with the most recent at the top.
Email search results will include details such as the To/From address (depending on whether the email was sent or received), an icon to indicate if the email was sent or received (if the email was sent from you or your team the icon will be green and if the email was received by you or a member of your team the icon will be blue), the email subject and the first few lines of the email body, as well as the email sent/received time.
Note search results display the writer of the note, the first few lines of the note and when the note was written.
Clicking on the communication will open the work item which it is linked to in a new tab.
You can use Quickfind to search for individual files or to search for a work item by searching for one of its files. Searching for files in Quickfind will search for both files that are directly linked to the work item AND files that have been attached to communications for the work item.
The search results will be sorted by the date that the file was last updated on or when the email was sent/received if the file is a communication attachment, with the most recent at the top.
Search results will include details such as the type of file (i.e. whether it was attached to the work item or to a communication), when the work item was last updated if the file is attached to a work item or when the email was sent/received if the file is a communication attachment, the reference number and title of the work item(s) the file is attached to and the communication subject if the file is a communication attachment.
Clicking on the file will download a copy of it and clicking on the work item reference will open the work item the file is attached to in a new tab.
Note: You will only be able to see the files and work items that you have access to to based on the permissions you have. These settings are configured in Builder, click here for more information. You will also not be able to search for files or communication attachments that have been deleted.
Additionally, to mitigate performance issues Quickfind will not return search results for:
Communication attachments that start with 'Mime Attachment'
Communication attachments that start with 'MIME-Attachment'
You can still search for the text mime attachment, but the only results will be from work item files. You can still search for 'mim' which may return other results.
Also note that the system uses 'start with' logic for searching for files where it adds a wildcard to the END of search texts. This means that if you are searching for a file called 'Invoice Processing.docx', searches for 'processing' would not find the file, but searches for 'invoice' would.
On the right hand side of the home page is the Team Bar.
If you are a Team Leader, the Team Bar shows you your team, your bots and your unassigned work.
At the top of the Team Bar you can see the people in your team and, for each of them:
The amount of work they have outstanding (number in centre of pie-chart)
The due status of that work (i.e. Red/Amber/Green)
Their current availability status (available or offline)
You can see the availability status of your Team Members - so if they are online or offline.
The system tracks your active Enate browser session, and so is able to check if they are still logged into Enate.
Note: if you do not log out properly, i.e. shut down the browser or machine directly without logging out of Enate, the system will display you as still online for the duration of the standard system timeout (usually 30 minutes).
An important point is that this available / offline status is for informational purposes only – it is not taken into account as part of any allocation rules - i.e. the ‘Who does it go to?’ settings.
You can filter the display of your team to show available / offline / all users.
You can sort your team members by work item status criteria including:
Least / Most Work (Total)
Least / Most Overdue (Amber)
Least / Most Overdue (Red)
Least / Most On Target (Green)
You can use this to help identify resources which are stretched and other team member who you may be able to share work out among to help balance workloads.
Free text search also allows for you to search for individual users from the list.
Clicking on a team member from the Team Bar, will bring up their user profile. The grid filters down to show only work items currently assigned to that user.
The homepage bar chart will be replaced to show the amount of work that is assigned to the user (the number in centre of pie-chart), as well as the due status of that work (i.e. Red/Amber/Green), You will also see the user's profile picture, their role title, its description (if one has been added), and if you click on the 'More about this role' link, you'll see a list showing which features that the user has access to.
You can close the view and return to the standard bar chart view of all work items by clicking the 'X' icon.
If you find yourself needing to change the levels of access for yourself or users in your team, speak to your system admin.
If you are a Team Leader you will also be able to see your bots in the Team Bar. This shows you any Robots which are available to work on items you manage / work with, grouped by Robot farm.
Each row displays a different robot farm, along with their Technology (e.g. UiPath, Automation Anywhere, Blue Prism etc.).
The number of ‘bottable’ work items lined up for the robot farm will be displayed, as well as the estimated amount of work left available for the robot farm in minutes.
If any of the Robots in the farm are offline or unresponsive, a warning icon will be displayed.
Additionally, it's possible that some of the bottable work items for these bots are outside of this user's permissions. If that is the case then a warning 'i' icon and message will be displayed informing the user of this.
Clicking on a Robot farm in the Bots section swaps out the bar chart main display to show that group of robots AND filters down the grid results to show ‘bottable’ work items.
In this view, Team Leaders can:
See the status of individual robots within the robot farm:
Idle - the bot is available for work
Offline - if your bot uses deep integration, such as UiPath orchestration synchronisation, an offline status means that your IT system can't connect with the bot. In this situation you would reassign the bot's work items to other resources. If your bot does not use deep integration, such as Blue Prism, an offline status means that your IT system hasn't connected with the bot for a certain amount of time.
Suspended – the bot’s average work is not within standard deviation, so it has been paused
Busy Integrated – the bot is busy working on a task that is has been assigned to
Busy Independent- the bot is busy working on a task that it has not been assigned to
View the work currently being done by individual robots
Filter down the view to an individual robot
See how much work is remaining for the bots to do (both in volume, e.g. 20 items, and in how many minutes worth of work is remaining, i.e. how long we think it will take to complete all of those 20 items).
The system can make an estimate of the amount of work left in minutes because we have an ‘estimated duration’ value configured in Builder for different Actions. The system simply totals the value of these for the Actions currently available for the robots to do.
The grid will show projected start and end times for each piece of work, colour-coding the projected end date to show it if will breach the due datetime – this helps the Team Leader determine if they need to add further human / robot resources in order to meet SLAs.
The view can be closed to return to the standard bar chart view of all work items.
How does the system determine which work item to give a ROBOT when they send in a “Get more work" request?
The system works by looking at all unassigned Action work items from all of the Queues the robot is linked to and for which the robot's farm is set as the relevant farm in the 'General Settings' configured for that action (the equivalent of Robot permissions), then from this list determines the one due soonest, and assigns the Action to the Robot.
Exception: If a robot is already listed as working on an Action and yet sends in a "Get more work" request to Enate, the system will send back a response to the Robot of that same Action - effectively reiterating that the bot should carry out that Action. The system will do this a total of 3 times if the robot continues to send such requests while still supposedly 'occupied', and on the next such request will take the Action off the robot, mark it to be allocated to a human rather than a robot, and will then proceed with the normal logic of assigning the robot the soonest due Action from the list of ones it can perform.
At the foot of the Team Bar you can see the amount of work which is sitting unassigned in the Queues you manage, grouped by Queue. This includes information about the amount of work in each Queue that is unassigned (the number in centre of pie-chart), as well as the due status of that work (i.e. Red/Amber/Green).
If you have unassigned work which is overdue – i.e. any red items in this section – you should be looking to deal with that situation.
In this section you'll find lots of explainers and videos teaching you how to use Enate's Work Manager software to manage your business processes day-to-day.
Work Manager is a web-based, multi-page application used by members of the service delivery team to interact with Tickets, Cases and Actions running through managed business processes.
Users of Work Manager are service agents, team leaders, operations managers and executives. Work Manager provides a standard set of views for these users to carry out work.
Watch this video for a quick overview of Work Manager:
Work Manager is designed to support the following Browsers:
Latest version of Chrome (at time of release)
Latest version of Firefox (at time of release)
Latest version of the Microsoft Edge, based on Chromium (at time of release).
You can search for work items and their emails using focussed ‘search this value in this field’ on the work item. This is achieved by prepending the search with predefined search code. Before typing anything into Quickfind, the dropdown displays all short codes available in the system, and the field they relate to.
To search against a field, enter the short code and the desired value e.g. hq:Laptop
This will return work item (Ticket/Case/Action) and communication results where this field has this value:
You can put quote marks around your search value to search for an entire phrase as the field value you want to find e.g.: bn:“entire phrase”
You can also use this approach to search for phrases with general free text searching, i.e. even when you are not searching against a custom field with a prepended short code.
The Home page allows Team Leaders and Team Members to view the work for their area of business, i.e. Work Items sitting in their work Queues and with their Team Members (both human and robot).
On your Home page you will see:
Work Items that are assigned to you
Work Items that are assigned to your manager, i.e. the person you report to (if you have one)
Work Items that are assigned to your peers (people managed by the same person as you)
Work Items in a Queue that you are a member of / are a manager of
Additionally, as a Team Leader you will see:
Work Items that are assigned to people you manage (i.e. people who report to you)
Work Items that are assigned to people managed by people you manage (recursively down the hierarchy of manager relationships)
Work Items in a Queue that you manage, even if you are not a member of it
The Contact Activity Page displays the activity details for an individual service recipient.
You can navigate to the Contact Activity page via:
1. Quickfind – clicking on a user in
Once you are on the Contact Activity Page, you can see the contact's details on the right-hand side and update them as needed.
Clicking on the 'Work Items' tab lets you see all work items which relate to the contact. Each work item is shown as a card with data about it like reference, title of work item, due date, assignee, queue, and state. Work Items can be opened for further details by clicking on reference and title. Running items are displayed by default, completed work items can also be displayed.
Clicking on the 'Comms' tab lets you see communications (emails, notes) relating to the user and the work items relating to them. You can search for specific communications here too.
You can also start a new piece of work for the contact from the Contact Activity Page. Starting a new work item from the Contact Activity Page will automatically assign the contact as the Primary Contact, Requester and Subject on the work item, and if they have a Default Tag set, they will be tagged as this as well on the work item. Note that when launching a Ticket, the 'Send Automated Emails' option is automatically set to off.
You are able to copy the user's name by clicking on the copy button on the tab:
There a numerous ways of creating and managing contacts in Enate. Watch this video to find out more:
External contacts can be created in Enate in several ways.
The Enate system can be set to automatically create new external Contact records when incoming emails arrive which contain new email addresses if the .
The system will auto-populate the first name and last name of the contact based on the email display name. More specifics on this:
If there is a space in the email display name, anything before the first space will be used as the contact's first name and anything after the last space will be used as their last name. For example, if the email display name is 'John Smith' then the contact's first name will be auto-filled as 'John' and their last name will be auto-filled as 'Smith'.
If there is a comma in the email display name, anything before the first comma will be used as the contact's last name and anything after the comma but before the space will be used as their first name. For example, if the email display name is 'Smith, John' then the contact's last name will be auto-filled as 'Smith' and their first name will be auto-filled as 'John'.
If the system can't auto-fill the first name and last name with confidence, then the contact will be auto-created without a first and last name and the user will be prompted to fill this themselves when they submit the work item.
Additionally the to an auto-created contact will depend on the . If it's set to 'Global', or 'Global and Local', the auto-created contact will have a Global scope, i.e. not linked to any specific company. If it is set to 'Local', the auto-created contact will be created under the company that the related Work item exists under.
You can add contacts from the by clicking on the Create Contact icon and filling out the details for the contact in the resulting popup.
Note: The contact email address must be unique in the system.
If you have written the email address for the contact, the system will decode and auto-populate the first name and last name of the contact. Once you fill in all the information and click on create contact, the system will redirect you back to the work item.
Please note that if you create a new contact in test mode, that contact will only be available for running test packets in the system.
Please note that once a contact that auto-created has had edits made to it, it will no longer display as an auto-created contact in the 'Auto Created' column of the Contact Management Page.
Depending upon how it has been configured in Builder, you will have various options when assigning a company to an external contact:
All Companies/Global
Setting the company to this means that external contact can create and access work items for all companies.
It also means that work manager users are able to search for other all external contacts on a work item.
A particular company (local)
Setting the contact scope to a particular company means that external contact will only be able to create and access work items for that particular company that the external contact has been associated to.
Users will also only be able to add a Contact to a Packet API if the Contact is in the same Company (or is in an umbrella Company).
Please note:
It is only possible to change the associated company of an external contact from All Companies/Global to a particular company (local) if the external contact is not associated with work items from multiple different companies. You can change this by reassigning the Contact on a work item.
To scope external contacts to Global/All Companies the Company column in Bulk Upload file should be left blank so by default the contacts will be scoped to Global.
The company set to an auto-created contact will depend on the contact scope setting you have set. If it's set to 'Global', or 'Global and Local', the auto-created contact will have a Global scope, i.e. not linked to any specific company. If it is set to 'Local', the auto-created contact will be created under the company that the related Work item exists under.
Please note that if an External Contact is scoped locally (i.e. is linked a specific Company), you cannot add them as a contact for a work item which exists within another company. This is also true for Agent accounts (which must always exist under a specific Company). ONLY Globally scoped External accounts have the flexibility to be linked as contacts to work items in any Customer.
You are also able to bulk edit the company, time zone, office location, preferred language and default tag of your contacts by selecting on the contacts' tick boxes - click on the Edit button which will appear to display the Bulk Edit popup. Set details as desired and hit Confirm to save bulk changes.
It is important to take your user permissions into account when understanding which Contact records you are able to see, depending on the Global / Local scope setting which has been made in Builder:
Please note: - Locally-scoped contacts are visible to you in if you have permissions specificallly on that contact's company, or parent companies. If you don't have such permissions, you will not be able to see the contact record. - Global contacts are visible to all users.
Click to see how to set the users who report to you (i.e. your Team), and Queues which you manage.
2. A Work Item – clicking on a contact in the of a work item
3. The Contact Management Page – clicking on the first name of a contact in the
The work items that you can start from here depends upon if the work items have been , which when it was created in Work Manager, and which as well.
You can import a list of contacts from an Excel spreadsheet in the . A template is provided and the template is supported in all of the languages that Enate offers.
It is mandatory to fill in the email address when importing Contacts from an Excel template. If you don't specify a company, the contact will automatically be set to global. See here for more information about .
If you are searching for a new contact which does not currently exist in the system, you can create a new contact from itself. Navigate to the people search function in Quickfind and click on ‘add a contact’.
When you click on ‘add a contact’, the system will decode and auto-populate the first name, last name and email address. Once you fill in all the information and click on create, you will be taken to the of the new contact.
You can also create a new contact from the a work item. When you search for a user in the contacts card that does not exist in the system, you can create a new contact by clicking on the ‘Create Contact’ option and filling in the contact's details.
You can see if an external contact has been automatically created by the system or manually created by a user by looking at the 'Auto-Created' column in the .
Please note that this setting is only available if the External Contact Scope has been set to 'Global' or 'Global and Local' in Builder. See for more information.
To edit a contact, go to the and double click on the contact to bring up the Edit Contact popup.
To delete a contact, go to the and click on the contact's tick box and the delete button will appear. You are able to delete multiple contacts at once.
Contact tags are used to link contacts to work items.
The system-default Contacts Tags that are available are:
Primary Contact – the main person you are dealing with for this query. There can only ever be one Primary Contact for a work item. This is mandatory for a Ticket. Depending on Case configuration in Builder, this may or may not be mandatory for a Case (if set as mandatory for Case type, is also mandatory for that Case’s Actions).
Original Requester - the person who initially raised the request. There can only ever be one Original Requester for a work item, and it is independent to the 'Requester' tag. The original requester will be either automatically set in the situation where a valid contact sent in the email that started the work item, or the first person who gets manually set as the ‘requester’ will be promoted to ‘original requester’. The Original Requester tag cannot be changed once it has been set and you cannot remove the contact tagged as the original requester from the work item.
Requester – the person requesting the query. There can only ever be one Requester for a work item. This is mandatory for a Ticket. Depending on Case configuration in Builder, this may or may not be mandatory for a Case (if set as mandatory for Case type, is also mandatory for that Case’s Actions).
Subject – who the work item is about (this may be neither of the above). There can only ever be one Subject for a work item.
Very often all three will be the same person. If you tag another contact as any of these system-default relationship types, the tag will be removed from the previous contact - as there can be only one holder of the system-default contacts in one work item.
When you manually add the first contact to a work item they will be set as the Primary Contact, Requester and Subject by default. You can manually reassign these tags to other users afterwards.
CCs – any further contacts which can be copied on any correspondence. When a contact is tagged only as ‘CC’, it will be displayed in the separate CCs section (hidden until any CC-only contacts exist on the work item.
In addition to the system-default Contact Tags (Primary Contact, Subject, CC, Requester), you can add a further default contact tag to a contact record to make using contact tags on work items faster and easier.
Example: If you know that 'Jane Smith' is always going to be the Broker or any work item you add them to as a contact, you can give Jane's Contact record a default tag of 'Broker' so it gets auto-populated for her in the work item - rather than you having to manually set this tag value each time.
The Default Tags list available to choose from is set in Builder in the General Settings >> Contact Tags section.
You can set this Default Tag whenever you add a new contact into the system.
You can also add the tag to existing contacts and edit the Default Tag set to a contact via the Contacts page.
The Default Tag attribute is also available to edit in bulk, i.e. you can set this for multiple contacts at one time - simply select a number of contact records from the Contacts page grid and click on the Edit button to access the Bulk Edit popup.
If a specific tag value has not been set to 'Allow Multiple', only one contact in a Work Item is allowed to have the value. Example: it may be that there can be only a single 'Broker' contact for Ticket. This obviously impacts default tagging if two contacts with the same 'must be unique' Default Tag get added to a work item, either manually or automatically. In this scenario the system will allocate the Default Tag to only one contact (and therefore remove the Default Tag for the other contacts). The system will allocate to the Contact already tagged with an existing other tag value, in the following priority order.
Primary Contact
Requester
Subject
CC
Any other contact on the work item
You will not be able to add a Default Tag to a contact if the company they are assigned to has a different Supplier Company to the Default Tag.
You will not be able to submit a work item with a contact whose Default Tag is set to a different Supplier Company than the work item.
When an email arrives from an address which is associated with a contact that is already in the system and the contact:
has a Global scope setting, or
they have a Local scope setting but belong to the same company that the work item will belong to based on email routing rules
then their details are automatically populated into the Contacts Card when the work item is created by the system and they will automatically be tagged as the Primary Contact, Original Requester and Requester of the work item. Additionally, if they have a default tag assigned to them, they will also be tagged as that. However do note that you can always go in and manually edit the tags yourself once the work item has been created.
When an email arrives from an address which is associated with a contact that is already in the system, but they have a Local scope setting and belong to a different company than the one the work item will belong to based on email routing rules, their details will NOT be automatically populated into the Contacts Card when the work item is created by the system, (and therefore they cannot be automatically tagged to the work item). Note that you can always go in and manually edit the contact and tags yourself once the work item has been created.
Default 'Global' or 'Global & Local' Scope
When an email arrives from an unknown address and:
your system has been configured to set the scope of your external contacts to 'Global', or 'Global and Local',
then the contact will be auto-created, have a Global scope (i.e. the won't be linked to any specific company) and their details will be automatically populated into the Contacts Card when the work item is created by the system. Additionally, they will automatically be tagged as the Primary Contact, Original Requester and Requester of the work item. As they were previously unknown to the system, they will have no default tag set. Note that you can always go in and manually edit the tags yourself once the work item has been created.
Default 'Local' Scope
When an email arrives from an unknown address and
your system has been configured to set the scope of your external contacts to 'Local',
then the contact will be auto-created, have a Local scope (i.e. they will be linked to a specific company) and they will be created under the company that the work item exists under. Their details will be automatically populated into the Contacts Card when the work item is created by the system and they will automatically be tagged as the Primary Contact, Original Requester and Requester of the work item. As they were previously unknown to the system, they will have no default tag set. Note that you can always go in and manually edit the tags yourself once the work item has been created.
Automatic Contact Creation OFF
When an email arrives from an unknown address and
then the work item will be created based on the email routing rules, but the email sender's details will NOT be automatically populated into the Contacts Card when the work item is created by the system, (and therefore they cannot be automatically tagged to the work item). Note that you can always go in and manually edit the contacts and tags yourself once the work item has been created.
When a work item is created from the 'Start work item' button on the Contact Activity Page of a contact, that contact will be auto-tagged as the Original Requester, Requester, Subject and Primary Contact of the work item, and their Default Tag will be added too (if they have one).
Canned Texts are standard pre-configured texts which are created as part of system configuration.
When writing an email, you can insert a Canned Text by clicking on the Canned Texts icon at the bottom of a write an email screen. This will show you all canned texts available for the Service Line and you can use the free text search function to filter items by title.
You can also use the ‘recently used’ option by clicking on the dropdown list, allowing you to quickly access a more relevant canned text. You can also manually modify canned texts after they have been inserted into your email.
Note: Any files linked to the canned text section will also be attached at the same time.
Show by Language
You can also select a canned text in a different language by clicking on the language in the dropdown list.
Note: The system will show the canned text in your language by default.
You can write a new email from the Email tab of a work item.
You can save an email as a draft, schedule when you want to send an email and send an email straight away.
Note that you cannot send an email that exceeds the size set in Builder.
Once the email has been sent, it will appear in the timeline, where you can see who composed the email, the content of the email if you expand it, when the email was composed and when it was sent. You will also have the option to reply to the email, forward the email, expand the email or print the email.
You can write a brand new email without needing to have the work item assigned to you.
You can also reply / forward emails from the timeline by clicking on the links available. These buttons will be enabled when you mouse over the email card.
System behaviour for entering email addresses is as follows:
When sending a new email, the system will default the To address to that of the Primary Contact in the contacts section. Cc Address will also default to email addresses entered in the Ccs section.
If more than one possible From email address is configured, the system will populate the default one (configured as default in Builder), and will display a dropdown to allow the alternate ones to be selected.
These standard rules for default and suggested addresses can be overridden for To, Cc and Bcc for Cases and Actions in Builder configuration. Addresses set as default will auto-populate (more than one can be set in this way). Override addresses not set as default will be available for quick selection by clicking the To / Cc/ Bcc button address
When searching for a contact in the To/CC/BCC fields, you will only be able to view contacts from the same company as the work item. However, you can manually enter the email address of a contact from a different company.
Note: The From address always displays in the email composition section when you are writing an email. This ensures that the sender will always have a view of the email address being used as the from when sending out emails from a particular work item.
Note: You will only be able to see the email addresses of contacts from companies that you have access to. However, you are able to manually enter any email address. These permissions can be configured in Builder, click here for more information.
When composing emails, you can easily copy email addresses between the To/Cc/Bcc addresses via the ‘copy’ icon displayed when clicking into the relevant address field.
When you send out an email which contains new email addresses (i.e. not linked to existing contacts), the system will display a popup to allow you to create them as new contact records.
If there are any email addresses for which you do not wish to create a new record, simply hover over the row and click the delete icon. Additionally, there is a ‘Do not show this again’ checkbox which when clicked will ensure you are not presented with this popup for subsequent new email addresses (this can be switched back on again in the user profile section where you can also find your email signature settings).
Via the email toolbar you can:
Attach files to the email
Access the email body formatting toolbar
Pin the email body formatting toolbar
Insert a Canned Text
Set the email importance as high
Clicking on the email body formatting icon will formatting options for the main body of the email.
You also have the option to pin the email body formatting toolbar.
The email body formatting toolbar gives you the options to:
Select the font
Select the font size
Make the text Bold, Italic or Underlined
Undo your previous changes (also available with Ctrl + Z)
Redo your previous changes (also available with Ctrl + Shift + Z)
Expand the email to full screen
Select the background colour
Select the text colour
Choose how to align the text
Add a numbered list
Add a bullet list
Text inline options - ability to increase or decrease the text indent
Insert a horizontal line
Adjust the line height
Select an inline style
Format the cell style
Insert a strike through (also available by highlighting the text and Ctrl + S)
Add a subscript or superscript
Add special characters
Insert a link
Insert a table
Insert an image
You also have the option to view a list of keyboard shortcuts
When you compose an email (either as an email template in Builder, or any form of new/response/forward email in Work Items in Work Manager) your font settings (i.e. your font style and size) the font type and font size most recently used will be saved as the font for writing content so you don't need to set them again.
These values are saved to the user profile so will persist between Builder and Work Manager usage.
This only pertains to the front at the very top of the email being composed - if user clicks into any pre-existing content further down the mail, the font style and size already in use for that content will be used. See note for further details. As part of this change, inconsistencies in 'new empty lines' for emails has been resolved - when writing a new email, 2 blank lines will always be inserted that the top of the mail.
Note that the font for canned texts and templates will use the font settings when they were created.
The email font style and size being used when a user is composing a mail will depending on whether they are clicking on pre-existing content. The logic for which fonts will be used is as follows, and is impacted by the new auto-insertion of two blank lines at the beginning of every new email:
1st auto-inserted line: uses the user-saved font settings from their most - recent email.
2nd auto-inserted. This is always set as Arial - 10.
Subsequent email content after this may come from: -previous emails in the mail chain
email template content
email signature content font style and size in these sections will come from that already existing content, depending on where user clicks.
You can copy/paste information into emails from external documents, e.g. Excel tables and Word document content, as well as HTML information from webpages.
If you wish to dedicate more screen space to view emails, you can use the available pop out feature:
The Undo Send setting lets you add a time delay to when your emails will be sent, giving you the opportunity to cancel sending an email, or reviewing an email before it gets sent.
You can set an Undo Send time in User Settings.
When an Undo Send time is set, a popup will appear allowing you to cancel sending the email.
Additionally, when an Undo Send time is set, you will have the option of sending an email 'Now' in the Timeline which overrides the time delay from the Undo Send configuration and you will also have the option to cancel sending the email altogether.
When an Undo Send time is set, emails will be shown in the Outbox page with a Send Status of Queue.
For all type of emails (inbound / outbound / cancelled / failed/ scheduled) you have the option to download the underlying .eml file. This is available from the various locations in the system where emails can be see, i.e. Work Item Comms & Timeline sections, Email Inbox, Sent Items views.
Please note: If the email you are attempting to download contains an attachment file which has been explicitly manually deleted by an user (for e.g. reasons of data sensitivity), the .eml download option will be disabled for that email - the system will display a message explaining the reason for this disabling when download icon is clicked.
You can easily check the spelling & grammar for everything you write in Enate (including your emails) by switching on spellchecker in your browser. For information on how to enable spell checker in the most popular internet browsers follow this link "How to enable spell check in Enate".
The contacts card in the side panel of Tickets, Cases and Actions is where you can specify the people who relate to the work item and set their contact tags.
Clicking on an individual record will display the contact detail's information in a new tab showing the Contact Activity Page.
When an email arrives from an address which is associated with a system user or an external contact which has been previously recorded in the system then their details are automatically populated on the contacts tab when the Ticket is created by the system. They will automatically be tagged as the Original Requester Requester, Subject and Primary Contact. These tags can be removed.
Optionally the first operator to assess the Ticket can also set them as the Primary Contact if deemed appropriated by their assessment. If you tag another contact as any of these relationship types, the tag will be removed from the previous contact.
Similarly, when a work item is created from the 'Start work item' button on the Contact Activity Page of a contact, that contact will be tagged as the Original Requester, Requester, Subject and Primary Contact of the work item.
You can also add contacts to the work item manually by searching for them in the contacts card.
Note that you will only be able to view contacts from the same company as the work item.
If you search for a user in the contacts card that does not exist in the system, you can create a new contact by clicking on the ‘Create Contact’ option and filling in the contact's details.
If you have written the email address for the contact, the system will decode and auto-populate the first name and last name of the contact. Once you fill in all the information and click on create contact, the system will redirect you back to the work item.
When you manually add a contact for the first time, they will be tagged as the Primary Contact, Original Requester, Requester and Subject by default. You can manually reassign the Primary Contact, Requester and Subject tags to other users afterwards, but note that the Original Requester tag cannot be changed once it has been set.
The Contacts Page is where you can view and manage all of your external contacts in one place.
Note: you will only be able to access the Contact Management Page if you have been set up with the relevant permissions in Enate Builder. See here for more information.
You can access the Contact Management page from the Navigation link. Your contacts and their information will be displayed in a table.
Note: Access to this Contacts page is not switched on for standard Team Member and Team Leader Roles. To give users access to this feature, a Custom Role must be created via the User Management section of Builder, with the 'Contacts' option switched.
Clicking on the first name link will open the Contact Activity page.
You can add contacts from the Contact Management page by clicking on the Create Contact icon and filling out the details for the contact in the resulting popup.
You can import a list of contacts from an Excel spreadsheet in the Contact Management page. A template is provided and the template is supported in all of the languages that Enate offers.
It is mandatory to fill in the email address when importing Contacts from an Excel template. If you don't specify a company, the contact will automatically be set to global. See here for more information about company scoping.
To edit a contact, go to the Contact Management page and double click on the contact to bring up the Edit Contact popup.
You are also able to bulk edit the company, time zone, office location, preferred language of your contacts by selecting on the contact's tick box and the edit button will appear.
To delete a contact, go to the Contact Management page and click on the contact's tick box and the delete button will appear. You are able to delete multiple contacts at once.
You can choose which columns to see by by clicking on the cog icon and selecting from your list of Standard Columns.
The Auto-created column option lets you see how external contacts have been created - if they have been created automatically or manually. Please note that once a contact that has been auto-created has had edits made to it, it will no longer display as an auto-created contact in the 'Auto Created' column of the Contact Management Page.
You can add custom columns to the grid by clicking on the cog icon and selecting from your list of Custom Data Columns. Custom Data Columns are created in Builder (click here for more information). Fields of all data types can be created with the exception of Table fields and Long Text fields.
You can sort the table by alphabetical order for a column by clicking on that column's title, and you can go back to the original selection of columns by clicking 'Revert to Defaults'.
This shows emails related to in-progress Work Items in your business areas. There are various filtering options and ways to view different sets of data. Use this view to keep on top of incoming emails for the work items you and your team are dealing with.
By default, emails received within the past 90 DAYS are displayed. Agents can use the Filter dropdown to select a different (e.g. older) date or date range to see emails older than this, but note that the date range specified can only span a maximum of 90 days.
In the collapsible folder pane on left-hand side of the Email Inbox, you can see links to various sections of your Email Inbox, divided into:
My Emails - Emails for all work items that are currently in your Work Inbox (that you'd see in your Homepage)
My Team Emails - Emails for all work items that are currently in the Work Inbox of your Team. This link is visible if you are a Team Leader or are able to see your peers and Queues.
Unassigned Emails - Emails for all unassigned work items sitting in Queues you work out of. This link is visible if you are a Team Leader or are able to see your peers and Queues.
All emails - in this section you will be able to view all emails belonging to work items, including closed items, in your business areas that you have permissions on. In this section you can also filter by the status of the work item that the email belongs to.
The numbers displayed show the number of unread emails in these different folders.
You can see a list of all the emails in your inbox as well as Self Service user comments, with the most recent at the top, showing who the email is from, when it was received, the subject of the email, a preview of the first line of the email body and which work item the email relates to. You will also be able to see if the email has any attachments and if the email was sent with high importance.
Unread emails will appear in bold and you can filter to view just your unread emails by clicking on the 'Unread' option.
Note that an email will be marked as read when a user opens an email.
You can filter your inbox by Customer, Contract, Service, Process, Queue, the 'from' email address, whether or not the email has attachments, and by email received date.
If you have access to the 'My Team Emails' view you'll also be able to filter by assigned user.
For the 'All Emails' section you can also filter by the status of the work item that the email belongs to.
You can switch between viewing 'My Emails' which are the emails in your own inbox, 'My Team Emails' which will show you the emails in the inbox of your team members, 'Unassigned Emails' which will show you incoming emails for work items in your Queues which don't have an assignee, 'All emails' which shows you all emails related to work items, including closed items, in your business areas that you have permissions on and 'Unprocessed Emails' which shows you any unprocessed emails for your area of the business so that you can decide what to do with them.
For My Emails, My Team Emails, Unassigned Emails and All Emails, when a new email comes in the 'unread' number will refresh and a mail icon will appear on the refresh button. You just need to click it to refresh your inbox and view the newly arrived emails.
You can mark individual emails as read/unread, but please note that this will NOT affect the new information flag on the work item that the email relates to, so marking an email as read will NOT switch off the new information icon in the work item.
The main section of the Email Inbox view displays the preview panel for whichever email you have selected. You can adjust the size of the email preview panel to suit your needs.
When you click on a email, you will be able to see the full email in the right-hand side of the screen. You can see the subject of the email, who it was sent from, who it was sent to, any CC recipients, a link to the work item that the email relates to, the due date of the work item and the full content of the email.
If you click on reply, reply all, or forward for an email, the system will open a new tab displaying the Work item in question and will take you to the email editor screen to start composing your email.
Further options are also available from the ellipses next to the reply links. These will allow you to go directly to the work item that the email relates to (opening in a new tab), and to print the email directly.
You also have the option to download the underlying .eml file.
Please note: If the email you are attempting to download contains an attachment file which has been explicitly manually deleted by a user (for e.g. reasons of data sensitivity), the .eml download option will be disabled for that email - the system will display a message explaining the reason for this disabling when download icon is clicked.
If an email has any attachments, you can see the name of the attachment, its size and the option to download it. If the email has multiple attachments, you have the additional options of downloading all of the attachments or downloading them all as a ZIP file.
You can also expand the email to full-screen mode, where the preview pane is hidden.
Some further explanation of how Quickfind works: There are three different kinds of searches going on in parallel when you are entering Quickfind search data:
1) Specific search against reference number. This is based upon recognizing a known format of the system’s refence number for work items and then returning results related to Tickets, Cases, Actions which have that reference. You can just type the reference, e.g. ‘40308-T’ and the system will recognize it as a reference. You don’t need to enter a leading short code.
Note: There's also support for certain formats of your own internal reference numbers. Specifically, Quickfind will recognize text strings made up of a series of digits and a '.' decimal point marker, up to 10 digit characters, i.e. with the format 'NNNNN.NNNNN', no matter where the '.' character appears within this string.
2) Custom Data Field searches. As described above. The system will know to do this kind of search when you enter a known short code, e.g. ‘FN: ’. The search will be for a field which contains the specific value you enter. See further note below on Wildcards.
3) Free text searching for work items, communications and people against anything else you enter which doesn’t conform to the first two types of recognized data. The system free text searches the individual words against various system attributes of work items, communication and people, e.g. work item title, email subject and body.
4) 'Start with' searching for files - the system uses 'start with' logic for searching for files where it adds a wildcard to the END of search texts. This means that if you are searching for a file called 'Invoice Processing.docx', searches for 'processing' would not find the file, but searches for 'invoice' would.
When searching, the system will add a wildcard to the END of search texts, but not the start.
For Custom Data Searches specifically, an example of behaviour would be: searching for e.g. “p:John Smi” would find items with the value “John Smith” in a field ‘person’ but searching just for “p:Smith” would NOT find it.
In short: With Custom Data Field searches, we’re searching for the precise value of the field, or the start of the value. Free text searches aren’t quite the same as this, since a free text search will try to match against each individual word within a text value to get a match, rather than the value as a whole.
Wildcards are added to the end of reference number searches also.
While you are typing in Quickfind, the system will wildcard search against the very last word, e.g. if you’re free text search typing: "John return prio", the system will wildcard the last word and would also bring back results with e.g. ‘priority’.
Once you’ve pressed the space bar the system will conclude you’ve finished typing that word and will search against it without a trailing wildcard.
In order to retain system performance, the following are ignored from searches:
Words of 1 to 2 characters.
Quickfind is a text-driven search. Entering dates in the text strings may bring back inconsistent results. Use “quotes” where possible if such searching is necessary to help the search look for entire strings of characters such as "search for where this entire string occurs".
Use the date sliders to search for results in specific date ranges.
When searching for multiple words, the search will be using an ‘AND’ logic rather than ‘OR’, i.e. bring back items with 'Apple' AND 'Banana' AND 'Pear'.
It’s important to note that Quickfind performs three independent searches,
one for for work items (Cases, Actions, Tickets),
one for the Emails that may relate to them, and
one for people.
An effect of this can be that if you are e.g. searching against a combination of three words, e.g. 'apple' and 'banana' and 'pear', Quickfind will return results of any work items where all three words occur, and separately any emails where all three words occur. Situations where two of the words appear in the work item, and the third only in an associated email, would NOT be brought back by either search.
The specific attributes which the work item searches are performed against are as follows:
Work Item Reference
Title
Customer Name
Supplier Name
Contract Name
Service Name
Service Line Name
Process Type Name
The specific attributes which the Communications searches are performed against are as follows:
Email Title
Email Body
Email Addresses (From, To, CC, BCC)
Internal Note Body (for notes added in Enate / Self Service).
The Outbox Page is where you can find emails belonging to yourself or to your team that are scheduled be to sent at a later date, or have failed to send.
You can access the Outbox Page from the Emails section in the navigation link. The total number of emails in your Outbox will also be shown in the navigation link.
You can select how many emails will be shown from the option on the right.
The first time a Team Leader logs in, they will land on the 'My Team Emails' view. The first time a Team Member logs in, they will land on the 'My Emails' view. You are able to change your view of the outbox page to show just your outbox emails, your team's, the system's or all outbox emails. This will be saved when you log out and log back in.
Selecting 'My Emails' lets you see emails sent by you that are in your outbox.
'My Team Emails' shows you emails sent by your team that are in the outbox, as well as emails relating to work items that your team members are working on that are in the outbox.
Selecting 'System Emails' lets you see emails that are sent automatically by the system e.g. because a Ticket has been split or merged.
'All' lets you see emails sent by you, your team, as well as emails from outside of your team for which you have access.
You are able to manually retry sending an email by clicking on the Retry icon. The email will now be in a state of 'Pending Retry'.
You can also retry sending an email from the timeline of the work item itself.
You are also able to cancel sending an email by clicking on the Cancel icon. This will remove the email from the Outbox.
You are also able to retry or cancel sending emails in bulk.
Please note that the system will not automatically retry sending emails that have been migrated from an older version (2020.1 or older). These can only be sent by retrying manually, i.e. clicking the 'Retry' icon.
Double clicking on an email will open the email's details in a popup in read only form. You can see who the email is from, who it is to, etc. You are also able to retry and cancel sending the email from the popup.
You can adjust the grid columns by clicking on the settings cog. These will be saved when you log out and log back in. The 'To' and 'Subject' columns are mandatory.
Importance - the importance setting of the email i.e. high, normal, low.
System Generated - if the email was automatically generated by the system (e.g. to notify a user when a Ticket has been split).
Last Attempt To Send - when the last attempt to send the email was (automatically by the system or manually by a user)
Last Send Failure Message - a message displaying the reason why the last attempt to send the email failure e.g. The Email connector is disabled. Please enable it and try again.
Logged - the date and time recorded when the email first failed to send.
Next Attempt To Send - when the system will next try to send the email
Packet - the work item reference that the email is from. Clicking on this will take you to the work item screen.
Packet Type - if the email is related to a Ticket, Case or Action
Send Status - this shows what status emails in the outbox are in in terms of sending. There are 4 states:
Failed - an email with this Send Status has failed to send. In order to send it, it must be manually 'retried'.
Pending Retry - an email with this Send Status is awaiting automatic retry by the system.
Attachment Count - how many (if any) files are attached to the email
Unprocessed Emails - here you'll be able to see any such unprocessed emails for your area of the business, and decide on the what to do with them. The number next to this section shows you the total number of emails in the section. .
There's also links to your and your - all of which open in separate tabs.
For Unprocessed Emails, the number next to this section shows you the total number of emails in the section. .
Words in the system 'Stop List'. These are standard common words such as ‘and’ ‘the’, ‘me’ etc., which would otherwise return too many results. Please see here for the (in Quickfind and indeed in any other system searches).
Specific characters which are set to be ignored, e.g. “*”, “?”, “@” etc. in Quckfind specifically. Please see here for a . This will mean for example that when searching for customer.com in Quickfind, the words 'customer' and 'com' would be searched for. As such, it’s recommended to place such word combinations in quotes to search for them as a specific phrase - i.e. searching for “customer.com” will likely bring back the results you are looking for.
Additionally, the system can automatically retry sending emails if your system has been set with an Automated Failure Retry Pattern (). Once the system has retried sending an email the maximum number of times specified, it will no longer retry sending it automatically, but you can still retry sending the email manually, i.e. by clicking the 'Retry' icon.
Email Connector - the name of the email connector through which your system sends emails. This is configured in Builder, .
Send Retry Count - this will show the number of times the system has tried to send the email. You can set this number in Builder, .
Connector Disabled - if an email has this Send Status, it means that the Email Connector has been disabled in Builder. .
Queued - an email with this Send Status is already scheduled to be sent. Emails send when an Undo Send option has been set will have this status too (). When these emails will be sent depends on the Automated Failure Retry Pattern option which is set in Builder, .
You can view the unhandled incoming emails which were deleted by you / your team as part of dealing with them with the 'Deletion Audit' section of Unhandled Emails. This helps with an auditing how incoming emails which were unhandled have been dealt with.
Clicking on this 'Deletion Audit' link will bring up a view of all deleted unhandled emails within your area of the business. These are incoming unhandled emails where the decision was made to delete these mails rather than create a new Case or Ticket from them.
All filters and paging options are available as for the other email views in this page, but the emails themselves are shown in read-only mode..
Clicking on a deleted unhandled email will display the email in detail in the main section of the screen, with any attachments that it may have had.
Additionally, the header bar above the mail shows who deleted the email and when.
Note: You cannot 'undelete' emails which have been deleted, however if you wish to copy body text information from them you can do this by simply selecting the desired text and copying / Ctrl-C.
As part of dealing with Unhandled emails, agent users can create email routing directly within Work Manager. Creating these rules helps stop equivalent future emails from landing as Unhandled emails, ensuring that a Ticket or Case gets created for them. This reduces future Unhandled email volumes and makes sure work can start on these items more quickly. To provide an element of control, the ability of Work Manager users to create new email routes is an option which can be turned off/on in via User Roles in Builder.
Once these rules are created in Work Manager they're instantly live and working, however Admin users in Builder are notified of any new routing rules created in this way, and these remain marked for their attention until the Admin acknowledges them. Admins still have the ability to adjust or even turn off such rules after assessing them.
Feature Access to be able to create new Email Routes in Work Manager is controlled via Enate's User Role system, with a new option being added to the Email View Options section.
Note: This 'Create Email Routes' access will be set to ON for the Standard Team Member role
While dealing with an unhandled email in the Unhandled emails section of the Email Inbox page, if you choose to have the email processed into a Ticket / Case (by clicking 'New Work Item' option), you'll be met with the following popup:
You can search by email route (which will auto-populate the Customer/Contract/Service/Process fields based on suggestions for the mailbox address selected), or can manually select. Clicking Create at this point will create the specific Ticket or Case from the email, as normal.
However, if you also wish to have the same thing happen automatically ongoing, you can click on the 'Apply to other emails' link at the foot of the popup before you hit 'Create'. If you've selected this option, when you hit 'Create' two things will happen:
A small confirmation message shows confirming that a new work item has been created.
A further popup screen to 'Create New Email Routing Rule' is then shown where you can fill in the remaining routing rule details before confirming its creation.
You can decide if the route is going to be a 'To' or 'From' type of route, i.e.
'treat all emails FROM this address in the same way', OR
'Treat all email TO this address in the same way'
and then which email address is to be used in conjunction with this. Enate will automatically fill the email address with the relevant email address associated with the unprocessed email you were working on.
Within the 'Tips' section of this pop-up, there is a link that will take users to the Unhandled Emails page of the Enate online help, should users require any more information.
In addition to setting a rule which will deal with all future emails that match this pattern, you can also choose to have the rule run against all/some of the existing Unhandled emails which match this rule. If you wish this to happen, select the 'Auto-apply' toggle and this foot of this popup.
The system will show you how many of the current backlog of Unhandled emails match this rule, i.e. how many would be reprocessed.
Selecting this option will bring up a time filter allowing you to select a subset of these existing emails to run the rule for (if, for example, you only want to run this for emails up to a week/month old etc.
You can use the slider to set different date ranges, including setting specific dates. As you change this setting, the system will update to reflect how many emails this would run the rule for.
When you're happy with your selection, you can hit Create - the rule will be re-run and emails will start to be re-processed into the type of Case or Ticket you specified.
Important Note: Once you create a new email routing rule in this way via Work manager, it will instantly go live and start to run against any subsequent incoming emails.
If any new email routes have been created in Unhandled Emails in Work Manager, Admin users will be made aware of this in Builder by a red dot on the Email icon section.
Throughout any subsequent navigation sections and screens as they drill down to the Email Routes page, there will be continued signposting down the new Routing rules that they should be aware of.
Once on the Routes page, users will see a banner notifying them of new email routes to be aware of, as well as how many there are. A link will allow them to filter the routes down to just those new ones that they need to be aware of.
Within the routes table itself, users will be alerted to these new routes to be aware of.
Admin users are encouraged to review these new routing rules (and speak to the agent who created them*) to make sure they're happy with how they are running in conjunction with the various other rules. They can choose to unset them from live, make any adjustments and even delete them if they feel necessary.
If they're hapy with the rule they shoud unmark the 'be adjusted, They can use the 'Clear review filter' link in the header to return to the normal view.
*You can view who created an email routing rule from the 'Show Activity' icon in the top of the rule details popup.
Clicking on this will show the audit trail of who created and updated this rule.
Emails will appear in the Unhandled Emails view of your 'Email Inbox' view in Work Manager if they meet one of the following conditions:
None of the To and/or CC email addresses have a matching email route.
There are only BCC email addresses in an email, no To or CC addresses.
See the table below for further detailed information on how emails arriving into Enate are treated, depending on the combinations of Enate-relevant email addresses may appear in the TO, CC or BCC fields.
Scenario
Number of work Items Created
Will they appear in the Unhandled View
Email to just one email address in either the TO or CC field
1
No
Email to 2 or more email addresses in either TO or CC field
2 or more
No
Email to 1 email address in TO, another in CC field, and one in BCC field
1 for each TO & CC address
No
*Email to 1 email address in TO and another in BCC field
1 for TO field
No
Email to 1 or more email addresses in BCC only. Nothing in TO or CC fields.
0
Yes - for the BCC email mailbox
Email to just 1 email address that is not correctly configured in Enate
0
Yes - for the non-configured email address
Email to 1 email address that is not configured correctly in Enate and one email address configured in Enate
1 for the configured email address
No
Enate's browser-based Work Manager uses a multi-browser page approach. You can control how you want the system to behave when you click on links to open new items, for example to open a Ticket or Action from your home page, or to open up your Email Inbox page.
You can choose between links opening in a new, dedicated browser tab or in your current browser tab.
Watch this video to find out more:
As a default, when you click on a link the new content will show up in the same browser tab, replacing the previous content.
If you want to return to the previous page, you can use the browser's 'back' button to navigate back there, and equally use the forward link again to return to the newer screen.
Some other features which can be helpful when working with a single tab approach… The 'recently viewed' list from your navigation section is always a useful way re-find work that you've been looking at recently. You can click to open up a fresh Home page at any time… And, you can even use your focus list to put together a list of work items that you want to concentrate on, perhaps as part of a focused daily to-do list.
If you'd like to open a link in its own dedicated tab, you can right click on a link and select the 'open link in new tab' option from the subsequent menu.
Or you can hold down the 'control' or 'command' button on your keyboard when clicking the link.
This will open it in a new browser tab and leave the previous one as-is.
If you'd prefer that the links you click on to open in new, different browser tabs, every time you click on a link, you can do this by changing your User Settings.
This means that you can view content in separate browser tabs and can have two sets of content open side by side, letting you, for example have your Email Inbox open at the same time as viewing a ticket or action, so you can read mails without swapping between screens. The browser tab will show information such as the work item reference and title.
Each tab has a dedicated URL which means you can easily share links to specific work items to other team members. Just copy the URL and send it to them - when they open the link it will take them straight to that work item.
When you perform an update on a Work Item that would close the tab, you'll be returned to the page that launched it, for example your home page or Email inbox page.
If you're opening items from the Advanced Search page, save your search if you want to return to the page with the previous filters still set.
If you want to change how the system opens up links, you can go to your user settings page and change the tabs behaviour.
You'll see the 'Open Links in New Browser tab' option. This lets you decide how you would like the links you click on in Enate Work Manager to open - either in a new, dedicated browser tab or in your current browser tab.
By default, this option is set to OFF, meaning that when you click on a link the new content displays in your current browser tab. If you'd prefer that the links you click on open in new, different browser tabs, switch this option to ON and save your change. Now when you click on links, you'll see that a new dedicated browser tab will open up to show that content.
Work can be created by users from within Work Manager in two ways:
From Create New Work Item. This is a dropdown available from the toolbar, the agent selects a Case or Ticket to start under a specific business context
From the Contact Activity page, often also referred to as the Call Handling Page. From this page, the service agent would first search for and find a person (often someone calling in to the service centre), and then start a piece of work directly for them, i.e. a Ticket or a Case
You can create work by clicking on the ‘Create’ link in the header bar (cube image). This will produce a dropdown screen section allowing you to start a new work item. The hierarchy displayed in the dropdown goes Company, Contract, Service, Process Group (if Configured) followed by the Cases that can be created.
Input links automatically appear here for Tickets and Cases when you have created a Ticket or Case process in Builder and set it to Live. Clicking on a link will create the new work item in a separate tab.
Note: When running in Test Mode, processes which are in a state of ‘validated draft’ will be displayed here
You can create work by clicking on the 'Start New Activity' dropdown on the Contact Activity page.
If you are on a contact page for someone under a known company (i.e. scoped at customer level), the Customer information will not display in this link name. A free text search will allow you to filter this list of links. Administrators can control whether you wish to see the Input link for a given Ticket / Case process via settings in Builder
Creating a work item from the contact activity page will automatically assign the contact as the primary contact of the work item.
The Focus List enables you to put together a list of work items that you want to concentrate on, perhaps as part of a focused daily to-do list, or as a handy shortcut to get to the items you're needing quick access to.
Watch this video to find out more:
You can add Tickets, Actions and Cases to the list, even ones which aren't assigned to you, up to a maximum of 50 items. You can get to your Focus List from anywhere in Work Manager by clicking on the Focus List icon in your header bar.
Clicking on an item in your list will take you directly to that work item, either in a new browser tab or in the existing view if you're set to open up links that way.
You can add items to your focus list in a few different ways:
Firstly, you can add them from within the Focus List itself by clicking on the plus icon and then searching for either the title or reference number of the work item you're looking for. Select which work item or items you want to add from the search result and click to add.
Another way is to click on the 'Add to Focus List' icon from within a Ticket, Action or Case.
And you also can also add items to the list from the homepage grid by selecting one or multiple items and then clicking the 'Add to Focus List' option that appears in the grid header.
Once they're added, work items can easily be arranged in your list, just drag and drop to relocate them.
If you're accessing a Ticket, Case or Action which is already in your Focus List, you'll be shown that with the ticked Focus list icon. You can click on that link again to remove it from your list, or, alternatively they can easily be removed from with the list itself - select one or more, click the remove link and then confirm.
One thing to note is that once a work item moves to a state of Resolved or Closed, it will automatically be removed from your focus list, freeing up space for other open items you want to focus on. However, users can still add items in either of these states into the Focus List if they want.
Additionally, when a user tries to open multiple links in new tab from the Focus List, occasionally they might not be able to and will instead be shown a pop-up stating that multiple tabs have been blocked from being opened. Users simply need to click to allow pop-ups and redirects from Enate.
There are certain circumstances when clients may send in an email that should really be used to start a new work item but, because they've sent it as a response to an existing mail chain, it ends up being attached to an existing work item. A prime example of this is when a client responds to an email with the intention of starting a new ticket but it gets added to the work item of the email chain that they were replying to. In such circumstances, you can use a feature that allows incoming emails that get added to an existing work item like this to now be used to create a new work item.
If a user is working on a work item and realizes that an email that has been attached to it should actually be used to start a new work item, they can use a link now available to them when hovering over that mail in the Comms or Timeline view.
Clicking this link and then the following confirmation popup will result in the email being effectively sent back into Enate, but with an additional rule that it should not append itself to an existing work item. Once the email has successfully created a new work item, a confirmation message will appear.
Once the new work item has been created, a note will show at the top of that mail with a link to that new work item, and that original mail entry in the first work item will effectively be set to 'read only' (since it should no longer be used to process the request within that mail).
Links between the original work item and the new work item will also be displayed on each of their respective 'Linked Items' tabs.
It should be noted that this option will never appear on the initial email which creates a work item, only on subsequent incoming emails which could be inappropriately appending.
When you're working on a Ticket, Action or Case, operational issues can occur which have an effect on how you're able to deliver the process. It is important to record these as a way to highlight them for others who may view or work on the item, and to help with longer term efforts to improve process delivery.
The Defects section on your work item screens in Enate is there to help you record and manage incidents like this when they occur. If defect categories have been configured in the service line for a Ticket in Builder, a Defects Card will show in that Ticket's screen in Work Manager that provides the functionality to record defects for the work item.
Defects can occur for a wide variety of reasons, for example:
A client is late supplying information you've requested
A supplier has attached the wrong file
Something's gone wrong as part of the service centre's handling of the activity.
It is very important to record defects, for various reasons:
while the work item is still in progress, it gives other agents who might be viewing or working on the activity an instant heads-up of issues which have occurred or are still happening which they'll likely need to know about
after a work item has been closed, it helps serve as an accurate record of what went on and what went wrong - which might be important if you're reviewing a specific item and need to be able to explicitly show for example when a client took longer responding with critical information.
in the longer term it's really useful as part of analysis to spot patterns in where issues are occurring and where improvements can be made - perhaps there's a repeated quality issue with information from an external party, or a given customer if consistently late supplying information at a certain point in process. If defects aren't recorded, it's likely otherwise resolvable issues will still continue to happen.
It is important to note that the defects feature isn't linked to the way the Enate system determines SLA information.
Recording a defect is simple - with a Ticket, Action or Case open, simply expand the Defects card and click to add a new record.
Select the relevant category that the defect falls under.
If you're finding that some options are missing from the category list, i.e. a type of issue is happening regularly but there isn't really a sensible category for it, feed this back to your business admins and request to get it added to the category list.
Select the area of responsibility from the ‘Party at Fault’ drop-down - e.g. your organisation, a third party supplier, or the client themselves
Then add a relevant description.
If your system is set up to do so, you can also add the number of affected records - an example of when this can be useful is if your were running a payroll process for 100 employees and a defect occurs affecting 20 payslips, you can add that extra detail in here, which can be useful for subsequent reporting.
You can add as many defects as are needed if multiple issues occur.
Once you have recorded a defect on a particular work item, it is shared with all related cases, tickets and actions in the same manner as contacts are.
If a defect gets resolved while the work item is still open, you can go to the defect card and mark it as resolved.
If a defect was applied to a work item by accident or the defect itself was recorded incorrectly, you can chose to delete it as long as the work item is still in progress.
Any user can add a defect and mark defects as resolved. However, be aware that if the 'Restrict Defect Modification' setting in the System Settings section of Builder is enabled, only the agent who created the defect record can subsequently modify or delete a defect.
Once you're happy with all the details for your new Defect record, or with your changes if you're editing an existing one, click 'Submit' to save your changes.
Click the Note tab to add a note. Anyone can add an internal note to a Ticket, Case or Action – you don’t have to have it assigned to you, and adding a note won’t auto-assign the work to you. These are notes for internal use and the external contacts won’t ever see them.
If desired, you can specify which kind of interaction resulted in the note, e.g. phone incoming / outgoing etc.
If we we are adding a note to a Ticket assigned to ourselves, we have the additional option of Adding a Note & Resolving the work item which will resolve the work item when we click on it.
After adding the note, the screen will refresh with the new note displayed on the timeline.
If you have started to enter a note but have not saved it, the tab will display a ‘*’ marker on the tab alerting you to this.
If you subsequently try to close the work item tab with this ‘in-progress’ items still unsaved, the system will alert you asking if you wish to proceed.
The timeline shows the history of activity that has taken place for a work item in a chronological list. It is divided into the which shows the communications history for the work item and the which shows all of the activity that has taken place for the work item. See the following video for more information.
The Comms tab shows the communications history for a work item, such as emails, log activity and notes. For Tickets and Actions, the timeline section will display the Comms tab by default.
The communications will be displayed in chronological order with the most recent at the top and the most recent email communication will be auto expanded by default. You can expand items to view them in more detail.
Incoming communications which have arrived on the work item since it was last accessed by an agent will display on the timeline with a green dot to make you aware of the new communications. The green dots will clear after any manual update is made to the work item and you hit ‘Submit’. The system does not clear the green dots based purely on the work item being viewed, as it could be viewed by multiple parties. Instead, in order to ensure that the agent tasked with working on this item is aware of such recent updates an explicit update to the work item is needed before the green dot will clear.
Additionally, if another Ticket has been merged into the work item you are currently viewing, any communications from that now merged Ticket will initially display on the timeline highlighted with green dots to make you aware of the new relevant communications. These will again clear the next time the work item is manually updated.
You can choose which communications you wish to see on the comms timeline by clicking on the filter icon.
The number next to the filter icon lets you know how many types of communications you are able to see out of the total number of types of communications available.
You can choose to filter the Comms tab by the following communications:
Cancelled - this shows emails that have been cancelled, when they were cancelled and who they were cancelled by
Failed - this will shows emails that have failed to send and why they failed to send. Note that you can try to resend failed emails from the Timeline section by clicking the 'Retry' option.
Incoming - this will shows emails coming in from a third party, when they arrived and who they were sent by
Outgoing - this will shows emails going out to a third party, when they were send and who they were sent by.
Scheduled - this will shows emails that are scheduled to send at a later date, when the emails are scheduled to send and who and who set the schedule. You also have the option to send the email now or to cancel the email from the Timeline. Additionally, when an Undo Send time is set, the option to send emails straight away or to cancel sending the email
Log Activity
Incoming and outgoing phone calls
Incoming and outgoing letters
Notes - this shows the notes that have been added to the work item
Self Service - this shows communications entered by self Service Users
(If the work item is a Ticket) Ticket Initial Description - this shows the initial description under which a Ticket was submitted
When this is switched on, the comms tab will display communications not just from this work item, but for all related work items.
When a related work item appears on the timeline, its reference will be displayed in the timeline.
This setting is switched on by default for Cases so that when viewing a Case, you will also be able to see communications for all of its corresponding Actions.
This option is switched off by default for Tickets and Actions, so they will default to only displaying communications from this work item.
When switched on, system-generated communications such as auto-created submission confirmation emails which Enate sends out will be displayed. This option is off by default.
The timeline tab shows the all of the activity history that has taken place for a work item, such as allocation changes, status changes and information about the quality of the work item, as well as all of the communications information that is also displayed in the comms tab.
The items will be displayed on the timeline in chronological order with the most recent at the top.
You can choose which activities you wish to see on the timeline by clicking on the filter icon.
The number next to the filter icon lets you know how many types of communications you are able to see out of the total number of types of communications available.
In addition to all the communication options, you can choose to filter the timeline tab by the following information:
Allocations
Queues - when the work item has moved to a different Queue
Reassignments - the shows when the work item has been reassigned to another user
Case Rework History (Cases Only)
If a Case has been set to rework, the timeline will show who set the Case to rework, when it was set to rework, and the Step number and Action it was set to rework from.
Email Attachment Deletion
This shows when an email attachment has been deleted. It includes the file name of the email attachment that was deleted, the subject of the email it was attached to, who deleted it and when it was deleted.
Quality
Due Date Missed - this shows when the due date for the work item has been missed
Due Date Changed - when the due date of the work item, the timeline will show when it has been changed to, who changed it and when they changed it
this shows when the work item status was changed, what is was changed from and to (e.g. status changed from In Progress to Resolved), who it was changed by and the reason it was changed. The icon on the left will reflect the status the work item was changed to.
If the status has changed to Wait, the Timeline will also show the Wait type
If the status has changed to Resolved, the Timeline will also show the Resolution Method
when a Peer-Review Action is in the peer review stage
If a Case has a problem
Include Related Work Items
When this is switched on, the timeline will display information not just from this work item, but for all related work items.
When a related work item appears on the timeline, its reference will be displayed underneath the icon.
This setting is switched on by default for Cases so that when viewing a Case, you will also be able to see information about all of its corresponding Actions.
This option is switched off by default for Tickets and Actions, so they will default to only displaying information from this work item.
The one exception is when merging a Ticket, any Tickets which were closed due to merging will default to display the information from the downstream related Ticket.
When switched on, system-generated timeline entries such as auto-created submission confirmation emails which Enate sends out will be displayed. This option is off by default.
You can view when work items have been reopened from a resolved state in the timeline, as well as when it was reopened and by whom.
The information about who last reopened it and when is also shown explicitly on the work item info card.
The Bulk Create feature lets you create large numbers of Cases and/or Tickets via the uploading of data from Excel spreadsheets.
You can find a link to the Bulk Create page in the ‘Bulk Create’ link in the ‘Create New Work Item’ dropdown.
You can download a template of the excel file. The excel templates available will conform to whichever language you currently have set in your Enate user preferences.
Once you have added the data into the excel file, save and close it, then on the Bulk Create screen click to select the file.
Once you are happy, click on the ‘Upload’ button. This will upload your information about the Cases or Tickets from your file on-screen.
You will see the following information:
Total – the total number of items contained in the uploaded file that will be created
Created – the number of items that have been created successfully (this will be zero before you start to create)
Not Started – the number of items that are waiting to be created
Additionally, in the grid you will see that a 'Status' and 'Reference' column have been added - these will be filled in by the system when the items get created.
All you need to for now is to click ‘Create Items’ and the system will start creating your Cases/Tickets. The information displayed will update to show the number of items that have been successfully create and the reference numbers of the work items created.
It should be noted that excel uploads of up to 2000 rows are supported in bulk create. Sheets with more rows than this can lead to potential errors.
If you are using version 2022.5 or above of Enate, please use the in-product templates from the bulk create page. If you are using version 2022.4 or below of Enate, please use the templates below
You can download the excel file templates to bulk create Tickets from the following links:
You can download the excel file templates to bulk create Cases from the following links:
The mandatory fields which must be filled in order to create a Case are:
Customer
Contract
Service
Case - the process name
Title - the title for the individual Case work item.
The mandatory fields which must be filled in order to create a Ticket are:
Customer
Contract
Service
Ticket - the process name
Title - the title for the individual Ticket
Ticket Description
Ticket Category Level 1
Ticket Category Level 2
Ticket Category Level 3
Any contact records used in a bulk create file i.e. Primary Contact, Requester, Subject and CC contacts must adhere to the following rules:
the email address of the contact must be used
the contact must already exist in the system
Optional fields that can be filled in for both Tickets and Cases are:
Do Not Send Automated Emails To Contacts - whether or not you want to send system-automated emails, such as request acknowledgement emails, to the contacts of the work item. Enter 'True' or 'False', this also applies for languages other than English.
Please be aware that any dates entered must have the following formatting:
DD-MM-YYYY HH:MM
Note that hours and minutes entered can either be in the 24 hour system format i.e. 23:00 or in the 12 hour system format with an AM/PM after it i.e. 11:00 AM.
Valid date format examples:
25-05-2022 23:25
25-05-2022 11:25 PM
If you choose not to enter hours or minutes, the system will set a default time of 00:00.
You can also pass custom data fields into the Cases/Tickets as they are being created. To do this, add a column name which precisely matches the data field name in Enate. If any of these bespoke fields are marked as mandatory in your Case process configuration, you MUST supply a value in this field’s column for every row in the upload file (otherwise that row will fail validation and a Case will not be created for it).
Bulk create supports below list of custom field type:
Check Box
Decimal Number
Email Address
List
Long Text
Multiple level list
Short Text
Whole Number
Bulk create does not support below custom field type:
Tables
Entity Relationship
Additionally, the following system property fields are not supported when bulk creating work:
Keep with me
Keep Action with me
Defects
Files
If you do have any validation errors, these will be highlighted in red and a ‘warning’ status icon will be displayed. If the input values are wrong throughout an entire column, validation errors will be displayed at the bottom of the grid e.g. if a field column is referenced in the upload file which does not exist in the system. If the input values are wrong for an individual row, a ‘warning’ status icon will be displayed at the start of the row and the individual validation errors will be highlighted in red. You will then need to modify the file, click to 'change file' and select to upload your updated file.
You can still proceed with creation of the valid Case items in your upload file. The system will skip over the invalid rows and confirm creation of the valid ones, but the invalid items will need to be resolved before they can be created. You can do this by modifying the file and then clicking to 'change file' and select to upload your updated file.
Click here to see the full list of potential validation errors for Bulk Create:
Bulk Create is also supported in all of the languages that Enate offers: French, German, Spanish, Portuguese Brazilian, Romanian, Polish, Hungarian and Russian.
Note: the bulk create template uploaded should be in the same language as the logged-in user’s preferred language. For example, if a Spanish user wants to upload a bulk create template, then the template they upload should be in Spanish.
Clicking on the 'Pull from Queue' button in the Work Inbox grid header will assign you a new piece of work, if any is available for your to do.
How does the system determine which work item to give a user when they click the “Pull from Queue” button on their Work Inbox?
The system works by looking at all unassigned work items from all of the Queues the user is linked to, and has permissions on, and assigns one new work item, prioritising items as follows:
Any currently OVERDUE work item (most overdue item first). If none found, then
Any work item which has been rejected by a Robot. If none found, then
Any work item (item due soonest selected first).
Note: Queues set to ‘strict mode’ are there to allocate work strictly to robots. Any human users linked to such queues are there only as a fall back for rejected robot work items, and aren’t auto-allocated the normal, unrejected work items from them when hitting “Pull from Queue”.
All emails arriving into Enate get automatically processed into either Tickets or Cases based on business rules which look at things like where it's sent into, who it's from and what it's about. Occasionally though, emails arrive into Enate and do not get processed into a Case or a Ticket.
This can happen due to the following reasons:
None of the To and/or CC email addresses have a matching email route defined for them in Builder (that's the rules which say which kind of Ticket or Case an incoming email should generate).
There are only BCC email addresses in the email, no To or CC addresses.
If there any such emails in your area of the business, you'll see an icon in your header bar showing you how many.
This will show the total number of currently unhandled emails and, if you click the link will also show a popup showing how many of these have arrived in the past 24 hours, plus a link to take you straight to the Unhandled emails section of your Email Inbox page (alternatively you can find it within your Email Inbox view).
The Unhandled Emails view in the Email Inbox section in Work Manager allows agent users to review these unhandled emails and take the appropriate steps. This option is visible to all users.
You'll see emails that have failed to process into a Case or Ticket (i.e. they're unhandled) which have come into the mailbox that your area of the business works out of. Other unhandled emails which arrive into mailboxes that aren't linked to any of your business processes will be seen by agents in other areas of your business.
More specifically, if you have permissions on a process connected to an email route, you'll see the unhandled emails for any email that comes into that email connector, even if its from a different route.
The number next to this section shows the total number of emails in the unhandled email view.
You can filter the emails in this section by:
Mailbox Address
Mailbox Name (if you know it). Specifically, this is the email address of the mailbox which handles the incoming mails.
Date, i.e. the date which the email arrived.
The Unhandled Emails view will let you review the incoming email's content to help you determine where you should route.
Once you've determined where it should go, you've got a couple of options:
1) You can decide to create a work item from the email, specifying a Customer, Contract & Service for it, before launching the work item. If you do this, the email will be changed to 'Processed' and will be removed from the Unhandled Emails view when you next click to refresh your email inbox.
2) You can decide to delete the email if appropriate (for example if it's a spam mail). If you do this, the email will be changed to 'Deleted' and will be removed from the Unhandled Emails view when you next click to refresh your email inbox.
There's also an option to delete multiple emails in Bulk. Click on one or more boxes and a delete button will appear next to the filter, along with the number of emails selected.
Note: Users will be able to create a new work item from an unhandled email on this page even if they do not have the 'Can Create' permission set for them.
If you find yourself regularly having to pick up unhandled mails and route them into the same tickets or cases again and again, you've got a couple of options:
will appear in the Timeline during the Undo Send period () when scheduled emails are set to appear in the Timeline.
If a work item has been reopened as a result of an email, 'System' will be shown as who reopened the work item, so make sure that the option in the comms/timeline filter is enabled to see these timeline entries.
If a work item has been reopened by an agent, make sure the '' option from the timeline filter is enabled to see these timeline entries.
This will bring up the Bulk Create screen in a new tab. From this screen select whether you want to bulk create Cases or Tickets. You can then download the relevant Excel template, populate it, then upload it to the page - making sure to fill in any beforehand.
You can then choose if you want to allow work items with duplicate titles to be created by using the ‘Unique Title’ option. Leaving this option off allows work items with duplicate titles to be created. Switching this option on will ensure that any work item which is due to have the same title as another item in the upload file will .
Issues – the number of items with (these need to be fixed before the items can be successfully created)
Note that the Primary Contact and Requester fields are only mandatory for a Case when the '' option is set to 'on' for the Case type you are bulk creating in the Service Lines screen in Builder. If you do want to fill these fields in, make sure to.
Primary contact - the main contact you are dealing with for this query. .
Requester - the contact that raised the initial request. .
Note that all data entered must match existing values in the system, otherwise will be displayed.
the contact must be that the Case/Ticket will be created under
Subject - the contact the work item is about. .
CC email address(es) - any further contacts which can be copied on any correspondence. . Also note that when adding two or more CC email addresses, please make sure to separate the addresses with a semi colon (;) with no spaces either side e.g. user.one@example.net;user.two@example.net.
Override Due Date - enter the new due date. .
Date Only - .
Date and Time - .
Hyperlink - note that hyperlinks with customised display text are not supported i.e. the text entered in a hyperlink field must be the entire URL of the hyperlink e.g. and NOT
Additionally, the column header values in the bulk create template should match the values that are configured in Enate Builder in the . If the translations for fields like Primary contact, Requester, CC, Subject or any Custom Data Fields have been modified in the Localisations page, then the column headings in the bulk create template need to match these values.
Note that it is not currently possible to append an unhandled email to an existing work item, only to create a new work item. However once you have done this, you can still use the feature to merge it in with an existing work item.
You can speak with your Business Admin to see if a new can be set in order to catch these emails and automatically create the relevant Work Item for them.
Alternatively, you can resolve the issue at source and create a simple Email Routing Rule yourself, from within the Unhandled Emails view. See '' for how to do this.
And, for more information about how Enate processes incoming emails, .
The Ticket screen has the same overall layout as the Case and Action screen, and the same basic features including adding a note to a work item, sending an email, viewing the files and links attached and viewing the comms/timeline, but it also contains some Ticket-specific features. Watch this video to find out more:
At the top of the Ticket screen, you'll see the title of the Ticket.
Depending on Builder settings, this may be editable throughout the duration of a Ticket.
The title of the Ticket that will appear at the top of the Ticket's tab.
And the title will appear in the 'Title' column of the homepage grid for the Ticket.
You can copy the Ticket's reference and number by clicking on the copy icon in the tab:
The Ticket's due date will display, colour-coded to show if the date is:
On schedule:
Due today:
Late:
If a Ticket has been configured with an override due date option in Builder, then you will be able to override the due date of a Ticket by clicking on the due date in the header and changing the date in the popup.
Please note that if you change the category of the Ticket to a category that does not allow the option of overriding the due date, then the system will recalculate and use the due date that has been configured for that category in Builder.
You can also see whether or not the Ticket has been assigned, and who to.
You are able to reassign and unassign an Ticket, or assign the Ticket to yourself if it has not been assigned to you already.
See here for more information about assigning work in Enate:
In the Info Card you can see the status of the Ticket and change the status as needed.
The main label on the left side of the Info Card will display the status the Ticket is currently in. The dropdown button on the right side gives options for the states which you can move it into as part of processing.
See here for more information about processing a Ticket:
Once you have selected the new status from the dropdown and filled in any further required information, click the button to confirm.
The border of the Info Card highlights in a colour relating to the current status – once you have clicked the button to change status, the system will process the changes – the border colour and new status will change to confirm that the status update has occurred.
When changing the status of a work item, if you are moving it to a state of 'In Progress', the work item tab will remain open upon confirming the new status. When changing to any other status, e.g. 'Wait' or 'Rejected', the tab will automatically close. A label under the Status will inform you of this in advance.
In addition to showing the Ticket's status, the following information is displayed directly underneath:
Set by - who set the status
Reason - the status change reason - i.e. why was it changed, this could be manual or as part of a process)
Date - when the status was changed
Last Updated By - who last changed some data on the Ticket
Last Updated On - when some data was last changed on the Ticket
Note that not all of the above information will be displayed every time, the information that is shown depends on the status of the Ticket and how the Ticket has been configured in Builder.
The Settings Card shows you detailed information about the Ticket, including:
The name of the Ticket process
The Ticket's context (Customer>Contract>Service>Ticket Process), plus the Ticket's category and sub categories. These can be modified by expanding the card
Expanding the Settings Card will show you:
The name of the Ticket process
Editable versions of the Ticket's context (Customer>Contract>Service>Ticket Process), plus the Ticket's category and sub categories
When, how and who created the Ticket
If this Ticket was created from another work item, the initial request date shows the start date of the original request, allowing you to capture the entire length of time it has taken to complete a request.
Keep with me - users who have this option selected will be auto assigned as the work item's owner or assignee. This can still be changed manually.
Send Automated Emails - the option to send out automated emails e.g. Ticket acknowledgement emails to the Ticket's contacts.
Depending on if record count has been configured to be visible on a Ticket, users will also be able to see and interact with the record count on the Ticket Settings card.
The Contacts Card is where you can specify the people who relate to the Ticket.
By default, the available relationships are:
Primary Contact – the main person you are dealing with for this Ticket. This is mandatory for Tickets.
Requester – the person that raised the initial request. This is mandatory for Tickets.
Subject – who the Ticket is about (this may be neither of the above).
Very often all three will be the same person.
CCs – any further contacts which can be copied on any correspondence. When a contact is tagged only as ‘CC’, it will be displayed in the separate CCs section (hidden until any CC-only contacts exist on the work item.
Note: it is possible to add further relationship types into the system. See here for more information on how to add contact tags.
Auto-populating a Ticket's contacts
When an email arrives from an address which is associated with a system user or an external contact which has been previously recorded in the system, then their details are automatically populated on the contacts tab when the Ticket is created by the system. They will automatically be tagged as the Requester, Subject and Primary Contact. These tags can be removed.
Optionally the first operator to assess the Ticket can also set them as the Primary Contact if deemed appropriated by their assessment. If you tag another contact as any of these relationship types, the tag will be removed from the previous contact.
Manually Populating a Ticket's Contact's
A Ticket's contacts will usually be auto-populated from an initial email. However, if the Ticket's contacts are not auto-populated or if you want to add a different contact to the Ticket, you can add contacts to the Ticket manually by searching for them in the Contacts Card.
If you search for a user in the Contacts Card that does not exist in the system, you can create a new contact by clicking on the ‘Create Contact’ option and filling in the contact's details.
If you have written the email address for the contact, the system will decode and auto-populate the first name and last name of the contact. Once you fill in all the information and click on create contact, the system will redirect you back to the work item.
When you manually add a contact they will be set as the Primary Contact, Requester and Subject by default. You can manually reassign these tags to other users afterwards.
To help you manage activity against your SLAs, Enate allows users to track the time it takes for work items to be completed, both as an overall total and broken out by the various resources who may have worked on it.
The Time Tracker Card in work items tracks the time of each individual browser session that the item is worked on.
See here for more information about time tracking:
Additionally, a Custom Card can be configured to display custom data.
See here for more information:
When you're working on a Ticket, Action or Case, operational issues can occur which have an effect on how you're able to deliver the process. It is important to record these as a way to highlight them for others who may view or work on the item, and to help with longer term efforts to improve process delivery.
Watch this video to find out more about recording defects in Enate.
You can also go to the dedicated article to find out more:
If during processing of a Ticket query it becomes apparent that the request is better handled via a specific Case, you can support this by choosing to convert the Ticket into a Case. You can do this via the ‘Convert to Case’ option from the Ticket screen.
See here for more information:
If an incoming email creates a new Ticket instead of auto-appending itself to an already existing request, you can merge the Ticket into the other work item. You do this by selecting the 'Merge' option from the Ticket screen.
See here for more information:
If a Ticket contains multiple separate queries / questions which are better managed separately you can split the Ticket. You do this by clicking on the Split option from the Ticket screen.
See here for more information:
When a new email or Self Service message has come in for a Ticket that hasn't been read yet, the New Information icon will be highlighted. Clicking on it shows you when the new information was received.
You can choose to mark the new information as read which will set the New Information icon back to normal. You can also mark the information as unread by clicking on the 'Mark as New' option.
This provides a link to the Standard Operating Procedure for the work item that has been set in Builder.
If the ‘Allow Feedback’ setting is ticked in Builder (see here for more information on how to do this), the Customer Feedback icon will appear in the Ticket's Header Ribbon.
It will show you your current feedback rating as well as recent customer feedback. See here for more information about getting Customer Feedback.
The files tab shows all of the files and links that have been added to that work item and its related work items, plus attachments for incoming and outgoing emails.
Any files/links for the current work item which is open are displayed at the top of the files tab, and any for its related work items are shown in a separated section below this. Items are sorted by the date/time they were uploaded with the most recent at the top.
You can see the name of the file, what type of file it is, its size, who uploaded it (and when), plus the reference number and of the work item it was uploaded to. You can also see the tags and notes that have been added to the files.
Various icons help you to identify further information:
All files in the files tab are available to add as attachments to any outgoing emails and links are available to add to the email body.
Please note that when upgrading from versions older than 2022.3, the files attached directly to a work item will all show in the 'Other work items' section without a reference number. Email attachments for this work item's emails will show in the 'Current' section however.
If the work item is assigned to you, you can add files and links to a work item in the Files tab. Multiple files can be uploaded at one time. Click the upload links at the top of the tab to upload.
You can also drag and drop files into the files tab to upload them.
Note: The maximum size per file is 100.00 MB.
By default, all types of files can be uploaded, however filetypes can be restricted by specifying acceptable types in the general settings section of Builder.
Tags can be added to files and links. Tagging is very helpful to add more structure to your files information, and opens up features such as auto-attaching files with certain tags to emails being auto-sent by the system, and to canned responses in mails you're composing. They also allow external automation routines to know which specific files to pick up from a work item.
Tagging files is also an important feature for processes which involve automation technology. Example: if a downstream automated Action needs to know which of the files you’ve attached to your Case is the ‘Invoice Confirmation’ file, you can tag the relevant files as such and, no matter the file name, the automation technology would know to select that file based on its tag. Such external automation technology can equally well supply tags as part of uploading documents into Work Items in Enate for further downstream manual / automated use.
The tag titles available to you are set in Builder. If you're regularly finding that a specific tag is not available to select, make sure to speak to your admin team about getting it added.
You can add a tag to a file by clicking on the '+' icon and then selecting a tag from the resulting list.
You can also add tags to multiple files and links at once by selecting one or more items and using the icon which are then displayed in the Files tab header.
Enate can also help with automated tagging of email attachments. Various options are available in the Marketplace section of Enate Builder to enable components (from Enate as well as third party ones) which analyse incoming mail content, including being able to suggest tags for email attachments based on their contents.
If your admin has switched on an auto-tagging component, you'll see some extra bits of info in the file tag section, where automated suggestions of tag values for an attachment have been made.
If the technology you're using is confident enough about its tagging suggestion, the tag will appear in green. If you agree with the suggestion, you don't need to do anything, but if disagree with it, you can simply click to change it.
And if the technology was less confident in its tag suggestion, the tag will be highlighted in orange. If you agree with the suggested tag, make sure to confirm it, otherwise change it to your preference. Every time you do this, the technology will learn and get a little bit better at suggesting tags. If you notice that the technology is regularly getting its suggestions wrong, speak to your admin team about modifying the confidence threshold.
Once tags have been added, the files/links will become available for auto-adding to emails with matching tags, allowing you to ensure that all documents of a relevant type are included with specific emails / email body content.
When a canned response text is inserted into a manual email or when a new email is auto-created and sent in-process, the system will identify any tags linked to the canned text / email template and will then auto-attach all of that work item’s files which share the same tag. Tags are linked to the canned response / email content as part of system configuration by administrator users in Builder when creating email templates.
Note: If file tags are not configured in your system then this ‘add file tag’ option will not be displayed.
You can also add notes to files and links to provide a brief description of the content or to provide any other information that might be useful.
You can also add notes to multiple files and links at once by selecting one or more items and using the icon which are then displayed in the Files tab header.
The menu on the right lets you preview an individual file. The preview will open in a new tab.
If the file is not previewable, a confirmation banner will pop up to explain this, and to offer an option to download the file. The file types supported for preview are as follows: txt, pdf, jpg, jpeg, jpe, jif, jfif, jfi, png, gif, web, tiff, tif, heif,heic, svg, svgz.
You can download individual files by clicking on the option in the menu on the right.
You can download multiple files at once by selecting the files you wish to download and selecting the option at the top of the screen. These can be downloaded as multiple individual files or as a single compressed ZIP file via the ZIP download option here.
You can delete files or links individually by clicking on the menu on the right.
You can also delete multiple files/links by selecting the files/links you wish to remove and selecting the delete option at the top of the screen.
You can filter the files and links being displayed in the files tab by using the filter option at the top. You can filter by: Attachments, Outgoing Email Attachments, Incoming Email Attachments and Links.
There's also a freetext search available to help you locate individual files or links. You can search based on the various text groups on display - Filename, Tag info and Notes texts.
If a Ticket contains multiple separate queries / questions which are better managed separately you can split the Ticket. Click on the Split tab in the Activities tabs to start the split:
The screen will default split into two Tickets. You can manually add more splits if you wish by clicking on the '+' icon. The Title, Description and Context (Customer >> Ticket Category etc.) are copied from the current Ticket, but all can be modified. You can choose to keep each separate Ticket with you.
Confirm the Ticket split by clicking the button in the Info card:
After splitting, the original Ticket will be set to ‘Wait– split Ticket’ with links to the new Tickets the original was split into.
Once the split Tickets are resolved and the feedback window if they have one has expired, this original Ticket will be set to fully complete.
For SLA purposes the start date of the original Ticket is copied to each of the Resulting Tickets and the time when the original Ticket has been marked as Resolved is calculated as the time when the last Ticket it has been split into gets resolved.
For example, if Ticket A has been split into Tickets B and C, and Ticket B is resolved at '2022-02-02 01:10:00' and Ticket C is resolved at '2022-02-03 02:00:00', the time marked for when Ticket A is Resolved will be '2022-02-03 02:00:00'.
You can cancel the splitting of a Ticket at any time by navigating away from the Split tab (the main Action button on the Ticket changes away from ‘Split’, so you can be sure you’re not splitting it).
The 'Merge' functionality in Enate lets you merge existing work items together so that queries which arrived separately - but should in fact be processed together - can be processed as one work item.
This is useful when, for example, an incoming email relating to an existing request inadvertently creates a new Ticket instead of auto-appending itself to an already existing request. This can sometimes happen if the incoming email isn't a direct reply to a previously sent Enate email or if the reference number of the initial Ticket isn't part of the email.
Watch this video to find out more about how to use the merge feature or continue reading below.
There are two ways you can merge Tickets in Enate:
To merge a Ticket into another work item, click on the 'merge' tab and select the option to close 'This work item'. Then from the accompanying search field select the work item you want to merge the Ticket into from the Search bar. You can search by title, reference number or the name of the customer, contract or service that the work item belongs to.
Please note: when choosing to close THIS Ticket and merge other work items into it, select a Ticket, Case or Action to merge the Ticket into, but note that the work item selected must be running. Additionally, if your search returns more than 50 results, only the most relevant top 50 will be displayed. If your desired work item does not appear in the top 50 results, add more search criteria to narrow down the results.
Select the Merge button from the Info card to confirm.
The Ticket tab will close and be marked as 'Closed' with a resolution method of 'Merged'.
If you click view this ‘closed’ Ticket again, you will see its status, who it was resolved by, when it was resolved and its resolution method (i.e. 'Merged'). Additionally, the Info card will display a link to the work item it was merged into.
Communications from the now closed Ticket will now display in the timeline of the remaining work item, marked with a green dot to show they are new to this work item and the reference number of the Ticket they originate from. The markers will clear when a user sets the new information icon as read.
To keep this Ticket open and merge other existing Tickets into it, click on the 'merge' tab and select the option to close ‘Other work Items’. Then select for the desired Ticket(s) to merge the Ticket into from the Search bar. You can search by title, reference number or the name of the customer, contract or service that the work item belongs to.
Please note: when choosing to close OTHER work items, you can only select Tickets, but you can select multiple Tickets at one time. If your search returns more than 50 results, only the most relevant top 50 will be displayed. If your desired work item does not appear in the top 50 results, add more search criteria to narrow down the results.
Select the Merge button from the Info card to confirm.
The other Ticket(s) will be set to ‘Closed' with a Resolution method of 'Merged' and a link to the Ticket they were merged into. If you click view the ‘closed’ Ticket(s), you will see its status, who it was resolved by, when it was resolved and its resolution method (i.e. 'Merged'). Additionally, the Info card will display a link to the work item it was merged into.
Communications from the now closed Ticket will now display in the timeline of the remaining Ticket, marked with a green dot to show they are new to this work item and the reference number of the Ticket they originate from. The markers will clear when a user sets the new information icon as read.
When merging a Ticket or Tickets into another work item, the Due Date of that remaining work item is the single relevant Due Date for any ongoing work. It is not recalculated as part of the merging, and similarly the due dates of any of the previously running work items (now set to Closed) are not recalculated before their status is set to Closed. Examples:
If an overdue ticket is merged into an on-time work item, the Due Date of the remaining work item stays unaffected - it is not classed as now being Overdue.
If an on-time ticket is merged into an overdue work item, the Due Date of the remaining work item stays unaffected - it is not classed as now being 'on time'.
To help you manage activity against your SLAs, Enate allows users to track the time it takes for work items to be completed, both as an overall total and broken out by the various resources who may have worked on it.
The time tracker records the time of each individual browser session that the item is worked on; time is tracked whenever a work item is open on-screen, regardless of whether it is assigned to the user or not and regardless of what state the work item is in. The time tracker runs for one single work item at a time within a browser session and will run for a work item tab when it gets browser tab focus. It continues to run even if the browser is minimized, if the computer is in lock screen etc.
In the scenario where work item A is open (with the timer running) and a further work item B tab gets opened, the timer will stop on item A and switch instead to item B. Flipping between these work item tabs would equally switch which one the time tracker is running for.
Time tracking halts when the work item tab is closed and in the event of a browser/machine timing out.
See here for more details about when time is tracked or not tracked in the Time Tracker card.
Clicking directly on an email in any of the Email View tabs will start the time tracker running for that work item and would stop a time tracker running for any other work item tab it had been running on immediately prior to this.
The card displays the length of time of the current session, a combined total of the length of time of all previous sessions, the expected initial estimated effort time and - for Actions and Tickets - the estimated effort time which the service agent can alter, which is useful for Forecasting.
Note: You are able to pause and reset the time being recorded for the current session, regardless of whether or not you are the work item's assignee.
Additionally you can edit the time of the current and your previous recorded sessions, regardless of whether or not you are the work item's assignee. However please note that only Team Leaders are able to edit the time recorded by other members of their team, whereas Team Members are only able to edit the time recorded for their own sessions.
Expanding the Time Tracker card displays the recorded time for previous sessions, as well as who was working on the work item during that session, how long the session lasted and if the session's recorded time has been edited.
Clicking on the information icon lets you see the date and time when the session was recorded and, if the work item is a Ticket, which category it was assigned to during that session.
You can edit the time of the current and previous recorded sessions, regardless of whether or not you are the work item's assignee. However please note that only Team Leaders are able to edit the time recorded by other members of their team, whereas Team Members are only able to edit the time recorded for their own sessions.
Manually editing the current time-on-task will save that edited time as a new row in the history.
You will be able to see further information including when an edit was made and who by when you open the card in full-screen mode.
Note that time tracker values for work performed by robots are read-only.
You can click the expand icon to open the card in full-screen mode. Here you can see the length of time of the current session, a combined total of the length of time of all previous sessions, and, for Actions and Tickets, the expected time required to complete the work item. You will also be able to see more detailed information about the individual session, as well as information about edits made to the recorded time:
User
Who was working on the work item
Time
The start and end time and total length of time of the recorded session
Date
The date when the session was recorded
Time Edited By
Who last edited the session's recorded time
Time Edited To
What the session's recorded time has been edited to
Date Edited
The date when the session's recorded time was edited
Ticket Category (Ticket Only)
The category that the Ticket was in when the time was edited
The expected time required to complete the work item can be configured in Builder for Cases, Actions and Tickets. Note that this information will only display if:
An Initial Estimated Effort value has been entered for this Case, Action or the selected Ticket Category in Builder.
The system-wide settings 'Show Time Tracker' and 'Display Expected Time in Time Tracker' are enabled.
If you only have one work item open in Enate and are currently working on a different business application, as long as you return to that tab before your Enate session expires your time will be tracked accurately.
If you have multiple work items open in Enate and are currently working on a different business application, as long as you return to the most recently accessed tab before your Enate session expires your time will be tracked accurately. The other work items that were open but not accessed mostly recently will not have their times tracked.
In order to keep time tracking of your activities as accurate as possible, here are a few help 'Do's and Don'ts' that will optimise how the system can help while running in a web browser.
Remember that you might have one single Enate Work item tab open, or perhaps multiple work items open in tabs in your browser.
Always open the work item you want to track time against as the LAST activity in Enate before switching to another business application to work on your task.
Make sure to return to the Enate application at the point where you finish your task.
If your activity is taking an extended period of time to complete, it's a good idea to come back to Enate from time to time, since your session may otherwise time out due to your browser timeout*.
*Session timeout periods for browsers could be typically from 20 mins to several hours. If you're finding that that things are timing out like this, speak with your IT admin about how that settings can be extended to help avoid this.
Failing to return to Enate after finishing your work.
Returning to Enate too late, i.e. after a session timeout due to inactivity.
Logging in on a different device or browser rather than going back to the same tab you left.
Just clicking the 'X' on the Enate tab without having reopened it (i.e. without having clicked to display the tab content).
Restarting the browser before returning to the Enate tab.
Closing the entire browser.
Restarting your system.
Time is tracked whenever a user has the Enate work item tab open either displayed or not displayed on screen. Time will not be tracked when the Time Tracker Card has been paused. You can find more detailed information about whether time is tracked or not in a particular scenario from the table below.
One Enate work item tab open
Users performs work away from Enate, then returns to Enate before the session timeout
Time is tracked on the work item accurately. Most correct user behaviour.
Multiple work item tabs open
Users performs work away from Enate, then return to last focused tab before session timeout
Time is tracked on the most recently focused work item tab. Most correct user behaviour.
Multiple work item tabs open
Users performs work away from Enate, then returns to a different tab, not the last focused tab, before session timeout
Enate records time spent on the business application to the last focused tab, but subsequent time is added to the currently focused tab.
Multiple work item tabs open
Users performs work away from Enate, then clicks to switch the display of currently focussed work item tab to instead show Enate Home page
Enate stops recording time on that work item tab, and does not start automatically recording anything until another work item tab is clicked onto.
Non-work item tab opened, no work item tabs
Users performs work away from Enate, then returns to Enate before the session timeout
Time is not recorded as no work item tab was open. not ideal user behaviour from the time tracker feature pov.
Non-work item tab opened, one work item tab open
Users performs work away from Enate, then returns to Enate before the session timeout
Time is recorded accurately on the work item tab if the user visited/opened it.
Work item tab open
Users performs work away from Enate, then Enate Tab gets closed without reopening
Enate may not record this accurately.
One or more Enate work item tabs open, browser minimized
Users performs work away from Enate, then returns to Enate before the session timeout
Time is tracked on the most recently focused work item tab.
One or more Enate work item tabs open
Users performs work away from Enate, User session times out (e.g., due to inactivity, browser closed, login in different device/browser)
Enate may not record this accurately.
One or more Enate work item tabs open
User navigates to Enate website and logs out successfully.
Enate accurately records time on the last focused tab.
One or more Enate work item tabs open
Internet connection lost, but then restored and user returns to Enate before session timeout.
Enate accurately record time on the last focused tab.
One or more Enate work item tabs open
System crash or unexpected shutdown. User restarts the system and returns to Enate
Time tracking may be incomplete or inaccurate due to the unexpected interruption.
Work item tab open
Users presses F5 / reloads the Enate tab
Time is recorded accurately on the work item tab.
Work item tab open
Computer is put to sleep and then resumed within User session timeout values (i.e. user wouldn't be re-asked to sign into Enate).
Time tracking will include the time the computer was asleep
Work item tab open
Computer is put to sleep and then resumed but after the user session has timed out.
Enate may not record this accurately.
The Enate system will always keep a record of the automatically recorded time (i.e. not manually edited). This is a record of the amount of time which the work item tab was displayed directly on screen. This data is not displayed to you but can be accessed for MI / reporting purposes. Please note that the time tracker tracks ALL accessing of the work item, even after it is completed.
Manually editing the current time-on-task will save that edited time as a new row in the history. The ‘time on task’ box will subsequently display the auto-running count of the time since you started the manual edit of the previously displayed value.
If during the processing of a Ticket query it becomes apparent to you that the request is best handled as a Case, you may choose to convert the Ticket to a Case.'
To convert a Ticket into a Case, expand the settings card of a Ticket, select 'Convert to Case' and then select the Case process you want to convert the Ticket into.
The system will then bring up any relevant custom cards for that Case - just fill in any required data and then click on 'Start Case' in the info card.
If your system has be configured to allow you to override the due date upon Case creation, you can select a new due date here.
If your system has been configured to set a schedule for a new Case upon creation in work manager, you can select a schedule here.
You can choose to keep each separate Ticket with you by selecting 'Keep with me' in the settings card and you can choose to send an email to the primary contact for the Ticket informing them that the Ticket has been turned into a Case by selecting the 'Send Automated Emails' option.
Confirm the Ticket promotion up to a Case by clicking the button in the Info card:
You will see a confirmation messages informing you that the Ticket will be closed and replaced by a Case (with the same reference number, but a ‘-C’ ending).
The original Ticket does not form any further part of service delivery and will now be in a state of Waiting with a Resolution Method of 'Case Launched' with a link to that Case.
The original Ticket will move to a state of Closed when the Case that has been launched is Closed.
The new Case launched will be in a state of To Do.
When manually starting a Ticket directly in Enate it will sit in a state of 'Draft' until it has been submitted for the first time.
To submit a Ticket, you must:
Add a Title
Enter a Ticket description in the section provided (after submitting, this section will disappear and instead will show as the initial submission note).
Set a Ticket Category in the Settings Tab - see here for more information
Set a Primary Contact and a Requester in the Contacts section.
Note: For manually created Tickets which have yet to have a title and description entered for them, if you send out an email prior to initial submitting (and saving) of the Ticket, the system will auto-populate the Ticket title and description from the email subject and description respectively. Upon sending an email, the email’s subject and body are copied into the Ticket’s title and description.
Then hit the ‘Submit’ button.
Once you have successfully submitted the Ticket, the Ticket will close and a confirmation pop-up will display showing that the Ticket has been submitted successfully and is now in a state of To Do.
You can click the Ticket reference link on this message to immediately re-open the Ticket (note that the Ticket may still be processing if you re-open the tab immediately). Alternatively, you can re-open using the ‘Recently Accessed’ link at the foot of the navigation dropdown.
When you see a Ticket in a state of To Do, it means that it is not currently being progressed.
The Ticket will sit in a status of To Do until a resource has picked it up - this could be a human resource or a robot resource.
Once you start updating a Ticket in a state of To Do, it will:
automatically assign to you and
the status will change to ‘In progress’
You can also choose to change the state yourself.
When a Ticket is in a state of In Progress, this signifies that work is now underway. It will stay in that status until it’s resolved (unless it needs to be moved to a state of Wait).
You can change the category of the Ticket after it has been initially categorised and an entry will appear in the timeline showing who changed the Ticket category, when they changed it and what it has been changed to.
Note that you will need to have selected the 'Ticket Category Changed' option from the timeline filter for this to show.
If you’ve picked up a Ticket in error, or if your reach the conclusion that it’s not a piece of work you’re going to be able to progress, you can unassign it from yourself, either to another resource or just back to its Queue. This could be after 10 seconds or half an hour, but when you do this the system will automatically set the status back to ‘To Do’ to let everyone know that it’s not going to be progressed until another resource picks it up. You can also just manually set the status back to ‘To Do’ if for example you started working on it in error and need to quickly undo the status change.
Similarly, if a robot resource rejects a piece of work, its status will be set back to ‘To Do’ as part of handing it over for a human resource to carry out.
If you’re working on a Ticket and you have to temporarily halt work on it because you’re waiting for some additional information or because of some other temporary blocker, you should choose the ‘Wait’ status.
When placing a Ticket into a state of 'Wait', you need to specify the type of wait. The options are:
Impact on SLA clock: SLA clock PAUSES while a Ticket is in this state, IF the Ticket's Due Date rule (configured during process design) has 'Add Wait Time To Due Date' set to ON. If it is set to OFF, the SLA clock CONTINUES while the Ticket is in this state.
If you’re working on a Ticket and you have to temporarily halt work on it because you’re waiting for some for some information from a third party or client, you should choose 'Wait for more information' and then add the number of days you want to wait for a response.
Upon confirming the 'Wait for more information' status, the Ticket will move from your Work Inbox into your Owned Work list, as there is no active work to be carried out on it until a response is received.
Once a response has been received, the Ticket will move back from your Owned Work list into your Work Inbox in a state of To Do, highlighted for you to progress.
Alternatively, if you have set the ‘Close if no response received’ to On, then upon reaching the number of days to wait if there has been no response received from the client, the Ticket will automatically close.
Impact on SLA clock: SLA clock CONTINUES while Ticket is in this state.
If you’re working on a Ticket and you have to temporarily halt work on it until a specific future date/time, you should choose 'Wait Until'.
When you select 'Wait Until', you must specify the desired follow up date and time.
Upon confirming the 'Wait Until' status, the Ticket will move from your Work Inbox into your Owned Work list, as there is no active work to be carried out on it until the follow up date.
When this date is reached, the Ticket will move back from your Owned Work list into your Work Inbox in a state of To Do, highlighted for you to progress.
Re-select this option if you wish to take the Ticket off 'Wait'.
You signify completing a Ticket by marking it as Resolved.
In addition to marking the Ticket as resolved you can specify the 'Resolution Method', with the following options:
With Customer Response
No customer response
Rejected
Rejected as Spam
The Ticket will then move to a state of Closed, unless a feedback window has been set for it, in which case it will move to a state of Resolved. See below for more information on this.
When you select to resolve a Ticket, if it has been configured this way in your system (see here for more information), you must either:
Send a resolution email
or
Add an internal resolution note
If you mark the Ticket as resolved and have not done either of these, the system will bring up a reminder message:
If you then choose to send a resolution email, the system will show this with a green tick in the email or note:
You will then be able to mark the Ticket as resolved.
If you have already added a resolution
If you have just added a note or sent an email before marking as ‘resolved’, the system will automatically mark this accordingly, and will not ask you to add a further resolution confirmation.
Subsequent Resolution Note / Email display in timeline.
For resolved Tickets, you will be able to see the note / email which was tagged as the resolution highlighted in green with tick marker:
Quick Resolution
For quick resolution, you can also send your resolving email and mark the Ticket as resolved in a single click. Just click the ‘Send and Resolve’ button at the foot of the email you are sending.
Note, this option is not available if you are sending an email from the pop-out screen. You need to come back to the main Ticket browser screen to confirm resolution of the Ticket.
After a Ticket has been resolved it may sit in that status for a brief period if a Feedback Window has been set for it - during this time period the service recipient may respond and the Ticket may be reopened, either manually using the 'Reopen' button or automatically upon receipt of a new incoming email or feedback within the time period.
Please note that when work items are reopened, the data stored for who resolved it and when it was resolved are persisted, and are not overwritten when the item is resolved for a second time.
After the feedback window has completed without any further response, the Ticket will move to a state of fully 'Closed'. Any subsequent mails received will launch a brand new work item.
Note: You can easily move an item from draft straight through to resolved - a good example of this is a ticket query which gets resolved on first contact.
A Sub Case will behave according to its own specific configuration, but its “parent” Case will not complete until all of its Sub Cases have completed.
You can therefore only create a Sub Case from an existing Case.
To create a new Sub Case, click the ‘+ Work item’ link shown near the tabs section of a Case and the choose the 'Sub Case' option from the dropdown.
In the resulting pop up, you can filter to search for the new type of Sub Case process you want to create in two ways:
by searching by email route - you can specify the mailbox address which people would normally send emails into to create work items. Often an email mailbox represent a certain part of the business within which you want to create your new work item. As a useful shortcut we've added a feature here where you can search by mailbox and narrow down straight away the Sub Case processes that you can choose from. Selecting a mailbox will filter the dropdown options to only the processes linked to that mailbox.
by selecting a Customer, Contract, Service and a Sub Case process to launch (these will default in values if there is only one option to choose). Note that the Customer for a Sub Case will will be auto-filled as the same as its parent Case i.e. the Case you are creating it from.
Please note that the Sub Cases available for you to launch will depend on the permissions settings in Builder. Additionally, you will also only be able to select a Sub Case process from an email route that has been enabled in Builder (see here for more information). You will also only be able to select a Sub Case process in Test Mode if the email route for that Sub Case process has been configured to run in Test Mode.
You can then adjust the following settings for the Sub Case:
Override Due Date
Description
You can modify the description of the new Sub Case you are creatin
Schedule
Adding Contacts
You can add multiple different contacts for the new Sub Case and divide the tags between them as you need.
Please note that Defects, Files, Links & Custom Data will be automatically shared will be automatically shared from the parent Case to your new Sub Case. Communications from the parent Case, and its related work items, so its Action and Sub Cases (if it has any) will also be shared with the new Sub Case. However please note that emails will not be shared but you can easily see them by selecting the 'Include related work items' option in the timeline. Also note that making updates to the Defects, Files, Links, Custom Data or Communications in the new Sub Case WILL update update them in the parent Case too.
A link to the new Sub Case will appear in the Sub Cases tab and NOT in the Links tab.
The Sub Cases tab will show the following information for any Sub Cases under a Case:
Current State icon
Sub Case reference number and Case title
Action Count – The count of Actions associated with this Sub-Case
Owner– the Case owner(If defined)
Queue – the Cases Queue (If defined)
Due Date – The Case due date
Icon to expand the Sub Case to reveal its Actions
Reference numbers of Sub Cases can be broken down as follows:
Most often the Actions in a Case are started automatically (either by process flow or based on schedules). However, if an Action has been configured to be manually startable, you can do this from the Case.
Select the ‘Start Action’ tab in the Activities section. In the resulting panel, choose the Action type to launch (must have been configured as manually startable in Builder), set a due date and specify how many of the Action you wish to launch. Specify the Action instructions if you wish these to be different from the default instructions displayed.
Hit ‘Start Action’ to confirm. You can refresh the screen display to see the newly created Action:
Note:
You do not need to have the Case assigned to you in order to launch a new Action.
This option is also available from any of the Actions within the Case.
The tab will not close upon launching the new Action, as this is an additive activity which does not modify the current Case.
The Action screen has the same overall layout as the and screen, and the same basic features including to a work item, , viewing the and viewing the , but the Action screen also contains some Action-specific features.
At the top of the Action screen, you'll see the title of the Action, made up of:
Customer name - Contract name - Service name - Case Process name - Action Process name
For example:
The title of an Action is automatically set and is not editable.
'Action Reference - Case Short Description - Action Process Name' '10040-C-A1.1 - Jack Jones new starter - HR Approval'
Note that the Case Short Description cannot be edited directly from an Action.
This is the name that will be shown in the Action tab:
The Case's short description is also the title that will also appear in the 'Title' column of the homepage grid for the Action.
You can copy the Action's reference and number by clicking on the copy icon in the tab:
The Action's due date will display, colour-coded to show if the date is:
On schedule:
Due today:
Late:
If an Action has been configured with an override due date option in Builder, then you will be able to override the due date of an Action by clicking on the due date in the header and changing the date in the popup.
You can also see whether or not the Action has been assigned, and who to.
You are able to reassign and unassign an Action, or assign the Action to yourself if it has not been assigned to you already.
See here for more information about assigning work in Enate:
In the Info Card you can see the status of the Action and change the status as needed.
The main label on the left side of the Info card will display the status the Action is currently in. The dropdown button on the right side gives options for the states which you can move it into as part of processing.
See here for more information about processing an Action:
Once you have selected the new status from the dropdown and filled in any further required information, click the button to confirm.
The border of the Info Card highlights in a colour relating to the current status – once you have clicked the button to change status, the system will process the changes – the border colour and new status will change to confirm that the status update has occurred.
When changing the status of a work item, if you are moving it to a state of 'In Progress', the work item tab will remain open upon confirming the new status. When changing to any other status, e.g. 'Wait' or 'Rejected', the tab will automatically close. A label under the Status will inform you of this in advance.
In addition to showing the Action's status, the following information is displayed directly underneath:
Set by - who set the status
Reason - the status change reason - i.e. why was it changed, this could be manual or as part of a process)
Date - when the status was changed
Last Updated By - who last changed some data on the Action
Last Updated On - when some data was last changed on the Action.
Note that not all of the above information will be displayed every time, the information that is shown depends on the status of the Action and how the Action has been configured in Builder.
The Settings Card shows you detailed information about the Action, including:
The Action's context (Customer>Contract>Service>Case Process). This cannot be modified.
Action Instructions
The Action's parent Case, a link to the parent Case and a symbol showing the state of the Case
When the Action was created and who by
If this Action was created from another work item, the initial request date shows the start date of the original request, allowing you to capture the entire length of time it has taken to complete a request.
Keep with me - users who have this option selected will be auto assigned as the work item's owner or assignee. This can still be changed manually.
Record Count - depending on configuration for the Action in Builder, the record count may or may not be displayed here. If it is, the record count is editable. If you update the record count for an Action, it will update the record count for future Actions but not previous Actions that have been closed.
By default, the available relationships are:
Primary Contact – the main person you are dealing with for this Action.
Requester – the person that raised the initial request.
Subject – who the Action is about (this may be neither of the above).
Very often all three will be the same person.
CCs – any further contacts which can be copied on any correspondence. When a contact is tagged only as ‘CC’, it will be displayed in the separate CCs section (hidden until any CC-only contacts exist on the work item.
If you search for a user in the contacts card that does not exist in the system, you can create a new contact by clicking on the ‘Create Contact’ option and filling in the contact's details.
If you have written the email address for the contact, the system will decode and auto-populate the first name and last name of the contact. Once you fill in all the information and click on create contact, the system will redirect you back to the work item.
When you manually add a contact they will be set as the Primary Contact, Requester and Subject by default. You can manually reassign these tags to other users afterwards.
To help you manage activity against your SLAs, Enate allows users to track the time it takes for work items to be completed, both as an overall total and broken out by the various resources who may have worked on it.
The Time Tracker Card in work items tracks the time of each individual browser session that the item is worked on.
See here for more information about time tracking:
Additionally, a Custom Card can be configured to display custom data..
See here for more information:
When you're working on a Ticket, Action or Case, operational issues can occur which have an effect on how you're able to deliver the process. It is important to record these as a way to highlight them for others who may view or work on the item, and to help with longer term efforts to improve process delivery.
Watch this video to find out more about recording defects in Enate.
You can also go to the dedicated article to find out more:
In order to mark an Action as complete, you must confirm for each item in the checklist whether you have completed it (the options are Yes, No, N/A) and you may need to add a note for each check.
You can also see the name of the person who last updated the item in the checklist and when this update was made.
If issues have occurred during the running of a Case you may wish to rework the Case. You can do this from an Action by selecting the ‘Rework’ tab from the Action screen.
See here to find out more about reworking a Case from an Action:
Most often the Actions in a Case are started automatically (either by process flow or based on schedules). However, if an Action has been configured to be manually startable, you can do this from an Action using the 'Start Action' feature.
See here to find out more about manually launching an Action from an Action:
When a new email has come in for the Action that hasn't been read yet, the New Information icon will be highlighted. Clicking on it shows you when the new email was received.
You can choose to mark the new information as read which will set the New Information icon back to normal. You can also mark the information as unread by clicking on the 'Mark as New' option.
You can view how the Case that the Action belongs to is progressing by clicking on the map icon. will bring up the Case progress popup. This displays the progress made on steps in the Case, showing completed steps in green, the current step in orange and future steps in grey.
If you do not want any percentages to show here, simply leave them blank when configuring the Case’s steps in Builder.
This provides a link to the Standard Operating Procedure for the work item that has been set in Builder.
The Case screen has the same overall layout as the and screen, and the same basic features including to a work item, , viewing the and viewing the , but the Case screen also contains some Case-specific features.
At the top of the Case screen, you'll see the context of the Case, made up of:
Customer name - Contract name - Service name - Case Process Name
For example:
This is the title that will then appear at the top of the Case's tab.
This is the title that will also appear in the 'Title' column of the homepage grid.
You can copy the Case's reference number and title by clicking on the copy icon in the tab:
The Case screen display is laid out to emphasise visibility of the Actions which are run for it. To support this, an additional dedicated 'Actions' tab exists which allows you to quickly see the status of its Actions and to access them. This is the default displayed tab in this section for Cases.
This tab shows the following information for any Actions under the Case:
Current State icon
Action reference number
Action title and instructions
Due Date, Assignee, Queue
State in text form
Actions will be displayed in order of:
Status, with Actions in a status of Draft at the top, followed by Actions in a status of To Do, then In Progress, then Waiting, then Resolved, then Closed. If all the statuses are the same, then the Actions will be displayed in order of:
Due date, with the Actions due soonest at the top. If all the due dates are the same, then the Actions will be displayed in order of:
Time remaining when paused, with the Action with the least amount of time remaining when paused at the top. If the time remaining when paused is the same for all the Actions, then the Actions will be displayed in order of:
Step number, with the Action with the lowest step number at the top. If the step numbers are all the same, then the Actions will be displayed in order of:
Start Date/Time, with the Action with the most recent start date/time at the top. If the start date/time is the same for all the Actions, then the Actions will be displayed in order of:
Reference number
Sub Cases are created from an existing 'parent' Case that retain a link to their 'parent' Case will behave according to its own specific configuration, but its parent Case will not complete until all of its Sub Cases have completed.
You can create Sub Cases by clicking on the ‘+ Work item’ link shown near the tabs section of a Case and the choose the 'Sub Case' option from the dropdown.
The Sub Cases tab will show the Sub Cases for that Case.
See here for more information about Sub Cases:
Another feature of the Case screen is the option to launch a Case or Ticket from the Case to create a 'Linked' relationship between the work items.
See here for more information:
The Case's due date will display, colour-coded to show if the date is:
On schedule:
Due today:
Late:
If a Case has been configured with an override due date option in Builder, then you will be able to override the due date of a Case by clicking on the due date in the header and changing the date in the popup.
You can also see whether or not the Case has been assigned, and who to.
You are able to reassign and unassign an Case, or assign the Case to yourself if it has not been assigned to you already.
See here for more information about assigning work in Enate:
In the Info Card you can see the status of the Case and change the status as needed.
The main label on the left side of the Info Card will display the status the Case is currently in. The dropdown button on the right side gives options for the states which you can move it into as part of processing.
See here for more information about processing a Case:
Once you have selected the new status from the dropdown and filled in any further required information, click the button to confirm.
The border of the Info Card highlights in a colour relating to the current status – once you have clicked the button to change status, the system will process the changes – the border colour and new status will change to confirm that the status update has occurred.
When changing the status of a work item, if you are moving it to a state of 'In Progress', the work item tab will remain open upon confirming the new status. When changing to any other status, e.g. 'Wait' or 'Rejected', the tab will automatically close. A label under the Status will inform you of this in advance.
In addition to showing the Case's status, the following information is displayed directly underneath:
Set by - who set the status
Reason - the status change reason - i.e. why was it changed, this could be manual or as part of a process)
Date - when the status was changed
Last Updated By - who last changed some data on the Ticket
Last Updated On - when some data was last changed on the Ticket
Note that not all of the above information will be displayed every time, the information that is shown depends on the status of the Ticket and how the Ticket has been configured in Builder.
The Settings Card shows you detailed information about the Case, including:
The context of the Case (Customer>Contract>Service>Case Process).
When, how and who created the Case
If this Case was created from another work item, the initial request date shows the start date of the original request, allowing you to capture the entire length of time it has taken to complete a request.
Keep with me - users who have this option selected will be auto assigned as the work item's owner or assignee. This can still be changed manually.
Keep Action with me - all future Actions within a Case will automatically be assigned to the user who has the "Keep Action with me" option selected.
Send Automated Emails - the option to send automated emails for the Case. At the moment, the only automated email available to send for cases is a Case creation acknowledgement email.
Record Count - depending on configuration for the Case in Builder, the record count may or may not be displayed here. If it is, the record count is editable.
By default, the available relationships are:
Primary Contact – the main person you are dealing with for this Case. This is may or may not be mandatory for Cases, depending upon Case configuration in Builder.
Requester – the person that raised the initial request. This is may or may not be mandatory for Cases, depending upon Case configuration in Builder.
Subject – who the Case is about.
Very often all three will be the same person.
CCs – any further contacts which can be copied on any correspondence. When a contact is tagged only as ‘CC’, it will be displayed in the separate CCs section (hidden until any CC-only contacts exist on the work item.
If you search for a user in the Contacts Card that does not exist in the system, you can create a new contact by clicking on the ‘Create Contact’ option and filling in the contact's details.
If you have written the email address for the contact, the system will decode and auto-populate the first name and last name of the contact. Once you fill in all the information and click on create contact, the system will redirect you back to the work item.
When you manually add a contact they will be set as the Primary Contact, Requester and Subject by default. You can manually reassign these tags to other users afterwards.
To help you manage activity against your SLAs, Enate allows users to track the time it takes for work items to be completed, both as an overall total and broken out by the various resources who may have worked on it.
The Time Tracker Card in work items tracks the time of each individual browser session that the item is worked on.
See here for more information about time tracking:
Additionally, a Custom Card can be configured to display custom data..
See here for more information:
When you're working on a Ticket, Action or Case, operational issues can occur which have an effect on how you're able to deliver the process. It is important to record these as a way to highlight them for others who may view or work on the item, and to help with longer term efforts to improve process delivery.
Watch this video to find out more about recording defects in Enate.
You can also go to the dedicated article to find out more:
If issues have occurred during the running of a Case you may wish to rework the Case. You can do this from the Case by selecting the ‘Rework’ tab from the Case screen.
See here to find out more about reworking a Case:
Most often the Actions in a Case are started automatically (either by process flow or based on schedules). However, if an Action has been configured to be manually startable, you can do this from the Case using the 'Start Action' feature.
See here to find out more about manually launching an Action from a Case:
When a new email has come in for a Case that hasn't been read yet, the New Information icon will be highlighted. Clicking on it shows you when the new email was received.
You can choose to mark the new information as read which will set the New Information icon back to normal. You can also mark the information as unread by clicking on the 'Mark as New' option.
This provides a link to the Standard Operating Procedure for the work item that has been set in Builder.
A ‘Wait for Sub-Cases to Complete’ Action will wait for a specific Sub-Case to reach completion before allowing the Case to move on to the next Action.
You can tell that an Action is a ‘Wait for Sub-Cases to Complete’ Action because it will say 'Action is waiting for Sub-Case to complete' in the Action's info card.
Once a ‘Wait for Sub-Cases to Complete’ Action has been launched AND the Sub-Case it has been set to wait for has been launched (either manually or through a 'Start Case' Action), the ‘Wait for Sub-Cases to Complete’ Action will move into a state of 'Waiting'.
Once the Sub-Case is completed, the 'Wait for Sub-Cases to Complete' Action will close automatically.
You will be notified of this in the timeline as well.
If the Sub-Case the 'Wait for Sub-Cases to Complete’ Action is set to wait for it not available - either because it has not been launched or because it was resolved before the ‘Wait for Sub-Cases to Complete’ Action was launched, the ‘Wait for Sub-Cases to Complete’ Action will enter a state of 'To Do' and be assigned to a Queue where a user will pick it up and decide how to proceed.
If you then try to set the 'Waiting for Sub-Case to Complete' Action to 'Waiting', the Action will close as the Sub-Case it is set to wait for hasn't been launched.
If the Action is not in a 'Wait for Sub-Cases to Complete' state and the Sub-Case for which it is waiting has been completed, a message will appear as 'Sub-Case is completed' in the Info Card.
If you manually Resolve a ‘Wait for Sub-Case to Complete’ Action, the Action will be marked as Resolved without the Sub-Case having completed.
Please note that if your system has been configured to auto-close a 'Wait for Sub-Case to complete' Action (see here for more information about how to do that) and the Sub Case the 'Wait for Sub-Cases to Complete’ Action is set to wait for is not available - either because it has not been launched or because it was resolved before the ‘Wait for Sub-Cases to Complete’ Action was launched, the ‘Wait for Sub-Cases to Complete’ Action will automatically move to a state of Closed. You will be notified of this in the timeline.
An Action in Enate will begin in a status of ‘To Do’ until a resource has picked it up - this could be a human resource or a robot resource.
Once you start updating an Action sitting in this state, it will:
automatically assign to you and
the status will change to ‘In progress’
You can also choose to change the state yourself. This signifies that work is now underway and it will stay in 'In Progress' until it’s resolved – assuming e.g. no waiting for further information.
If you’ve picked up an Action in error, or if your reach the conclusion that it’s not a piece of work you’re going to be able to progress you can unassign it from yourself, either to another resource or just back to its Queue. This could be after 10 seconds or half an hour, but when you do this the system will automatically set the status back to ‘To Do’ to let everyone know that it’s not going to be progressed until another resource picks it up. You can also just manually set the status back to ‘To Do’ if for example you started working on it in error and need to quickly undo the status change.
Similarly if a robot resource rejects a piece of work its status will be set back to ‘To Do’ as part of handing it over for a human resource to carry out.
If you’re working on an Action and you have to temporarily halt work on it because you’re waiting for some additional information or because of some other temporary blocker, you should choose the ‘Wait’ status.
When placing an Action into a state of 'Wait', you need to specify the type of wait. The options are:
If you’re working on an Action and you have to temporarily halt work on it because you’re waiting for some for some information from a third party or client, you should choose 'Wait for more information'.
Upon confirming the 'Wait for more information' status, the Action will move from your Work Inbox into your Owned Work list, as there is no active work to be carried out on it until a response is received.
Once a response has been received, the Action will move back from your Owned Work list into your Work Inbox in a state of To Do, highlighted for you to progress.
Impact on SLA clock: SLA clock CONTINUES while the Action is in this state.
If you’re working on an Action and you have to temporarily halt work on it until a specific future date/time, you should choose 'Wait Until'.
When you select 'Wait Until', you must specify the desired follow up date and time.
Upon confirming the 'Wait Until' status, the Action will move from your Work Inbox into your Owned Work list, as there is no active work to be carried out on it until the follow up date.
When this date is reached, the Action will move back from your Owned Work list into your Work Inbox in a state of To Do, highlighted for you to progress.
You signify completing the Action by marking it as Resolved.
Along with this there are two options to specify how the Action was resolved:
Complete
Unable to complete
Set this option if you cannot complete the required activity. Once you have confirmed this option, the Action will be closed and cannot be re-opened. The Case Owner will be notified of this and be asked to take the necessary steps to resolve at Case level. This may involve starting another copy of the Action, reworking the Case from a previous step, or moving on.
Enter the reason you are unable to complete the Action and hit the ‘can’t Complete’ button to confirm. The tab will close.
After the Action has been resolved, it will move to a state of 'Closed'.
Any subsequent mails received will launch a brand new work item. Once you have selected this, the Action will be closed and cannot be re-opened.
Note: You can easily move an item from 'To Do' straight through to resolved.
The Document Extraction component automatically extracts the relevant data from files attached to incoming emails so that this data can be used in further processing of the work item, saving your agents time and effort. This also means that documents such as PDFs can be scanned and used both to start Cases in Enate and to form part of the ongoing process's activities.
When a Document Extraction Action runs for a Case, documents attached to the Case can be submitted to your desired technology for scanning and the processed output files will be returned and automatically attached to the Case.
If at any point the technology you're using is not confident enough of the results, based on a confidence threshold that you can set, Enate will instantly transfer the work to an agent in Work Manager to look over and verify, giving you that 'human in the loop' support.
This component can be switched on by your admin in the section of Enate Builder.
Check out this video to find out more:
When the Case is run in Work Manager, relevant data from files attached to incoming emails for it will be automatically analyzed and extracted.
If the technology you're using is confident enough about its data extraction results, this Action won't even need to be seen by a human user, it will simply be completed automatically and the Case will move on to the next Action. The completed data extraction Action can still be viewed if you click on it, but it won't need to be handed over to a human user for involvement.
However, if the extraction technology is less confident in its data extraction results, the Action will be handed over to a human user when you next hit 'pull from Queue' in their home page, to pick up and look over. When an agent opens the Action, you'll see that it's been given to them because some further checks are required.
To do this, you just needs to click on 'Verify Now' and scroll to the 'validation station' screen in the Action, which shows the scanned document image and the resulting extracted table of data values. This lets you see where those lower confidence levels are highlighted, review them and make any necessary corrections manually. This can viewed in-situ, or expanded out to a popup to display full screen.
Every time this is done, the technology will learn and get a little bit better at its data extraction suggestions. If you notice that the technology is regularly getting its suggestions wrong, speak to your admin team about modifying the confidence threshold.
Once you are happy that the extracted data is as desired, you can click to mark the Action as completed successfully.
Enate is able to provide integration with - this is achieved through use of an ABBYY FlexiCapture integrated Action (see the for guidance on how to create and configure this new Action type).
When an ABBYY Action runs for a Case, documents attached to the Case can be submitted to ABBYY FlexiCapture for OCR Scanning and the processed output files will be returned and automatically attached to the Case.
Note: Only filetypes supported by ABBYY v12 onwards can be submitted. Click to see the following link for list of formats supported by ABBYY.
The system will show this message while it is waiting for you to submit document(s) to the ABBYY FlexiCapture engine for processing:
You’ll see confirmation of when documents have successfully been submitted to ABBYY for processing:
Last attempt is the time when the document(s) have been submitted to the ABBYY FlexiCapture engine for processing.
If the documents submitted were of an invalid file format or if there were problems with the formatting of the document itself, the system will return this message:
If there is still a problem with submission following the automatic retries (e.g. if the retry setting is set to 5 and the system fails to establish a connection following 5 automatic retries), the ABBYY Action will move to a state of 'Closed'.
In this circumstance of the Action failing to establish connection with the external sytem, this will escalate to the Case Owner, highlighting in the Action section of the Case screen that this Action was Closed - Not Done Successfully.
After having scanned a document, ABBYY creates a score based on how confident it is in the quality of the scan. If the confidence score is above the threshold defined then no verification is required and it will process the data and complete the task. If the confidence score is below a certain threshold, human verification is required.
A status message will confirm that human validation is not required:
Once processing is complete, the ABBYY Action will close. Exported files will be attached to the Case and are visible in the Files Card.
Note: if Output File Tags’ have been set then ABBYY will apply the output tag to all files which it processed, ready for use in downstream activities.
The system will alert you if human verification is required:
Additionally, a reminder text will display in next to the Action status to reaffirm that manual verification must be completed in ABBYY before continuing.
Clicking on the ‘Verify’ button will take you to the ABBYY Verification Station where you can verify the scans of the documents and adjust information as necessary.
Note : A valid ABBYY FlexiCapture account with permissions to carry out verification in the chosen project will be required for full access.
Once you are logged in, you will be presented with ABBY FlexiCapture’s Verification Station screen where you can review and adjust information as necessary.
The Verification Station is made up of three sections:
The individual pages of the document to be scanned.
A close up of the original document to be scanned.
The Extracted Output - so the scanned version of the original document.
Text highlighted in yellow in the original document tab is the data ABBYY is unable to read. This is highlighted in red in the Extracted Output.
Certain characters like ‘i’ may also been highlighted Extracted Output section if ABBYY is uncertain about the scanned copy.
Once you’ve finished the manual verification, the screen will confirm this has been done but will note that there was an expectation which required manual intervention:
You can then mark the Action as complete.
Note: if Output File Tags’ have been set then ABBYY will apply the output tag to all files which it processed, ready for use in downstream activities.
Enate allows a granular level of granting access to people based on their role and business requirements. These settings are defined in the User Management section of Builder.
Every user has a Work Manager role assigned to them. The role has a number of access options configured for it which determine what they can see and do in Enate.
Enate provides two standard, pre-configured roles for Work Manager:
Team Member - this is for Agent users who process Tickets, Actions & Cases and who report to a Team Leader. This role gives them access to work assigned to them, their team (people who report to the same Team Leader as they do) and work that is in the Queues that they work out of, but has fewer levels of access than the Team Leader role.
Team Leader - this is for senior members who manage a Team and oversee Queues. This role gives them access to set up and maintain their teams and Queues, to assign work to others, as well as to more advanced features such as creating customized reports.
This article provides a full breakdown of access options for Team Member and Team Leader roles.
If a standard role doesn't quite fit the bill, you can create custom roles that allow you to fine-tune levels of access to give users the exact combination of access levels they need.
Custom roles might be particularly useful in the following circumstances:
Senior Team Members - You may wish to create a custom role for your more senior team members which falls part-way between the standard 'Team Leader' and 'Team Member' roles, giving them access to some Team Leader-like features without needing to have them fulfil that role entirely.
Junior Team Members - You may wish to create a custom role for your more junior team members which gives them access to some 'Team Member'-like features while hiding other aspects of the system until they gain more experience
You can also give some Work Manager users access to Enate's Builder application, for example so that they can view local processes. You do this by assigning them a Builder role, .
Users are also able to view which roles their team members have in Work Manager - will bring up their user profile which includes information such as their role title, its description (if one has been added), as well as a list showing which features that the user has access to.
If you find yourself needing to change the levels of access for yourself or users in your team, speak to your system admin.
Work items are classified into their respective due states:
Green – on target, not yet overdue
Amber – due today (but not yet overdue)
Red – work items which are now overdue (including items where the due date is today, but the due time has now passed).
Grey – work items are classified into a state of 'Not Set' when the due date is not currently known. This can be in the following situations:
When the work item has just been started (manually) but has not yet been submitted
When the work item is in a state of ‘Wait for more Information’ AND is set to add the wait time on the due date
If you click on one of the due dates, the grid will be filtered down to work items with just that due date:
Bar Chart information is displayed in a Pareto format, i.e. with highest volumes shown first. A maximum of ten bars are displayed. The top nine groups are displayed uniquely, with all remaining items shown combined in the final bar.
The ‘Display By’ choice for the bar chart is also accessed via the grid settings link. This will bring up the 'Display and Column Settings’ popup. The ‘Display By’ options for the bar chart can be found at the top. You can select a standard a standard system information column to display the bar chart by.
The standard system information by which you can display the bar chart display is as follows:
Action Type – this shows the Action type, either as send email or as a manual Action.
Assigned To – this shows who the Action has been assigned to.
Contract Name – this shows the name of the contract.
Last Updated By – human/digital worker who last updated this item.
Last Updated On – datetime when this item was last updated by a human/digital worker. The datetime on which custom data field values are updated is stored in the Enate database and can be used for subsequent reporting.
Owned By – name of the user who currently has ultimate responsibility for the work item.
Parent Process Name – if this an Action, this shows the parent Case.
Process Name – the business process the work item is part of, e.g. ‘Maternity Request Process’.
Queue – the work Queue which Cases/Tickets/Actions get sent to based on their routing rule.
Service Line – the overall area of the business this work item runs under, e.g. ‘Payroll’.
Service Provider – the company delivering service for this work item, usually your company.
Started By – this shows who the Action was started by.
Started By Method – how the work began, e.g. incoming email, automatic schedule, manually, etc.
State – current state of the work item e.g. Running, Waiting for more Information, Resolved etc.
Work Item Type – i.e. Case, Action or Ticket.
If your system has been configured with them, you can also choose to select a custom data column to display the bar chart by.
Custom Data fields of the following types can be used to display information in the bar chart:
Short Text
List (simple list only)
Checkbox
Note: When you choose to display information in the bar chart by a certain item (standard system property or custom data field), that item will be added to the main grid display as an additional column.
You can return to the system defaults by selecting 'Revert to Defaults' in the 'Display and Column Settings’ popup.
Clicking on a bar name within the chart filters the grid to those results.
Clicking on a specific R/A/G section within an individual bar filters the grid results down to the items in that state.
Icons in the homepage grid let you know the state of the work item and give you high-level information about them.
These icons also appear when you search for a work item in Quickfind.
They denote the following information:
And they denote the following information about the status of the work item:
You are able to choose which work items you can see on the home page by selecting Work Inbox, Owned Work, Team Work Inbox, or Team Owned Work.
Generally, if a work item is assigned to you or one of your team members, or it's in a state of To Do or In Progress, you'll see it in the Inboxes. Everything else, such as items in a Wait state, you'll find in the Owned Work views. The sections below go into this in a bit more detail.
Note: The RAG volumes and bar charts are shown independently for each of these views, and so the displays of each will also change when you flip from one grid view to the other.
The Work Inbox view shows you which work items are currently assigned to you.
The Owned Work view displays work items for which you are the Owner, rather than the current assignee.
These are work items which may not necessarily be assigned to you (or anyone) right now, but for which you have longer-term responsibility for, e.g. Cases.
Long term responsibility refers to the person responsible for the entire Case journey. This includes its Actions, the status changes of the Cases and its Actions, as well as the delivery of the Case.
A Case can be owned by using Keep with me.
Please note:
Actions can only have an Owner if they are in a state of Pause e.g. states such as Wait for more information, Schedule for follow-up, etc.
There can be only one Owner of a Case at any one point
The Team Work Inbox view shows you all the work items which are assigned to you or one of your team members, or it's in a state of To Do or In Progress.
The Team Owned Work view shows you all work items that are owned by your Team i.e. Cases started by them, and Cases in states such as Wait for more information, Schedule for follow up, etc.
Note: If you are a Team Member who prefers a focused view of your Inbox and you do not want to see the Peers and Queue work, then please ask your manager to switch off these views for you. Your view after login will then only show items in your Inbox / Owned Work.
See the table below for a more detailed breakout of scenarios:
You can reorder the columns in the home page grid according to your preference. This column order will persist when doing multiple searches, as well as when you log out and log back in.
Column widths can be manually adjusted, and data can be sorted by a a particular column by clicking on the name in column header. Click it again to cycle though ascending, descending and no sort.
You can display additional columns in the grid by selecting them from the standard columns section in the left hand side of the 'Display and Column Settings’ popup. The mandatory columns are shown in grey.
The list of standard system attributes you can display as grid columns which are available in the home page grids include :
Action Type – this shows the Action type, either as a send email or as a manual Action-type.
Assigned To – this shows who the Action has been assigned to.
Contract Name – this shows the name of the contract.
Customer – this shows the name of the customer.
Due – this shows when the Action is due.
Has Been Reopened - this shows if a work item has been reopened or not.
Initial Request On - this shows the start date of the original request. This is particularly useful in situations where a further work item has been created from the original request (when a Sub Case is created, when a Ticket is converted into a Case, when a Case or Action gets reworked, when an Action is created via the 'Start Action' option or when a new linked work item is created), as it allows you to see the entire length of time it is taking to complete a request, as opposed to just the length of time an individual work item has been being worked on.
Is Overdue - this shows if a work item is overdue
Last Email Received - the date and time the last email of a work item was received
Last Email Sender - the details of the last person who sent an email relating to a work item. If the user is already in the system, this column will display their name, otherwise this column will display their email address.
Last Reopened By - if a work item has been reopened, this shows the person who last reopened the work item.
Last Reopened On - if a work item has been reopened, this shows the date when the work items was last reopened.
Last Updated By – human/digital worker who updated this item last time.
Last Updated On – datetime when this item was last updated by a human/digital worker. The datetime on which custom data field values are updated is stored in the Enate database and can be used for subsequent reporting.
Original Requester Email – the email address of the original requester of a work item, i.e. the person who initially raised the request.
Original Requester Name – the name of the original requester of a work item, i.e. the person who initially raised the request.
Owned By – name of the user who currently has ultimate responsibility for the work item.
Overdue By Days - this shows the number of days a work item is overdue by.
Parent Process Name – if this an Action, this shows the parent Case.
Parent Reference – reference number of the work item which started this one, e.g. parent Case.
Primary Contact Email - the email address of the primary contact of a work item
Primary Contact Name - the name of the primary contact of a work item
Process Name – the business process the work item is part of, e.g. ‘Maternity Request Process’.
Queue – the work Queue which Cases/Tickets/Actions get sent to based on their routing rule.
Reference – the unique reference number e.g. 101342-T.
Requester Email - the email address of the requester of a work item
Requester Name - the name of the requester of a work item
Resolution Method - this shows how a work item was Resolved e.g. if has been done successfully, if it was resolved by a Case being launched, if it was resolved by Tickets being merged etc.
Service Line – the overall area of the business this work item runs under, e.g. ‘Payroll’.
Service Name – the service instance the work item runs under, e.g. ACME French Payroll.
Service Provider – the company delivering service for this work item, usually your company.
Started – this shows when the Action was started.
Started By – this shows who the Action was started by.
Started By Method – how the work began, e.g. incoming email, automatic schedule, manually.
Status - the current state of the work item e.g. In Progress, Waiting, Resolved etc.
Status Reason - this shows the reason the work item's status was updated e.g. if it was updated by a resource, if it was updated by Enate, if it has newly been created etc.
Subject Email - the email address of the subject of a work item
Subject Name - the name of the subject of a work item
Ticket Category Level 1 – high-level categorisation of type of Ticket e.g. ‘Healthcare Request’.
Ticket Category Level 2 – next level categorisation of type of Ticket e.g. ‘International Travel Coverage’.
Ticket Category Level 3 – most detailed-level categorisation of type of Ticket e.g. ‘Eligibility Query’.
Time Remaining When Paused – the amount of time left before the due date at the point the item was placed into a paused state.
Title – a brief text description of the work item, often the subject of the original email.
Wait Type - if a work item is in a state of Waiting, this column will show the type of Waiting the work item is in e.g. Wait for more information, Wait Until, etc.
Work Item Type – i.e. Case, Action or Ticket.
You can also revert the column settings to default if you wish by selecting 'Revert to Defaults'.
The number total at the top right of the grid show the total number of items in the grid and, when filtering, the number of filtered items from that total.
In-grid filtering
You can apply filters to all the standard and custom data columns on the grid by clicking on the filter icon next to the desired column title.
Your applied filters will remain when switching between your Work Inbox, your Team Work Inbox, your Owned Work and your Team Owned Work, as well as after the you log out and log back in.
You can clear the applied filters by clicking on the 'clear filter' icon, and all work items will be displayed again.
You can also apply multiple filters to all the standard and custom data columns on your bot farm grid. The applied filters will remain when switching back to your Team Work Inbox.
You can also search the grid by using the free text search function.
You can copy and paste information from the grid into an Excel spreadsheet by selecting the information you want to copy and using Ctrl C and Ctrl V.
The information that is copied and pasted includes any applied filters. The column titles will automatically be copied and pasted as well.
You are also able to copy and paste all of the information in the grid by using Ctrl-A.
Standard file attachments are denoted with a paperclip icon:
Links are denoted with a links icon:
Attachments from incoming emails are denoted with a green email icon:
Attachments from outgoing emails are denoted with a blue email icon:
If your system has been configured this way (), you can select to override the due date of the new Sub Case you are creating.
If your system has been configured this way (), you must select a schedule for the new Sub Case you are creating.
If the , the changes to Case Short Description will be reflected in the Actions Screens of all the Case's Actions (you may need to refresh your Action screen for this to take immediate effect) and the title of the Action will be made up of:
The is where you can specify the people who relate to the Action.
Note: it is possible to add further relationship types into the system. See here for more information on how to .
An Action's contacts will usually be auto-populated as the same as the contacts for the parent Case. However, if the Action's contacts are not auto-populated or if you want to add a different contact to the Action, you can add contacts to the Action manually by searching for them in the . This change will also be reflected in the Case's contacts too.
Some Actions have a checklist section. This shows the checks which are required for this Action - defined during its .
The Case short description is shown on the right-hand side of the screen. If the has been selected in the Case Info tab in Builder, you will be able to edit the short description of the Case.
Items created in this way will retain a link to the original Case / Ticket and will show on a within it, making it easy to track a group of work items which relate to each other.
The is where you can specify the people who relate to the Case.
Note: it is possible to add further relationship types into the system. See here for more information on how to .
A Case's Contacts Card will not usually be auto-populated, so you need to manually add a contact. You can do this by searching for a contact in the .
Impact on SLA clock: SLA clock PAUSES while an Action is in this state, IF the Action's due date rule (configured during process design) has set to ON. If it is set to OFF, the SLA clock CONTINUES while the Action is in this state.
If there has been an issue with document submission, the system will automatically retry submitting a certain number of times, depending on how your system has been configured in Builder (see for more information).
Once processing is complete, exported files will be attached to the Case and are visible in the .
You can find more information about the states a Ticket goes through , the states of a Case and the states of an Action .
You can display additional custom columns in the Home page grid by selecting them from Custom Data Columns section in the right-hand side of the 'Display and Column Settings’ popup. Custom Data Columns are created in Builder, see for more information.
Any Case/Ticket/Action with an Assigned User
Inbox
Any Case/Ticket/Action with the “More Information” flag set that is configured to use Queues
Inbox
Case with the “Problem” flags set that is configured to use Queues
Inbox
Any Action in a To do / In Progress state that is configured to use Queues
Inbox
Any Ticket in a To do / In Progress state that is configured to use Queues
Inbox
Any Case in a To do / In Progress state with an Owner that does not have the “More Information” or “Problem” flag set that is configured to use Queues
Owned Work
Any Case/Ticket/Action in a Wait State with an Owner where Queues are configured
Owned Work
Any Case/Ticket/Action in a Wait State with an Owner where Queues are not configured
Owned Work
Any Case/Ticket/Action in a Wait State without an Owner where Queues are configured
Owned Work
Any Case/Ticket/Action in a Wait State without an Owner where Queues are not configured
Not displayed
Tickets placed in a Wait State at the same time as changing the Category where Queues are configured
Owned Work
Tickets placed in a Wait State at the same time as changing the Category where Queues are not configured
Not displayed
Tickets already in a Wait State when the Category is changed where Queues are configured
Owned Work
Tickets already in a Wait State when the Category is changed where Queues are not configured
Not displayed
Cases automatically created by Schedule that no User has ever updated where Queues are configured
Owned Work
Cases automatically created by Schedule that no User has ever updated where Queues are not configured
Not displayed
Case/Ticket/Action without an Assigned User or Owner where Queues are not configured
Not displayed
Task can be carried out by a Robot
Robot Task – Needs Attention
New information has been received that hasn't been read yet.
Case only : Case is in a problem State (i.e. needs attention)
The Action is a Peer Review and it is in the "doing" stage.
The Action is a Peer Review and it is in either in the reviewing stage, or the review is complete.
Work Item is in a state of DRAFT
Work Item is in a state of TO DO
Work Item is in a state of IN PROGRESS
Work Item is in a state of WAIT
Work Item is in a state of RESOLVED
Work Item is in a state of CLOSED
Related work items are a tightly connected group of items which, while they behave according to their own specific configuration, do have an active impact on their 'parent' work item - specifically the parent work item will not complete until all of its 'children' have completed first.
Communications will be shared automatically between work items in the related group so they are always visible, and when you reply to an email in one work item, the reply can be seen in all the other work items.
Additionally, files, links, defects, smart cards, and contacts are also shared automatically between all the work items in the group, so updating for example a file in one work item will update the file in all the other work items in the related group as well.
Groups of Related work items include:
A Case and its Actions
A Case and its Sub Case(s)
The remaining Ticket and other 'resolved' Tickets if multiple Tickets have been merged
A 'child' Case and its parent Ticket if a Ticket has been converted to a Case
Note that for split Tickets, a snapshot of the files, links, defects, smart cards, and contacts of the parent are to its child Tickets, so updating for example a file in one work item will not update the file in all the other work items in the related group. However, the parent Ticket, which will have moved to a state of Waiting, will not complete until all of its 'child' Tickets have completed first. Also note that if the parent Ticket receives an incoming email, it will be copied to its child Tickets rather than shared.
When work items don't have an active impact on each other (i.e. they're not part of a Related Work Items group) but there's still a loose connection between them and you want to be able to quickly jump to one from another, you should use the Linked Work Item feature in Enate.
Work items with a 'Linked' relationship behave according to their own specific configuration and do not need to wait for the other to complete before they can complete themselves. You can easily link two or more work items together at any time and it's a very useful, flexible way of loosely connecting together items so people in e.g. different departments can stay easily up to date on how other work connected to the Ticket/Case they're working on is going.
Communications will also not be shared automatically between linked work items, but you can choose to copy a snapshot of the communications in one work item to a work item it is linked to.
Note that you also have the option to share emails between linked work items - see here for more information on how to share emails between linked work items.
Additionally, the files, links, defects, custom data, and contacts will not be shared automatically when launching a new linked work item, but you can choose to copy a snapshot of them. Any updates made to these will not be reflected in the other linked work items.
Work items with a linked relationship will show in the 'Linked Work' tab in Cases and Tickets.
Using this type of connection is useful if e.g. a Case’s due date is not dependent on some other piece of work being completed (e.g. by a different department), but it's still considered useful for people working on either one to remain aware of activity on the other and, importantly, to have a quick point of accessing the other.
Work Items can be linked together in the following ways:
A Case or a Ticket launched directly from within an existing Case or Ticket.
Manually adding a link from a Case/Ticket to another existing Case or Ticket.
Cases can be started in the following ways:
Via an incoming email (if the system is configured to do so for that email mailbox)
By a ‘Start Case’ Action within another Case flow.
Manually, from the ‘Create New Work Item’ link in the Work Manager toolbar
Automatically started
Via third party integrations
When manually starting a Case directly in Enate, it will sit in a state of 'Draft' until it has been submitted for the first time.
When starting manually, you should fill in the ‘Case Short Description’.
Once a Case has been submitted into Enate, it will then sit in a status of ‘To Do’ until a resource has picked it up - this could be a human resource or a robot resource. Once you start updating a Case sitting in this state, it will:
automatically assign to you and
the status will change to ‘In progress’
You can also choose to change the state yourself. This signifies that work is now underway and it will stay in that status until it’s resolved – assuming e.g. no waiting for further information.
If you’ve picked up a Case in error, or if your reach the conclusion that it’s not a piece of work you’re going to be able to progress you can unassign it from yourself, either to another resource or just back to its Queue. This could be after 10 seconds or half an hour, but when you do this the system will automatically set the status back to ‘To Do’ to let everyone know that it’s not going to be progressed until another resource picks it up. You can also just manually set the status back to ‘To Do’ if for example you started working on it in error and need to quickly undo the status change.
Similarly if a robot resource rejects a piece of work, its status will be set back to ‘To Do’ as part of handing it over for a human resource to carry out.
Additionally, if there is a problem with a Case (usually be because of an issue with one of its Actions), the Case will be put back into a state of 'To Do'.
Once the Case is in this state, the Case owner can see this along with the reason – i.e. often the problem Action in the Info Card. As Case Owner, you have various options available to you:
Rework the Case from a previous step or from completed Actions within this step
Place the Case on Wait - Pause
Reset the Case to In Progress
Manually launch / re-launch Actions
If you’re working on a Case and you have to temporarily halt work on it because you’re waiting for some additional information or because of some other temporary blocker, you should choose the ‘Wait’ status.
When a Case is in a state of Waiting, no more new Actions for that Case will be launched until the Case moves back into a state of To Do or In Progress. Users can complete Actions that have already launched and are already running Actions, but once these Actions have been completed, no new Actions will get launched.
When placing a Case into a state of 'Wait' you need to specify the type of wait. The options are:
Impact on SLA clock: SLA clock PAUSES while Case is in this state, IF the Case's Due Date rule (configured during process design) has 'Add Wait Time To Due Date' set to ON. If it is set to OFF, the SLA Clock CONTINUES while Case is in this state.
If you’re working on a Case and you have to temporarily halt work on it because you’re waiting for some information from a third party or client, you should choose 'Wait for more information'.
When a Case is in a state of Waiting, no more new Actions for that Case will be launched until the Case moves back into a state of To Do or In Progress. Users can complete Actions that have already launched and are already running Actions, but once these Actions have been completed, no new Actions will get launched.
When you click on 'Wait for more information', you must choose the reason for placing the Case in that state from the dropdown list.
Upon confirming the 'Wait for more information' status, the Case will move from your Work Inbox into your Owned Work list, as there is no active work to be carried out on it until a response is received.
Once a response has been received, the Case will move back from your Owned Work list into your Work Inbox in a state of To Do, highlighted for you to progress.
The Remaining Hours of SLA when a Case is set to 'Waiting for more Information' will be displayed. To explain..
If a Case is set to 'Waiting for more Information' and the option to 'Add Wait Time To Due Date' is set to ON in the Case's Due Date rule (defined during process design in Builder), then the system will PAUSE the SLA clock. In conjunction with this, the Due Date value normally displayed on the Case header bar will be hidden (because until the SLA clock starts again, we can't know it!). In its place, the system will show the remaining time which was left until the Case is due at the point where it was put into this state (or how long it was overdue at the point where it was put into this state, if it has already passed the due date).
Example: If the Case is yet to pass the due date the the message will show as ‘Due: Paused x h y m before due’.
Example: If the work has passed the due date then the message will show as ‘Due: Paused x h y m after overdue’.
Impact on SLA Clock: SLA Clock CONTINUES while Case is in this state.
If you’re working on a Case and you have to temporarily halt work on it until a specific future date/time, you should choose 'Wait Until'.
When a Case is in this state, no more new Actions for that Case will be launched until the Follow Up Datetime has been reached. Users can complete Actions that have already launched and are already running Actions, but once these Actions have been completed, no new Actions will get launched.
When you click on 'Wait Until', you must specify the desired follow up date and time.
Upon confirming the 'Wait Until' status, the Case will move from your Work Inbox into your Owned Work list, as there is no active work to be carried out on it until the follow up date.
When this date is reached, the Case will move back from your Owned Work list into your Work Inbox in a state of To Do, highlighted for you to progress.
Impact on SLA Clock: SLA Clock CONTINUES while Case is in this state.
If you’re working on a Case and you have to temporarily halt work on it, but you are not waiting for some information from a third party or client, or waiting until a specific future date/time, you should choose 'Pause'.
When a Case is in a state of Waiting, no more new Actions for that Case will be launched until a user actively changes the status of the Case to To Do or In Progress. There is no automatic way of taking a Case out of a state of Pause, it can only be done manually. Users can complete Actions that have already launched and are already running Actions, but once these Actions have been completed, no new Actions will get launched.
Upon confirming the 'Pause' status, the Case will move from your Work Inbox into your Owned Work list, as there is no active work to be carried out on it by you until a user actively changes the status of the Case to To Do or In Progress.
When this is done, the Case will move back from your Owned Work list into your Work Inbox in a state of To Do, highlighted for you to progress.
When all the actions in a Case are completed, the system will move the Case into a state of 'Resolved' if the Case has been configured with a feedback window. It will sit in this status for a brief period during which the service recipient may respond and the Case may be reopened, either manually or automatically upon receipt of a new incoming email or feedback within the time period.
Please note that when work items are reopened, the data stored for who resolved it and when it was resolved are persisted and are not overwritten when the item is resolved for a second time.
After the feedback window has completed without any further response, or if the Case does not have a feedback window, the Case will move to a state of fully 'Closed'. Any subsequent mails received will launch a brand new work item.
Selecting the 'Cancel' option and hitting the button to confirm will abort the Case. It will be completely closed and will no longer be available to process. If you re-open the tab for this item, system will confirm that the Case has been aborted.
Details around how to configure actions to trigger external APIs, and how they will display in Work Manager for operational users.
Similar to other action archetypes, 'Trigger External API' actions can be used in Case processes, and are used for when you need to automatically call out to another system, passing data to it and potentially getting the external system to pass updated custom data back into Enate.
For information on how to configure 'Trigger External API' Actions check out this Builder section.
Sometimes there can be a delay when waiting for the external system to respond. When that happens, i.e. when the ‘Trigger External API’ Action is waiting for information to come back from an external system, the Action info card will display in Work Manager as being in a state of 'Waiting'.
When the external system ultimately responds to Enate with the data update, it will be with a marker to say whether it has been successful OR unsuccessful:
If the system is responding to say it has been successful, the Action will automatically move to a state of 'Closed', with a Resolution Method of 'Done Successfully'.
Response with Unsuccessful Completion
If the system is responding to say it has been unsuccessful, the Action move into a state of 'To Do', with a reason of 'Updated by Integration'. The external API can also respond with additional information regarding why it was unsuccessful. This information will display in the Info card of the Action in the 'Rejected Reason' section.
If the Action isn't successful because it did not complete within the time set for it (configured in Builder), then it will moved to a state of 'To Do' with a reason of 'Timeout' and it will allocate to a Queue / human user based on the configured allocation rules.
Such unsuccessful Actions will now effectively behave as a standard manual action.
Please note that the Case owner will NOT be notified in these situations.
If the Action is not able to connect to the external system, it will automatically retry connecting for a certain number of times, depending on how your system has been configured in Builder (see here for more information). You will also be shown an error message bar on the Action showing:
when the error occurred
when the system will retry establishing a connection automatically
how many times the system has automatically retried establishing a connection, and
how many times the system will automatically retry establishing a connection.
You are able to manually retry establishing a connection from here too, by clicking the 'Retry' link in the error message.
Please note that when you do a manual retry, this will be counted as an attempted retry and will therefore be included in the number showing how many times the system has 'automatically' retried establishing a connection.
If the Action fails to establish a connection following the automatic retries (e.g. if the retry setting is set to 5 and the system fails to establish a connection following 5 automatic retries), it will move to a state of 'Closed' with a resolution method of 'Not Done Successfully'.
In this circumstance of the Action failing to establish connection with the external system, this will escalate to the Case Owner, highlighting in the Action section of the Case screen that this Action was Closed - Not Done Successfully.
When the Action receives the required information, it will close automatically.
If the automatic retry setting in Builder is changed after the system has automatically retried establishing a connection with an external system, the following will occur:
If, for example, the retry setting was originally set to 5 and the system automatically retried establishing a connection 5 times but failed, the Action will have moved to a state of Closed with an error message showing a retry count of 5/5.
If the retry setting then gets subsequently increased to anything above 5, for example 7, the error message will display a retry count of 5/7, but the system will NOT automatically retry establishing a connection for a 6th and 7th time as the Action is already closed.
However, if the Action had not yet moved to a state of Closed because it had not yet reached the maximum number of automatic retries (e.g. it had only retried 4 times out of the 5), then increasing the retry setting to 7 means that the Action will automatically retry establishing connecting until the count has reached 7.
Conversely, if you reduce the retry setting after retries have started, e.g. you're on retry 4 of 10 but then reduce the max down to 4, the system will still display 4 of 10 but will in fact be closed.
The Linked Work tab is where you can view all linked work items of a Ticket or Case.
Note that Sub-Cases created via the '+ Work item' link will still display in the 'Sub Cases' tab for the time-being, and do not show in the Links tab.
Within the Links tab grid you can a list of Linked work item, showing their reference, title, assignee, Queue and due date of a work item.
There is also an icon to unlink the work item if they have been linked in error.
You can also expand linked Cases to see their Actions.
If you don't have permissions on a certain business process, the work items from that process will be greyed out and you won't be able to open or edit them. You'll still be able to see higher level information about the work item, e.g. who they're assigned to, which Queue they're in and when they're due.
'Send Email' Actions involve Enate auto-sending an email and then the Action will immediately close. Work Manager Users should not have to do any work on this type of Action.
'Send Email and Wait' Actions involve Enate auto-sending an email. The Action will then move to a state of Waiting until a response has been received. Once a response has been received, the Action will move to a state of To Do to be processed further.
The To address and any CC or BCC addresses on the email are configured in Builder - see this article about how to configure 'Send Email' Actions in Builder:
Once the email has been sent, an entry will appear in the timeline showing when it was sent, who it sent from and to, any CC or BCC addresses, the email subject and if you click to expand, the email body itself.
If an invalid To, CC or BCC email address is used, the email for the Send Email/Send Email and Wait Action will fail to auto-send and the Action will then be moved back to its Queue.
A warning will appear in the timeline:
The Case owner can then decide if they want to manually send the email and will need to correct the email address and add the email body manually. They should also contact their system administrator to alert them about the issue so that they can correct the email address to prevent future email failure.
Various features in Enate allow you to manage activities being carried out by different teams, letting you easily create and oversee work items even when you don't have full permissions on each other's work.
In addition to having the ability to create new linked work items from a Case or Ticket, you can also create links between existing Cases and Tickets to allow you to better manage activities being carried out by different teams.
You can create links between existing work items in two ways:
Note that you can only create links between Cases and Tickets and you cannot copy communications, files, defects, links or custom data when creating a link between existing work items.
You can link existing work items from your Home page by selecting the Cases and Tickets from the Home Page grid (which could be displaying your Work Inbox, Team's Work Inbox, Owned Work or Team's Owned Work) that you want to link together and selecting the 'Link' option that appears at the top of the grid.
The first Case or Ticket that you select will be the work item that all of the subsequent selected work items will be linked to (or the first in your list if you've used the 'Select All' option).
The resulting pop-up will confirm to you the Case / Ticket the items will be linked to, and the specific items themselves, before allowing you to complete the linking confirmation:
You can link up to a maximum of 50 work items at one time, but there is no upper limit on the number of work items that can ever be linked.
If you subsequently go to this main Ticket / Case that everything has been linked to, on its Linked Work tab you'll see ALL of the items you chose to link to it.
However if you're in one of the works items you chose to link to this main Ticket / Case, on that Linked Work tab you'll only see a record of that main Ticket / Case (and not all of the other ones which were linked).
You can link existing work items from within a work item itself by going to the work item's screen and selecting the '+ Work item' option and then choosing to add an 'Existing item'.
In the resulting pop-up you can search for the Cases and/or Tickets you want to link this work item to.
You link up to a maximum of 50 work items at one time, but there is no limit on the number of work items that can ever be linked.
A link to the new linked Case or Ticket will appear in the Linked Work tab in screen of the work items that have been linked.
You can unlink work items at any time by going to the Linked Work tab in the work item's screen and selecting the Unlink icon.
Both Team Leaders and Team Members, (provided the Team Member has been set up with the 'Can Assign' permission in Builder, see here for more information) have the ability to assign/reassign one or more work items to themselves or to other members of their team. You can assign/reassign a work item to yourself in a number of ways:
1) If the work item is not assigned to anyone, as soon as you start to do any activity which requires assignment the system will automatically assign the work to you (i.e. you do not need to manually set yourself as the assignee).
2) If the work item is assigned to a different user, the system will display a short message when opening the work letting you know this. Click the ‘Take it’ grab icon to instantly assign the work item to yourself.
3) From the homepage grid by selecting which work items you want to reassign to yourself and clicking on the 'Reassign' button that will have appeared at the top of the grid. This will open up a popup where you can can then select the 'Reassign to me' option and you can also add a note if you wish.
If you open an unassigned work item and subsequently make a change which would result in it being auto-assigned to you, if during the interim period another user has opened the same work item and has already assigned to themselves, the system will display a warning popup explaining that if you assign the work to you, any unsaved changes from the other user will be lost.
You have the choice to continue with assigning the work to you (which will discard the other person’s unsaved changes) or cancel your reassignment / update.
Note that some activities can be performed even if the work is not assigned to you since they are purely additive:
Adding a Note
Sending an Email
Adding an Action while in a Case
Both Team Leaders and Team Members, (provided the Team Member has been set up with the 'Can Assign' permission in Builder, see here for more information) have the ability to reassign one or more work items to themselves or to other members of their team. You can do this in a couple of ways.
1) From the work item itself by clicking on the assignee dropdown in the header ribbon and selecting to reassign it to a different user. A popup will display; you can search for a user to assign work to and add a note to go along with the assignment. A notification message (including the note) will be sent to the new user.
2) From the homepage grid by selecting which work items you want to reassign and clicking on the 'Reassign' button that will have appeared at the top of the grid. Clicking on reassign will open up a popup where you can search for which team member you wish to reassign the work items to, and you can also add a note if you wish.
If a work item can be done by a robot, you can also choose to reassign the item to any individual bots that are in your team.
You can also make that reassignment choice at the farm level by selecting ‘Any Bot within [farm name]’. The system will then automatically assign the work item to one of the bots in the farm.
Both Team Leaders and Team Members are able to unassign one or more work items. You are able to unassign work items in any state apart from Closed.
To unassign work items, select which work items you want to unassign from your Work Inbox. This will make the option to Reassign and Unassign appear at the top of the grid.
Once you have unassigned the desired work items, they will then become available for users to pick up from their work Queue.
If your system is set up to allow it, you are able to mark one or more work items from your Work Inbox as 'Complete' directly from the Work Inbox grid. Both Team Leaders and Team Members can use this function.
Note: this is only possible for work items in your Work Inbox. Additionally, this is not possible for Cases or Peer Review Actions.
Enate's Work Manager provides you with embedded reporting capabilities, driven by Microsoft's Power BI reporting platform, which gives you lots of additional information at your disposal to gain new insights and support for your business operations.
You get:
Standard, out of the box reports based on Enate data. Your user role will determine which standard reports you are able to see
The ability to build on the standard reports to create your own personalized reports with exactly what you want
The ability to save your personalized reports so you can easily navigate back to them
The ability to share your reports with whoever you think needs to see it
Team Leaders or users with the 'Can customize reports' permission will also get access to advanced editing options which allows them to create brand new visuals and to delete visuals, as well as the ability to create and delete cards
Watch this video to find out more:
Please note that at the moment, dates given to the creation of reports will be according to UTC time zone. Additionally, report data is not updated in real-time, and will be updated a regular scheduled intervals (last updated time stamp is shown on a report). Also, at the moment reports are only available in English. Lastly, information regarding closed work items will only be shown for the past year. Open/running work items will show information spanning the entirety of its processing time, even if it has been longer than one year.
You can access reports from the brand new section in the Work Manager the nav menu.
Clicking on the main Reports link will open up the Reports page, with the default standard report depending on your role displayed. For Team Leaders this will be the Team View report and for Team Members it will be the User's Overview report.
If you hover over the Reports link, you'll see a list of reports that you have access to, divided into various sections:
Standard Reports - here you'll see the standard, out of the box reports associated with your role data. Your user role will determine which standard reports you are able to see - generally, if you're someone with team member level access, you'll see the 'User's Overview' report, which shows data about your own work and if you've got more team leader-like access, you'll also be able to see the 'Team View', which looks at data about work across your team.
My Reports - here you'll see reports that you have personalized in some way and then saved as a new report
Shared with Me - these are reports, custom or standard, that have been shared with you by someone else
Reports are sorted alphabetically and you can mark a report as a favorite. Favorite reports will appear above your 'non-favorite' reports.
Once you've opened up a report, you'll see the report name and when it was last updated at the top.
The 'All Reports' button will show you the list of reports that you have access to, divided into various sections:
Standard Reports - these are standard, out of the box reports associated with your role data.
My Reports - here you'll reports that you have personalized in some way and then saved as a new report
Shared with Me - these are reports, custom or standard, that have been shared with you by someone else
You can save a personalized report by clicking the 'Save As' option and you can share a report via the Share button.
A report will generally contain a mixture of cards, showing you headline level information, and a number of visuals.
The data fields you'll have access to will depend on the report you have access to - each report has its own set of data fields. If you have access to a report, you have access to all of the data fields within the report too. For example, the 'User's Overview' report, and any report which was created from it, displays data about you and your work. The Team View report or, again, any report created from it, allows access to data about your team and the work in your business area more generally.
If there are any of your custom data fields that you'd like to see in your reports, ask your admin to get in touch with Enate Customer Support to get these made available for you.
All users have the ability to personalize a report to get the data to show just how they want, for example by applying filters or by adjusting the data fields. See the personalizing a report section to find out more about what options you have.
If you have the 'Can customize reports' permission, you'll be able to click on 'Advanced' mode and get access to more advanced editing options, which includes all the standard personalization options as well the ability to create brand new visuals, to delete visuals, and to create and delete cards.
All users have the ability to personalize a report to get the data to show just how they want.
There are a number of filter options at the top that you can apply to the report. You can choose to filter the report by, customers, contacts and so forth, plus specific types of Case or Ticket (under the Process dropdown) and certain Queues or work in a given state. If you want to remove all these filters, click on the main Filter display button and scroll down to find the Clear Filters link.
Hovering over a visual also gives you further editing options. Links in the header of each visual will let you drill down and apply further filters.
If you click on the personalize link you'll see much more options that you have to play with. You can change the visualisation type to show your data in a different way and you can change the data fields used in the visual.
The data fields you'll have access to will depend on the report you have access to - each report has its own set of data fields. If you have access to a report, you have access to all of the data fields within the report too.
For example, the 'User's Overview' report, and any report which was created from it, displays data about you and your work. The Team View report or, again, any report created from it, allows access to data about your team and the work in your business area more generally.
If there are any of your custom data fields that you'd like to see in your reports, ask your admin to get in touch with Enate Customer Support to get these made available for you.
You can also export an individual visual into Excel. There's also a 'focus' option to give a dedicated view of a single visual, and you can also choose to see the underlying data in a table.
You can easily discard your changes at any time by reverting back to the previous view of a visual.
You can find out more about the editing options you have from Microsoft's own Power BI documentation, available here:
You can also save a personalized report by clicking the 'Save As' option, making it easier for you to come back to, and you can share a report via the Share button.
You can save your personalized report so that you can access it easily ongoing by clicking the 'Save As' button.
Depending upon who originally created the report, there are a couple of options when it comes to saving a report:
If you have made adjustments to a report created by someone else, you will have to save the report as a brand new (the 'saved as a new report' checkbox is auto-selected for you) since it's not your original report.
If you have made adjustments to a report created by yourself (and the report is in your 'My Reports' section), you can either:
Update the existing report by clicking on 'Save As' and then de-selecting the 'Save as a new report' option
Save the report as a brand new report by clicking on 'Save As' and then selecting the option of saving the report as a brand new report
Once you have clicked 'Confirm', the saved report will appear in the 'My Reports' section, which you can access from the main system header, or from the reports list in your reports page. All your saved reports will appear here.
In addition to all the report personalization options listed above, Team Leaders or people with the 'Can customize reports' permission will also get access to advanced editing options.
This lets them completely remove and create brand new visuals within a report, rather than just having the ability to modify existing ones, and gives them the ability to create and delete cards with headline level information.
You can easily discard your changes at any time by reverting back to the previous view of a visual
You can find out more about the advanced editing options you have from Microsoft's own Power BI documentation, available here:
You can also share reports with other users by clicking on the 'Share' option and selecting which users you want to share it with.
The report will then show in the user(s) Shared Reports section.
Note that you will only be able to share reports with someone if they have permission to view all of the data in the report.
You can also copy the Report link URL here too, if you want to share the report via another app.
Reports that have been shared with you will appear in your Shared Reports list.
When it comes to deleting reports, there are a few of things to be aware of.
You can delete any of your own personalized reports i.e. any of the reports under the 'My Reports' section.
You can delete any reports that have been shared with you i.e. any of the reports under the 'Shared Reports' section. Deleting a report that has been shared with you will not delete the report for anyone else.
You cannot delete an original standard report. However, if you have personalized a standard report and saved that personalized report (and it therefore appears under the 'My Reports' section), you can delete that personalized report (see above point).
Deleting a report that you have shared with another user will delete the 'original' report for you, as well as deleting the shared report for the other user. The report will also no longer be accessible for that user via a saved URL link.
Any reports deleted by yourself will still be accessible via a saved URL link.
Currently, Enate provides three standard, out of the box reports:
Your user role will determine which standard reports you are able to see.
Information on how client users can provide feedback to you on specific work items, via feeback links available in the footer of emails sent from Enate.
If the ‘Allow Feedback’ setting is ticked in the Ticket's Builder settings (see here for more information on how to do this), outgoing emails will contain a footer-based link for recipients to give feedback scores.
They can do this at any point in the processing of the Ticket. When a client user clicks on any of these links, a browser window will be opened for them showing the Enate Feedback form. It offers the same feedback icons as shown in their email, but allows a user to change their selection should they wish, and also to add an additional comment before submitting.
All feedback and comments are subsequently stored in Work Manager against this Ticket, for Agents to view.
Further to this, feedback data is stored in the Data Warehouse, allowing longer-term analysis of feedback data (i.e. you can build reports to analyse this data across multiple different criteria).
When dealing with a Ticket, if a client user has provided feedback (via the feedback footer links in one of the emails they have received from Enate) Agents are able to see the customer’s current feedback rating via the 'smiley face' icon link in the ribbon bar of the Ticket:
Clicking on this will open a feedback popup displaying the client user's feedback rating/s (via emoticon), along with any associated comments. The overall average rating, between 1 and 5 - calculated when feedback is given multiple times on a single Ticket - is also show at the top of the popup. Latest feedback is shown at the top of the screen.
Further to this, this feedback data is also stored in the Data Warehouse, allowing longer-term analysis of feedback data (i.e. you can build reports to analyse this data across multiple different criteria).
The Team View report displays information relating to email sentiment analysis allowing users to quickly and clearly see developing trends regarding incoming emails and take action where necessary.
Access to and the ability to edit the Team View is controlled by permissions in user roles, in the same way as all other reports within Enate. If users do not have the right permissions enabled, they will not be able to access or edit the report.
Here are some of the type of information which can be found within the report
Ensure uninterrupted service and efficient workload planning by tracking monthly work item initiation volumes.
Optimize resource availability and streamline operational efficiency by monitoring monthly work item closures.
Prioritize backlog resolution and task management by categorizing open work items by age in days.
Aid targeted defect resolution and service quality improvement by highlighting defect categories needing attention.
Enable efficient resource allocation and service delivery optimization with monthly user and active user counts.
See below for a complete list of all the available data fields that can be used within the User Insights report:
Activity
Active Users
Count of users who are active on a selected date
Activity
Total Hrs Logged
Total time in hours spent by an Agent on all the Work Items they worked on for the selected date range
Activity
Total Users
Total number of users responsible for all the Work Items in a Queue
Activity
Activity Type
The type of activity performed on the Work Item by an Agent (e.g. 'Saved' or 'Completed')
Activity
Duration in Sec
Time spent in seconds on a Work Item by an Agent. Manually entered time is considered if available.
Activity
StartDate
The Work Item activity Start Date in date/time format
Activity
StartDate_date
The Work Item activity Start Date in date only format
Activity
User Name
The user who performed the activity
Context
Contract
The name of the contract
Context
Customer
The name of the customer
Context
Service
The name of the service
Context
Supplier
The name of the supplier
Date
Date
Calendar range of dates for filtering data
Date
Month
Months of the dates
Date
Week
Weeks of the dates
Date
Year
Year of the dates
Defects
Work Item Count
Number of Work Items that have defects
Defects
Date Raised
Date on which the defect was raised for a Work Item
Defects
Defect Category
Category of the defect
Defects
Description
Description of the defect
Defects
Status
States whether the defect is resolved or not
Feedback
Avg. rating
Average of ratings for each Work Item
Feedback
Rating
User rating for each Work Item
Feedback
Reference
Reference number of a Work Item that has feedback
Process
Process
Name of the process each Work Item belongs to
Process
Work Item Type
Type of the Work Item (Ticket, Action or Case)
Queues
Queue
Name of the queue the Work Item was last present in
Status
Status
Work Item Status (To Do, In Progress, Waiting , Resolved , Closed)
Status Reason
Status Reason
Reason behind the status change of the Work Item (Newly Created, new Info Receieved, Blocked by Business rule etc.)
Wait Status History
Waiting each Day
Count of Work Items that are set to waiting status on a particular day by the Agent (out of the Work Items he/she working/worked on)
Wait Status History
EndDate
End Date in Date time format when Work Item was in waiting state
Wait Status History
EndDate_date
End Date in Date only format when Work Item was in waiting state
Wait Status History
StartDate
Start Date in Date time format when Work Item was in waiting state
Wait Status History
StartDate_date
Start Date in Date only format when Work Item was in waiting state
Wait Status History
User Name
Agent who set the status of Work Item to Waiting
Work Items
Action
Sum of Closed and Waiting work items on a particular day by an Agent
Work Items
Work Items Assigned Today
Count of Work Items that are assgined to the agent today
Work Items
Work Items Closed
Total Work Items closed by agent for the selected date range
Work Items
Work Items Closed Today
Count of Work Items that are closed by agent today
Work Items
Work Items Due Today
Count of Work Items that are due today by agent
Work Items
Work Items Open
Total Work Items that are Open by agent
Work Items
Work Items Overdue
Total Work Items that are Overdue by agent
Work Items
Work Items Reopened
Total Tickets that are reopened for the agent
Work Items
Work Items Resolved
Total Work Items that are Resolved by agent for the selected date range
Work Items
Work Items Started
Total Work Items started by agent for the selected date range
Ageing Category
Grouping of Aging in Days into different buckets
Work Items
Ageing In Days
Ageing in calendar days. For completed Work Items its (end date - start date), for open items its (today - start date).
Work Items
Count of Affected Records
Records affected count
Work Items
Count of Defects
Count of defects each Work Item has (if any)
Work Items
Count of Rework
Count of rework each Work Item has (if any)
Work Items
DueDate
Work Item Due Date in date time format
Work Items
DueDate_date
Work Item Due Date in date only format
Work Items
EndDate
Work Item End Date in date time format
Work Items
EndDate_date
Work Item End Date in date only format
Work Items
Has Defects
Whether the Work Item has defect or not (Yes or No)
Work Items
Is Reopened
Tickets that got opened after going to resolved status
Work Items
Reference
Reference number of each Work Item
Resolved Date
Work Item resolved date in date/time format
Resolved Date_date
Work Item resolved date in date format
Work Items
SLA
Service Level Agreement to indicate where Work Item is Overdue or not
Work Items
StartDate
Work Item Start Date in date time format
Work Items
Start Date_date
Work Item Start Date in date only format
Work Items
Title
Title of the Work Item
As part of supporting work being carried out across multiple Cases & Tickets, you can share emails between Linked work items to allow them to be viewed more widely. You can even do this for work items which you don't have permissions on.
You can share emails between linked work items in two ways.
1. From an existing email - Clicking on the '+' icon at the top of an existing email in the timeline and selecting the relevant work item you wish to share the email with.
2. From composing new email - Another way is when writing a new email, you can simply add the work item reference number into the To / CC / BCC of an email by clicking the '+' icon, just as you wold when adding an email address:
You can even use this approach when you just want to share emails between linked work items, without needing to add an email address.
Please note that you can only share emails between work items that are linked. You cannot share emails between Closed work items. Additionally, once an email has been shared between work items, it cannot be unshared.
The email will be sent as normal to any emails addresses specified, and it will also be shared with the selected work items.
When someone responds to the shared email, that response will be attached to both work items.
Sometimes when you're sending an email on a Work Item and you need to involve teams in other parts of your business, you may not know if they're using Enate yet to manage their work - particularly in larger organisations - and so it can be unclear precisely how to proceed.
Now, when you're working in Enate, you no longer have to worry about this - the system will take care of this for you. You can just write your mail and the system will know what to do next; if anyone internal is involved and they're using Enate, we'll prompt you with tickets or cases of theirs that you might want to share this email with, or quickly create a new work item if needed.
Doing so helps keep all subsequent communications tightly synched up between those teams and any external parties. If you're sending the email to someone who is not using Enate, the system will just send them the email.
If we take an example where we have:
Jane, an Agent working out of Team A in the UK
Karina, an agent in Team B in Poland
An external party who has mailed in a query initially relating to the UK, which lands with Team A
Jane in Team A is writing a response email to the external requestor also see that part of the query needs to involve their Polish team, Team B. Jane doesn't need to know if the Polish team are using Enate, she just adds their email address to her outgoing email.
Enate knows that the Polish team's email address is connected to an Enate mailbox and so it's going to result in Ticket or Case for them. Upon clicking to send the email, Enate will bring up a pop-up explaining this to the Agent, and asking for some more information which will help in the creation of of the work item for the other team.
Once the agent adds this further information to create a linked work item she can confirm to proceed. The email gets sent out to any external recipients, and the other team, Team B in Poland, see the email within a relevant, LINKED, Ticket or Case. Both Teams are aware of the other team's Linked ticket or Case and can keep themselves in the loop on progress.
If Team B's activities happen to fall outside of Team A's permissions, they're still able to see at least the header-level information for it on the Linked Items screen.
Importantly, all the downstream communications get kept tightly in synch.
The External recipient can see both team's addresses on their email and, if they send back a response, BOTH teams will be updated at the same time. Everyone is kept in the loop.
In the most regular scenario, the pop-up would likely show the single, already linked ticket or Case which Team B are working on, essentially saying 'do you want to share this mail with Team B's running ticket?'.
If there's any other internal email addresses added to a mail, going to areas of your business that aren't yet using Enate that's fine - they'll simply go out as emails to communicate with that other team as they normally would.
IMPORTANT NOTE: in order to make use of these features, your email admin team MUST have enabled the 'Plus Addressing' setting in your email server setup - this is what helps route all mails through to the right work items downstream.
For more information on Plus Addressing and how to enable it, see this article:
The Insights page, available from the main menu, shows a daily breakout of your Insights Data, relating to how time is spent each day. use this screen to view and adjust their Insights data across a number of days via the calendar control. have these same options, plus additional features available for this page, .
Team Leaders can use this data to see patterns in how time is being spent through their team, both here and in the Insights into upcoming availability of their team can also be seen here and such data can contribute to further reports to help with short-term capacity planning. Team Leaders should primarily use this page to help ensure all required data has been filled in by their team.
You can access the Insights page from the Nav item option, and via a link at the top of the .
The view defaults to today's date. For each day a user will see in the main section:
The 'How are you feeling' value to the day (this can also be set here, but once set is read-only and comment shows as a mouseover tooltip).
Data they manually entered on the Insights popup (or indeed on this same main Insights Screen)
Time auto-tracked by Enate - This is Time which Enate has tracked being spent on the Ticket, Case, Action screen or on an Enate email on this day, (includes manual adjustments)
The overall totals hours of these numbers
These values are grouped into two section showing:
'Operational value added hours' - spent actively performing work for service delivery
'Business value added hours' - spent on suppotring activity which indirectly contributes to service delivery
Modifying Values
The Insights values (number of Hours and minutes) can be modified by users for each day selected.
Users can change all of these values manually except for the 'Time auto-tracked by Enate' value, which comes from the Time Tracker control on all work items the users worked on on that day (and any work item-related emails they worked on in the Email view). Note that the time tracker data will take manually applied overrides set on work items in preferences to auto-tracked time, wherever they have been entered.
Click Submit to save any adjustments.
Adding missing data
For days marked as still missing any confirmed data, a message will show at the top of the table. All missing data should be added, including confirming of the Working Hours for that day (a suggested value will often be displayed)
Click Submit to save any adjustments.
The following data is displayed on the main section, corresponding with the data options shown on the Insights Popup.
Working Hours - Standard amount of working hours for this day.
Breaks - Time spent on breaks, e.g. lunch, throughout this day.
Downtime - Time lost due to, e.g. system issues, or non-availability of work.
Time auto-tracked by Enate - Time which Enate has tracked being spent on the Ticket, Case, Action screen or on an Enate email on this day, (includes manual adjustments)
Active time not tracked by Enate - (only available for historic dates). Time spent actively working to provide service but where a Ticket, Case or Action screen, or Enate email, is NOT open in Enate to auto-track this time.
Examples might be: time spent on the Enate homepage or working in another system while an Enate work item tab is NOT open and so not auto-tracking time. Note: This should NOT include activities such as meetings or training, which should be noted separately.
Meetings - time spent in any collaborative gathering or group meeting.
Feedback / 1-2-1 - time spent in individual sessions with e.g. team leader, manager, mentor.
Training - time in organised training or knowledge-transfer sessions.
Other - time spent on any other activities which are not listed above, or any additional breaks taken in a day.
Users can use the calendar control to flip between dates, updating the Insights data displayed in the main section to show data for that date. They also have the following options:
View and mark dates as 'On Leave', i.e. vacation days (shown in yellow).
View and mark dates as a 'non-working day' for that user, e.g. a weekend day or equivalent (shown in purple).
View dates where their Insights data is currently incomplete (date shown in RED). Use this control to help identify which dates you need to fill in gaps in Insights data.
Dates where they can no longer adjust data are shown greyed out.
Team members can add or Edit Insights data (including setting dates as 'On Leave' or 'Non-Working Day' for up to 7 days in the past). If you need your data to be adjusted for dates beyond that, speak with your Team Leader who can make necessary adjustment for up to 31 days.
Remember that users can enter future Insights data, particularly planned leave and non-working days can be entered in advance if missing, the help Team Leaders withe future capacity planning.
Team Leaders* have all the same features that Team Members have on the Insights page, PLUS additional features available to them, with a Team section, and an additional tab in the Calendar section. *(Specifically: users with the 'Set up Team & Queues' feature access option enabled )
To identify missing Insights data quickly, Team Leaders can:
Look at the Teams section first, click on a user with a red circle (showing they have missing data on that date). Fix their data, then look at the Calendar to see any other 'red' highlighted days where data is missing for that user, and go through each until data is complete.
OR
Select the Team Calendar first, select a date highlighted in red (showing that at least one team member has missing data). Then select the users from the Team section circled in red and work to fix their data. Cycle through each red date until all missing user data is complete.
Team Leaders can see their team members in the Teams section.
Clicking on any team member will show their calendar and the Insights Data in the main section for the selected date. They can flip between dates, viewing and if necessary adjusting the Insights data. They also have the following options to adjust that user's data, in the user's calendar displayed:
View and mark dates as 'On Leave', i.e. vacation days (shown in yellow).
View and mark dates as a 'non-working day' for that user, e.g. a weekend day or equivalent (shown in purple).
View dates where their Insights data is currently incomplete for the selected user (date shown in RED).
Dates where they can no longer adjust data are shown greyed out.
Finding missing data: Team Leader should use this view to click on a user with a red circle (showing they have missing data on that date). Fix their data, then look at the Calendar to see any other 'red' highlighted days where data is missing for that user, and go through each until data is complete.
Team Leaders have are able to see each of the team member's detailed calendar when they click on them. They also have a Team Calendar tab. This will display in red any day where at least one team member has incomplete Insights data.
Finding missing data: Team Leader should use this Team Calendar to identify each date highlighted in red, the select the users from the Team section who are circled in red, and work to fix their data. Cycle through each red date until all missing user data is complete.
Team Leader can add or Edit Insights data (including setting dates as 'On Leave' or 'Non-Working Day') for up to 31 days in the past, including their own data.
The advanced search feature gives you a flexible way to view the work items in your business area by allowing you to specify multiple different combinations of search criteria, letting you view your work item data precisely how you want to.
You can access the ‘Advanced Search’ tab from the Nav section. When you hover over the 'Advanced Search' option here, you'll also see a list of your (if you have any), sorted in alphabetical order. You can easily created Saved Views from the Advanced Search feature so you don't have to enter your search criteria each time.
Note: Access to this Export feature is not switched on for standard Team Member and Team Leader Roles. To give users access to this feature, a must be created via the User Management section of Builder, with the 'Can Export Advanced Search views to Excel' option switched on in the 'Advanced Search' feature access section.
To use the Advanced Search feature, enter your search criteria by setting its Field, Condition (e.g. Equals, Greater Than etc.), and Value against which to evaluate the Condition.
The table below gives more detailed information about the standard fields available in the system.
You can add as many additional sets of conditions as you wish by clicking on the green plus icon.
Once you have entered your search conditions, click Search to reveal your search results. Your total number of search results will be shown at the top of the grid.
As with your Work Inbox and Owned work grids, you can choose which data columns you wish to see or hide in your search results grid by clicking on the Cog icon above the Search Results grid.
A ‘Display and Columns Settings’ popup will appear, allowing you to select which data columns you would like your search results to display.
Note: These custom data column preferences will stay the same when you do multiple searches, and when you next log back in.
You are also able to Group and Order your search results by selecting your Group By and Order By preferences from their respective dropdown lists.
Note: Only a single grouping criteria can be specified, and results will be loaded when you click on and expand an individual group.
You can also save your Advanced Searches as views which allows you to call them up again whenever you want. There is no limit to the number of views that you can save.
You can access your Saved Views by clicking on the Saved Views link.
Here you can search for a specific Saved View and rename and delete your Saved Views.
You can copy the name of your Saved View by clicking on the copy button on the tab:
You can export your views data from your Advances Searches into Excel. Watch this video to find out more:
To export your views data into an Excel spreadsheet, enter your search criteria in the Advanced Search page and then click to 'Switch to Export'.
This will show you a list of all of your previously exported files, as well as when they were downloaded, the size of the file, the total number of rows in the file, when the file export was requested, when the export began and when it was completed.
Before you export your search, you can edit the name of the file it will be exported as.
You can also adjust which columns you would like to view in your excel export by clicking on 'Select columns'. The columns selected in your search will be automatically selected, but you can adjust your selection here too.
Then click to 'Export'.
Your file will appear as a new row in the Exported Files section with a 'queued' icon next to it. Click to refresh the grid.
Once refreshed, the icon will change to a green single tick to show that the export is complete.
If there has been an error in exporting the file, a red warning icon will appear next to it.
You can download the file by clicking on the file name.
Once it has been downloaded, the icon will change to a green double tick to show that it has been downloaded.
The time and date that it was downloaded will then appear in the 'Downloaded On' column.
The data from your Advanced Search will have been exported into a .xlsx file, including the column titles selected.
Please note that in this initial release, column titles will only appear in English. They will be localized in a future release.
Additionally, please note that you can export up to a maximum of one million rows.
Column names in the exported file are different to the names that are displayed in the UI in the Advanced Search page.
You can copy and paste information from the Advanced Search grid into an Excel spreadsheet by selecting the information you want to copy and using Ctrl C and Ctrl V. The information that is copied and pasted includes any applied filters. The column titles will automatically be copied and pasted as well.
You are also able to to copy and paste all of the information from the Views grid by using Ctrl-A.
Note: only information that has loaded in the Advanced Search grid will be copied across.
Report detailing User Availability Insights data of how their work time is being spent.
As part of the Insights feature, a standard report is available that summarizes you or your team's availability data. It shows:
Planned leave data
Non-working days
Trend of duration of activities
Overall sentiment
Sentiment trend
More information about these visuals can be seen in the table below:
The Team View Report contains the following available data sets:
The User Insights report provides information about a team such as when they are due to go on leave and how they are feeling. This allows team leaders to take prompt action and make adjustments to cover any team absences or drops in team morale.
Access to and the ability to edit the User Insights is controlled by permissions in user roles, in the same way as all other reports within Enate. If users do not have the right permissions enabled, they will not be able to access or edit the report.
Here are some of the type of information which can be found within the report
Here are some of the type of information which can be found within the report
Optimize resource management by exploring your team's leave dynamics.
Strategically plan downtime using public holidays and breaks for work scheduling.
Understand team productivity through efficiency analysis and time allocation metrics.
Enhance performance by assessing team morale and fostering a positive work environment.
Cultivate consistent success with daily mood assessments, promoting productivity and positivity.
See below for a complete list of all the available data fields that can be used within the User Insights report:
Sent Items shows you all of the emails from your business area's work items that have been sent out.
You can see a preview list of all the emails that have been sent out, with the most recent at the top, showing who the email was sent to, when it was sent, the subject of the email, a preview of the first line of the email body and which work item the email relates to. You will also be able to see if the email has any attachments and if the email was sent with high importance.
You can adjust the size of the email preview panel to suit your needs.
When you click on an email, you will be able to see the full email in the right-hand side of the screen. You can see the subject of the email, who it was sent from, who it was sent to, any CC recipients, a link to the work item that the email relates to, the due date of the work item and the full content of the email.
You can also expand the email to full-screen mode, where the preview pane is hidden.
You can switch between viewing 'My Emails' which are the emails that you have sent and 'My Team Emails' which will show you the emails that members of your team have sent.
You can also reply, reply all, or forward a sent email. When you click on one of these options, the system will open a new tab displaying the work item in question and will take you to the email editor screen to start composing your email.
You can filter your sent emails by Customer, Contract, Service, Process, Queue, who the email was sent to, date range, the status of the work item that the email relates to, whether or not the email has attachments, and whether or not the email was system-generated.
Note that when filtering by date you can only filter for a maximum timespan of 90 days.
If you have access to the 'My Team Emails' view you'll also be able to filter by assigned user and by who the email was sent by.
Further options are also available from the ellipses next to the reply links. These will allow you to go directly to the work item that the email relates to (opening in a new tab), and to print the email directly.
You also have the option to download the underlying .eml file.
Please note: If the email you are attempting to download contains an attachment file which has been explicitly manually deleted by a user (for e.g. reasons of data sensitivity), the .eml download option will be disabled for that email - the system will display a message explaining the reason for this disabling when download icon is clicked.
To make your email work more flexible we've added the ability to save your emails as drafts if you're not quite ready to send them. Now when you are writing an email in a work item, you can choose to save the email as a draft and come back to it later.
When you are writing an email in a work item, you can choose to save the email as a draft and come back to it later. Drafts will be saved for a maximum of 90 days.
Note that you cannot save an email as a draft that exceeds the size set in Builder - .
If you have the Drafts filter in the comms/timeline tab switched on (note that this will be switched on automatically by default upon upgrade), you will see any saved draft emails for that work item in the comms/timeline.
You'll see who created the draft and when and the first few lines of the email.
If you click to expand the view, you'll also see the email address that the draft will be sent from, the address it will be sent to, any CC or BCC email addresses, the subject of the email, any attachments and the full email content if these have been added when the draft was saved.
You can edit a draft email from the timeline by clicking 'Update Draft'. This will open up the email editor where you can edit your draft. Note that you can only edit or delete a draft email from the work item it belongs to.
You also have the options to delete the draft, to open the email in a pop-out window or to print it.
Multiple users can work on the same draft, just not at the same time. A single work item can have multiple draft emails. These can all be seen and edited from the work item's comms/timeline.
When a draft already exists for a work item, the system will alert you to this when you start writing a new email so you can choose whether you want to continue writing your new email or whether you would like to edit the draft email instead.
If a work item has a draft email and you merge or convert a Ticket to a Case, you will be able to see the draft email in the comms/timeline or all work items in the related group as long as the 'Drafts' filter and the 'Include Related Work Items' filter are switched on.
The draft email will show in the timeline with the reference number of the work item it belongs to.
Note that draft emails will not be copied across when copying communications to a new linked work item, even when the 'Copy communications' option is enabled.
An attachment icon in the draft email comms/timeline entry shows you if any files have been attached to the draft email.
Clicking to expand the comms/timeline view will show you the name of the attachment and give you the option to download it.
Additionally, any files attached to draft emails will show in the files tab and be marked with a draft icon. You can view, download or delete files attached to draft emails from here. Note that you cannot add notes or tags to files attached to draft emails.
You can schedule the date and time of when an email will be sent by selecting the Schedule Send option.
The scheduled email will appear in the Comms and Timeline tabs, along with who scheduled it and when it has been scheduled for. If the email has been scheduled to send more than 2 minutes later, a 'Send Now' and 'Cancel' button will appear to let you send the scheduled email straight away if you have changed your mind or to cancel sending the scheduled email altogether.
You can also select Fields based on any , excluding custom data tables.
If an email has any , you can see the name of the attachment, its size and the option to download it. If the email has multiple attachments, you have the additional options of downloading all of the attachments or downloading them all as a ZIP file.
Note that you cannot schedule an email that exceeds the size set in Builder - . However, validation of the email size occurs as part of saving the email, not at the sent time. So if a 25MB email has been scheduled and then the maximum email size gets reduced in Builder to 10MB, the scheduled email will still be sent as it conformed to the size allowance configured when it was scheduled.
Action Type
This lets you search for Actions of a particular type.
Begins With
Equals
Select from: Manual, Manual with Peer Review, Send Email, Send Email and Wait, Start Case, ABBYY OCR, Wait for Sub Cases to Complete, and Trigger External API.
Assigned To
This lets you search for work items based on who they are assigned to or whether or not they have been assigned to someone.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a worker
Context
This lets you search for work items with a specific context i.e. customer, contract, service
Equals
Select a customer, contract and service from the dropdown
Due
This lets you search for work items based on when they are due.
Equals
Is Empty
Is Not Empty
Not Equal
Greater Than
Greater Than Or Equals To
Less Than
Less Than Or Equals To
Between
Select a date
End Date
This lets you search work items based on when they have been completed i.e. they have been marked as Closed.
Equals
Is Empty
Is Not Empty
Not Equal
Greater Than
Greater Than Or Equals To
Less Than
Less Than Or Equals To
Between
Select a date
Has Been Reopened
This lets you search for work items that have been reopened from a Resolved state.
Equals
Select from Yes or No
Initial Request On
If a further work item has been created from an original request (when a Sub Case is created, when a Ticket is converted into a Case, when a Case or Action gets reworked, when an Action is created via the 'Start Action' option or when a new linked work item is created), this due date method captures the start date of the original request, allowing you to capture the entire length of time it has taken to complete a request, as opposed to just the length of time an individual work item has been being worked on.
Equals
Is Empty
Is Not Empty
Not Equal
Greater Than
Greater Than Or Equals To
Less Than
Less Than Or Equals To
Between
Select a date
Is Overdue
This lets you search for work items that are overdue.
Equals
Select from Yes or No
Last Reopened By
This lets you search for who last reopened a work item from a Resolved state.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a worker
Last Reopened On
This lets you search for the last time when a work item was reopened from a Resolved state.
Equals
Is Empty
Is Not Empty
Not Equal
Greater Than
Greater Than Or Equals To
Less Than
Less Than Or Equals To
Between
Select a date
Last Updated By
This lets you search for work items based on the human/digital worker who last updated the work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a worker
Last Updated On
This lets you search for work items based on the datetime the item was last updated by a human/digital worker.
Equals
Is Empty
Is Not Empty
Not Equal
Greater Than
Greater Than Or Equals To
Less Than
Less Than Or Equals To
Between
Select a date
Original Requester Email
This lets you search for work items based on the email address of the original requester of a work item, i.e. the person who initially raised the request.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a contact
Original Requester Name
This lets you search for work items based on the name of the original requester of a work item, i.e. the person who initially raised the request.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a contact
Owned By
This lets you search for work items based on the owner of the item i.e. the person who currently has ultimate responsibility for the work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a worker
Overdue By Days
This shows how many days or working days (depending upon the due date configuration) a work item is overdue by.
Equals
Is Empty
Is Not Empty
Not Equal
Greater Than
Greater Than Or Equals To
Less Than
Less Than Or Equals To
Between
Enter the desired number of days.
Parent Process Name
This lets you search for work items based on their parent process e.g. searching for the name of a Case will return the Actions of the Case in your search.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a parent process
Parent Reference
The reference number of the work item which started this one, e.g. parent Case.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter a reference number
Primary Contact Email
This lets you search for work items based on the email address of the primary contact of a work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a contact
Primary Contact Name
This lets you search for work items based on the name of the primary contact of a work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a contact
Queue
The work Queue which Cases/Tickets/Actions get sent to based on their routing rule.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a Queue
Reference
The unique reference number e.g. 101342-T.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter a reference number
Requester Email
This lets you search for work items based on the email address of the requester of a work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a contact
Requester Name
This lets you search for work items based on the name of the requester of a work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a contact
Running
This lets you search for work items based on their status. Running work items are work items in a state or To Do, In Progress, Waiting
Equals
Select Yes if you want to search for work items that are in a state of To Do, In Progress or Waiting.
Select No if you want to search for work items that are not in a state of To Do, In Progress or Waiting.
Schedule
This lets you search for Cases based on their schedule
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, select a schedule from the dropdown
Schedule Period
This lets you search for Cases based on their schedule period.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter a schedule period
Schedule Structure
This lets you search for Cases based on their schedule structure.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, select a schedule structure from the dropdown
Schedule Year
This lets you search for Cases based on their schedule year.
Equals
Is Empty
Is Not Empty
Not Equal
Greater Than
Greater Than Or Equals To
Less Than
Less Than Or Equals To
Between
If the condition you have selected is Equals, Not Equal, Greater Than,
Greater Than Or Equals To, Less Than or Less Than Or Equals To then enter a year.
If the condition you have selected is Between, enter the two different years that you want to search between.
Service Line
This lets you search for work items based on the overall area of the business the work item runs under, e.g. ‘Payroll’.
Begins With
Equals
Is Empty
Is Not Empty
Select a service line from the dropdown
Service Provider
This lets you search for work items based on the company delivering service for the work item, usually your company.
Begins With
Equals
Is Empty
Is Not Empty
Select a service provider from the dropdown
Started
This lets you search for work items based on when the when the work item was started.
Equals
Is Empty
Is Not Empty
Not Equal
Greater Than
Greater Than Or Equals To
Less Than
Less Than Or Equals To
Between
Select a date
Started By
This lets you search for work items based on who started the work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a worker
Started By Method
This lets you search for work items based on how they got started, e.g. incoming email, automatic schedule, manually.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, select from: Workflow, Manual, Self Service, Robotics, Email, Ticket, Bulk Upload, Schedule, Linked Work Item
Status
This lets you search for work items based on their current status.
Equals
Not Equal
Draft
To Do
In Progress
Waiting
Resolved
Closed
Status Reason
This lets you search for work items based on their current status reason.
Equals
Not Equal
Action Unable to Complete
All relevant Actions completed
All Split Tickets Completed
Blocked By Business Rule
Cancelled
Completed
Failed
Feedback Received
Feedback Window Passed
File not found during IDP extraction
Marketplace not configured
New Information Received
Newly Created
One or more Actions not completed successfully
Previous Step Completed
Reopened By Resource
Rework
Schedule Date and Time Reached
Sub Case Completed
Sub Case Cancelled
Sub Case Not Yet Started
Timeout
Unknown
Updated by Enate
Updated by Enate (as End Case Action reached)
Updated By Integration
Updated By Resource
Updated By Support Team
Waiting for Human Validation
Waiting for Marketplace
Subject Email
This lets you search for work items based on the email address of the subject of a work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a contact
Subject Name
This lets you search for work items based on the name of the subject of a work item.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter the name of a contact
Ticket Category Level 1
This lets you search for Tickets based on their Ticket category level 1 i.e. the highest level of Ticket categorisation e.g. ‘Healthcare Request’.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter a Ticket Category Level 1 value
Ticket Category Level 2
This lets you search for Tickets based on their Ticket category level 2 i.e. the next level of Ticket categorisation e.g. ‘International Travel Coverage’.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter a Ticket Category Level 2 value
Ticket Category Level 3
This lets you search for Tickets based on their Ticket category level 3 i.e. the most detailed-level of Ticket categorisation e.g. ‘Eligibility Query’.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter a Ticket Category Level 3 value
Title
This lets you search for work items based on their title - a brief text description of the work item, often the subject of the original email.
Begins With
Equals
Is Empty
Is Not Empty
If the condition you have selected is Begins With or Equals, enter a title of the work item
Wait Type
This lets you search for work items based on their wait type i.e. if they have a wait type of 'Waiting for more information', etc.
Equals
Is Empty
Is Not Empty
Not Equal
External System
Pause
Related Work Items
Wait for more information
Wait Until
Work Item Type
This lets you search for work items based on their work item type i.e. if they're a Ticket, Case or Action.
Equals
Select Case, Ticket or Action
Leaves
Shows the Daily/Weekly/Monthly trend of planned leave count by the user. If the logged in user is a team manager then it will also show leave count for their team members.
1. Count all rows where Work Day Type = "Leave" 2. Filter the rows for the "logged in user" and any user whose manager is "logged in user"
Date, User name
Non-working days
Shows the Daily/Weekly/Monthly trend of non working days count for the user. If the logged in user is a team manager then it will also show non working days count for their team members.
1. Count all rows where Work Day Type = "WeekOff" 2. Filter the rows for the "logged in user" and any user whose manager is "logged in user"
Date, User name
Avg. duration trend (in hrs)
Shows the average Daily/Weekly/Monthly trend of various durations entered by the user. If the logged in user is a team manager then it will also show average durations for their team members.
1. Calculate the average of DurationSpentInEnate, AdHocDuration, DowntimeDuration, FeedbackDuration, MeetingDuration, DurationSpentOutsideEnate, TrainingDuration by excluding any WeekOff and leaves 2. DurationSpentInEnate is calculated as total duration recorded in packet activities by each user on each day where activity type in (2,3) 3. Filter the rows for the "logged in user" and any user whose manager is "logged in user"
Date, User name
Overall sentiment
Shows the overall percentage share of each sentiment opted by the user. If the logged in user is a team manager then it will also show the percentage share of sentiments for their team members.
1. Calculate the count of sentiments for each sentiment type 2. Filter the rows for the "logged in user" and any user whose manager is "logged in user"
Date, User name
Sentiment trend
Shows the Daily/Weekly/Monthly trend of percentage share of sentiment entered by the user. If the logged in user is a team manager then it will also show the percentage share of sentiments for their team members.
1. Calculate the count of sentiments for each sentiment type 2. Filter the rows for the "logged in user" and any user whose manager is "logged in user"
Date, User name
Date
Date
Day of the week in DDMM Format
Date
Week
Week of the year
Date
Month
Month of the Year in MMYY format
Date
Year
Calendar Year
Sentiment type
Sentiment
Sentiments options (Excellent, Very Good, Good, Bad, Worse). It will be none if not entered.
Insights
Avg. other hours
Avg. hours spent on ad hoc tasks
Insights
Avg. contractual break hours
Avg. hours spent on breaks
Insights
Avg. idle hours
Avg. hours spent on system downtime
Insights
Avg. feedback/1-2-1 hours
Avg. hours spent on feedback sessions
Insights
Avg. work performed within Enate
Avg. hours spent in Enate (on cases, actions or tickets)
Insights
Avg. work performed outside Enate
Avg. value added hours spent outside the Enate
Insights
Avg. meeting hours
Avg. hours spent on meetings
Insights
Avg. training hours
Avg. hours spent on training sessions
Insights
Avg. working hours
Avg. working hours
Insights
Other hours
Total hours spent on adhoc tasks
Insights
Contractual break hours
Total hours spent on breaks
Insights
Downtime hours
Total hours spent on system downtime
Insights
Feedback/1-2-1 hours
Total hours spent on feedback sessions
Insights
Work performed within Enate
Total hours spent in Enate (specifically on Cases, Actions or Tickets)
Insights
Work performed outside Enate
Total value-added hours spent outside the Enate
Insights
Leaves count
Planned leave count for the user(s)
Insights
Meeting hours
Total hours spent on meetings
Insights
Non-working days count
Non-working day count for the user(s) includes holidays weekends etc
Insights
Sentiment count
Count of sentiments entered by user(s) for a particular day
Insights
Training hours
Total hours spent on training sessions
Insights
Working hours
Total working hours
Insights
Comment
Comments added by user for the sentiment chosen
Insights
Insights date
Date when the durations/sentiments captured from the user
Users
Email address
Email address of the user(s)
Users
User name
Full name of the user(s)
WorkDay type
Work day
Type of the day (Working, Non-working Day, Leave). It will be none if nothing is chosen by the user.
Date
Date
Day of the week in DDMM Format
Date
Week
Week of the year
Date
Month
Month of the Year in MMYY format
Date
Year
Calendar Year
Sentiment type
Sentiment
Sentiments options (Excellent, Very Good, Good, Bad, Worse). It will be none if not entered.
Insights
Avg. other hours
Avg. hours spent on ad hoc tasks
Insights
Avg. contractual break hours
Avg. hours spent on breaks
Insights
Avg. idle hours
Avg. hours spent on system downtime
Insights
Avg. feedback/1-2-1 hours
Avg. hours spent on feedback sessions
Insights
Avg. work performed within Enate
Avg. hours spent in Enate (on cases, actions or tickets)
Insights
Avg. work performed outside Enate
Avg. value added hours spent outside the Enate
Insights
Avg. meeting hours
Avg. hours spent on meetings
Insights
Avg. training hours
Avg. hours spent on training sessions
Insights
Avg. working hours
Avg. working hours
Insights
Other hours
Total hours spent on adhoc tasks
Insights
Contractual break hours
Total hours spent on breaks
Insights
Idle hours
Total hours spent on system downtime
Insights
Feedback/1-2-1 hours
Total hours spent on feedback sessions
Insights
Work performed within Enate
Total hours spent in Enate (specifically on Cases, Actions or Tickets)
Insights
Work performed outside Enate
Total value-added hours spent outside the Enate
Insights
Leaves count
Planned leave count for the user(s)
Insights
Meeting hours
Total hours spent on meetings
Insights
Non-working days count
Non-working day count for the user(s) includes holidays weekends etc
Insights
Sentiment count
Count of sentiments entered by user(s) for a particular day
Insights
Training hours
Total hours spent on training sessions
Insights
Working hours
Total working hours
Insights
Comment
Comments added by user for the sentiment chosen
Insights
Insights date
Date when the durations/sentiments captured from the user
Users
Email address
Email address of the user(s)
Users
User name
Full name of the user(s)
WorkDay type
Work day
Type of the day (Working, Non-working Day, Leave). It will be none if nothing is chosen by the user.
There are three types of Work Item in Enate:
Tickets – Used for modelling single-part activities, e.g. queries. Tickets are standalone and are not part of a business process. Can be promoted to become a specific type of Case.
Cases – Used for modelling multi-part activities (i.e. business processes).
Actions – the constituent parts of a Case, i.e. a Case is made up of a flow of Actions. Contains a set of instructions, often a checklist of activities to track progress within the Action. These can be manual (can be carried out by humans and bots) or automatic Actions, e.g. auto sending an email.
Details on screen resolutions supported by Enate
The minimum screen resolution supported by Enate at 100% DPI is: 1366 x 768. This means that resolutions of 1280x1024 and below are NOT supported.
Higher resolutions screens may run with DPI settings in excess of 100%. With this in mind, the list below shows the minimum 'screen resolution & DPI' combinations supported by Enate. Industry definitions for these screen resolutions are also provided here to help clarification:
1366 x 768 High Definition (HD) – Supported at 100% DPI Only
1600 x 900 High Definition Plus (HD+) – Supported at 100% DPI Only
1920 x 1080 Full High Definition (FHD) – Supported up to 125% DPI
1920 x 1200 Wide Ultra Extended Graphics Array (WUXGA) – Supported up to 125% DPI
2560 x 1440 Quad High Definition (QHD) – Supported up to 150% DPI
3440 x 1440 Wide Quad High Definition (WQHD) – Supported up to 150% DPI
3840 x 2160 4K or Ultra High Definition (UHD) – Supported up to 200% DPI
Particularly when running on minimum supported resolution, Enate always recommends users to run Enate in Full-screen mode (access this via F11 key in browser) to give maximum screen real-estate for display. If you have additional toolbars installed in the browsers above the 'default' system browsers (e.g. browser add-ins), this can significantly reduce available screen space and may go below minimum supported screen dimensions.
As part of managing Tickets, Cases & Actions in your workflows in Enate, the system will regularly evaluate who the work is assigned to, who is set as the Owner, and which Queue the work item is linked to. There are detailed sets of rules which are followed, in order, when determining this.
Before looking at these detailed sets of rules, it’s important to understand the higher-level pattern of how such work item allocations are evaluated, and indeed when. The way this works is as follows:
First we determine WHEN such re-evaluations occur – essentially this happens when anything changes in the 'Status’ card of a Work item.
When the system determines it needs to do such an evaluation, we initially use the work item’s status/situation to determine which of the Assignee, Owner and Queue values need to be Set, and which need to be Cleared completely.
For those which require setting:
a. If a Queue is to be set, it's simple - just select the Queue referenced in the Allocation rule (there are only two types of Queue allocation rule to follow).
b. For Assignee and Owner, there's more detail - we have to run through a series of rules, in order, for these - stopping when the rule is met and a valid* target is selected.
*Validity check - As part of the Assignee / Owner allocation rule check, we have to determine if the target is valid (there are a number of validity check rules which it must pass). If not, we continue through the rules in part 3 until a valid target is found.
Now that the higher-level pattern at play has been described, we can go look at each set of rules which are run through for sections 1-3 above, and for the target validity checks.
The system will re-evaluate the Assigned User, Owner and Queue whenever the information in the Status card changes, specifically:
the Status changes
the Wait Type changes
the Scheduled Follow Up On date changes
the Wait for More Information Until date changes
the Waiting For option changes (for Cases only)
the Ticket Context changes
the Ticket Category changes
the In Peer Review status changes
New Information is received on the work item
A Case encounters a Problem
When the system determines it needs to do such an evaluation, we initially use the work item’s STATE to determine which of the Assignee, Owner and Queue values need to be Set, and which need to be Cleared completely. You can see this information in the table below:
Work Item Status/Situation
Assignee
Owner
Queue
Closed
Clear value
Clear value
Clear value
Draft
Set a value
Clear value
Clear value
New Information Received
Set a value
Clear value
Set a value
Needs Attention (only relevant to a Case)
Set a value
Clear value
Set a value
To Do or In Progress for an Action or Ticket
Set a value
Clear value
Set a value
To Do or In Progress for a Case
Clear value
Set a value
Clear value
Resolved or Waiting
Clear value
Set a value
Clear value
Queues - If a Queue is to be set, it's simple – the configured Queue Allocation Method is run.
Assignee and Owner - If an Assignee or Owner is to be set, there's more detail. We have to run through a series of rules, in order, stopping when the rule is met and a valid target is selected.
Before the list of rules is run, there is one higher check: if an Assignee/Owner is currently set, don't change the Assignee/Owner unless the Ticket Category has changed.
Otherwise, run the following rules, in order, stopping when you a valid target is identified:
If the ‘Keep with me' option has been set on a work item, the Assignee/Owner is set as the user who has selected ‘Keep with me’. If not or the resulting user is not valid, then
If the Owner user is not blank, then set Assignee to that value also. If not or the resulting user is not valid, then
If the work item is a Ticket and the Ticket Category has changed and either the Wait Type has changed or the status is Resolved then the Assignee/Owner is set as the user currently updating the Ticket. If not then
If the work item is not a Ticket OR it is a Ticket (where the Ticket Category hasn't changed AND we have more than 2 status history rows - i.e. it is not in its first non-draft state), then:
Set Assignee and Owner to the last user/robot to update work item. If none or the resulting user is not valid, then
Set Assignee/Owner as (any) previously assigned to user/robot in descending order of when it was assigned to them. If none or the resulting user is not valid, then
If Action started by Workflow (i.e. not manual ad-hoc), then set the Assignee/Owner as the last user/robot to work on the same previously completed Action in the Case (or Peer Review the Action if in peer review). If none or the resulting user is not valid, then
Run the Allocation Rule for this work item:
If the primary push allocation is configured to a specific user, set Assignee/Owner to that user. If none or the resulting user is not valid, then
If the secondary push allocation is configured to a specific user, set Assignee/Owner to that user. If none or the resulting user is not valid, then
If Primary push allocation configured to Position, from the users that occupy this position set the Assignee/Owner as the user with the fewest work items in their inbox. If none or the resulting user is not valid, then
If Secondary push allocation configured to Position from the users that occupy this position set the Assignee/Owner as the user with the fewest work items in their inbox. If none or the resulting user is not valid, then
If the work item is a Case, set Assignee/Owner as the user/robot that started that Case.
As part of the Assignee / Owner allocation rule check, we have to determine if the target is valid. To be valid, there are a number of validity check rules which it must pass. If not, we continue through the rules of setting an Assignee/Owner until a valid target is found. The validity checks that are run through are as follows:
If the User/Robot is not allowed to work on work items of this type (i.e. Live/Testing) then block
If the User/Robot is retired then block
If the User does not have permission then block (no permission check for Robots)
If the Robot is suspended then block
If the Robot has performed Get More Work more than 3 times for this work item then block
If the user selected is a Robot and the work item is an Action that is in the Peer Review stage then block (Robots cannot perform Peer Reviews)
If the user selected is a Robot and the work item is an Action and no Robot Farm is configured for the Action then block
If the user selected is a Robot and the work item is an Action and the Robot is not a member of the Robot Farm configured for the Action then block
If the user selected is a Robot and the work item is a Case then block (Robots cannot be assigned Cases)
If the work item is a manual with Peer Review Action that is on the Peer Review stage and the User performed 1 or more updates while it was on the Doing stage then block (users can’t peer review their own work)
If the work item is a manual with Peer Review Action that is on the Doing stage and the User performed 1 or more updates while it was on the Peer Review stage then block (users can’t be asked to do work if they have previously peer reviewed it)
The optional 'Insights' feature lets you capture key information regarding the availability of agent users. This can help Team leads and Operations Managers to better schedule work by giving them a view of where time is being spent day-to-day.
If Insights is switched on in your system (see Enabling Insights), when users log into Work Manager for the first time each day, they'll be met with a popup after a short while, asking them to confirm:
Their working hours for the day, e.g. 8 hrs (this may default in a value from their working calendar if one is set for them, or from the previous day's entered value.
a rundown of any non-core activities they may have planned for the day, for example a training session, or 1-2-1 meetings, plus their expected working hours for the day.
optionally, they can note down how they're currently feeling too.
The purpose of this popup is to allow agents to note down the time when they will be busy on activities such as meetings or 1-to-1 feedback sesssions.
This data can then be assessed by Team Leader and Operations Managers to help form a clearer picture of how much time is available for actively working on Cases, Ticket and & Actions versus other indirect activities such as attending Meetings or Training courses or similar. As part of this, obviously the overall number of working hours available for a given day for that user needs to be captured, as well as things like expected break totals.
Over time, Team Leaders will be able to form a picture of the overall amount of time available for these different activities, and spot trends to help them predict capacity going forward. There's also the ability for some short term forward planning if we have visibility of agents' expected time available over the next few days.
The Insights feature can be enabled / disabled by Admin This feature can be enabled from the General Settings section of Builder.
The Insights Feature has the following main sections:
In the Main Insights Page, and the Insights Report, you will only see your own availability insight data. If you have people that report to you in Enate, you'll also be able to see the data from your team members, depending on the level of feature access you have set in your user role, specifically:
Users with the 'Set up Team & Queues' feature access option - set in the User Roles section of Builder - will be able to see the information entered by themselves and their team (i.e. the people who they manage).
Users without the 'Set up Team & Queues' feature access option will only be able to see their own data.
Enate Work Manager supports the following languages:
English (British)
English (US)
French
German
Romanian
Hungarian
Polish
Spanish
Portuguese Brazilian
Russian
The Operations environment for end users to deliver the service fully supports these languages and each user will be allowed to choose their preferred language along with date-time pattern in their user profile settings.
To set a preferred language, select a language from the Language dropdown list in User Settings.
The display of labels will appear in the logged-on user’s preferred language - this is achieved by adding a ‘language package’ into Enate. Each language package will have mapping for user-specific language like Portuguese, for example, ‘Queue’ will be ‘Fila’ and ‘Action’ will be ‘Açao’ in Portuguese.
Here is the list of UI elements which will be available in the logged-on user’s preferred language:
Item
Details
Home Page
RAG filters
My Team
Bot Farm
Queue
Chart
Grids and column settings
Same behaviour in Inbox page as well.
Quick Find
People, Comms and work items search
Queue Page
Navigation Links
Link to Builder, Queue Page or recent accessed work items etc.
User Profile Page
Here user can also change preferred language along with datetime pattern.
Call Handling Page
This page shows all communications and work items related to individual users
Work item UI
Labels and Button like Category picker, state etc.
Note – Real names such as customer names and usernames will be remained in the original language, as entered by the configurers in Builder.
Enate fully supports a User’s preferred language in Work Manager display and UI elements including labels, links and buttons, however anything added by you will stay in same language you originally entered it in and will not be auto-translated into any other language when being viewed by other users with a different preferred language.
For example, if a Brazilian user adds a note to a Case in Portuguese, Enate will then save the note in Portuguese in the database and will only ever show the note in Portuguese.
Here is full list of items which will be driven by user input and which WILL NOT be auto translated by the product:
Item
Detail
Case
Notes
Emails
Case - short description/title
Override Action instruction o new Action launched by end user
Action
Notes
Emails
Checklist comments
Action State- 'Unable to complete' reason text
Override Action Instruction of new Action launched by end user
Action Peer Review note entered by reviewer
Ticket
Title and description of new child Tickets
Name of new Action launched by user
Name of new Case launched by user
Contact
Details about contact like address.
Files
File name and note about file
Defect
Defect description
Reassignment Notes
Text entered by user while reassigning a piece of work to another teammate.
The initial releases of multilingual functionality will not support configurers defining multiple languages when creating Custom Data and Smart Cards in Builder. Multiple cards and data items would be required for this.
The initial releases of multilingual functionality will not support notifications in languages other than English.
To ensure that you are able to carry out your work in Enate spelling error-free, you can enable spell check in your web browser to help check your spelling as you go about your tasks.
Below are the steps to activate spell checker in three of the most popular browsers: Google Chrome, Mozilla Firefox and Microsoft Edge.
Open Chrome Settings:
Click on the three vertical dots in the upper right corner.
Select Settings.
Access Language Settings:
In the settings menu, type "language" in the search box.
Click on Languages.
Enable Spell Check:
Under the Spell check section, choose between Basic spell check or Enhanced spell check.
You can also add new languages if necessary.
Open Firefox Menu:
Click on the three horizontal lines in the upper right corner.
Select Settings.
Navigate to Language Settings:
In the left sidebar, select General.
Scroll down to the Language and Appearance section.
Turn on Spell Check:
Check the box next to Check my spelling as I type.
Open Edge Settings:
Click on the three horizontal dots in the top-right corner.
Select Settings.
Find Language Options:
Scroll down and click on Languages.
Enable Spell Check:
Toggle on the option for Enable spell check for your preferred languages.
Information about terms which are auto-removed from various searches that users can perform in the system
As part of standard underlying features in Enate to optimise searches which users perform, certain commonly used terms are removed from searches if they've been manually entered. This is in order to ensure timely response for search results, plus avoid the returning of vast volumes of qualifying results which would obscure the desired results from the users. One of the approaches used for this is the use of 'Stop Lists'.
A stop list is a list of standard common words such as ‘and’ ‘the’, ‘me’ etc., which are ignored from searches that would otherwise return too many results.
Below is a comprehensive list of all of the words in the stop list that ALL searches within Enate will ignore - this not only includes searches in Quickfind, but also searches which are performed for users, searches for emails, searches for Work Items e.g. for Tickets when merging Tickets etc. If you enter any of these terms, they will be auto-ignored as terms to return search results for.
Multiple Stop Lists are supported for various user languages.
Note: When searching for Users and Emails, the English (British) stop list is always used. For work items (Title, Customer Name, Contract Name, Service Name, Case/Ticket Name, etc.) we use the language of the logged-on user to find the stop list. Additionally, please note that Hungarian is not directly supported by SQL, so the stop list applied for searches for Hungarian users is also the English stop list.
Specific further characters are set to be ignored when performing searches in Quickfind, e.g. “*”, “?”, “@” etc. This will mean for example that when searching for customer.com in Quickfind, the words 'customer' and 'com' would be searched for. As such, it’s recommended to place such word combinations in quotes to search for them as a specific phrase - i.e. searching for “customer.com” will likely bring back the results you are looking for.
Below is a comprehensive list of all of the characters that searches in Quickfind will ignore:
How to use Enate's Test mode to check your config changes before setting them live.
If your user account is set to allow you to access test data, you can switch your Work Manager environment over to ‘Test Mode’. This link is available in the user dropdown on the right of the header bar.
Once you are running in test mode you will only see test data; allowing you to create and run test work items through test versions of processes to verify them before setting live, all without affecting live production data.
As a visual reminder, the header bar is set to red when you are in Test mode.
Test mode functionality allows you to set a different manager for a Queue when running in Test mode vs. Live mode.
Example: Consider Manager 1 who has access to live mode and is responsible for managing two Queues, Funding and Master Case Queue.
In Test Mode, the same two Queues can be managed by another user who has Team Lead and Test Mode permission – see below example where Manager 2 has been set to be in charge of the Queues in Testing Mode.
It is possible to switch a robot so that it can run in test mode or live mode. Specifically, two new activities have been added to the activity libraries for UiPath, Automation Anywhere and BluePrism (and the standard APIs adjusted so this can be called generically) as follows
Set Live Mode
Set Test Mode
These Actions allow you to flip a robot between test and live states. Once a robot has been flipped into Test mode, subsequent activity calls which the robot might make, e.g. ‘Get more work’ and ‘Create Ticket/Case etc.’ take place within that context of Test mode, getting and creating only test work items. The robot should be switched back to Live mode once the process is set to live, so ensure it is then creating live work items.
Enate supports the creation of separate Contact records in Test Mode, i.e. any contact records you create in Test mode will be accessible only to Test Mode users (and contacts created in live mode will be accessible only to Live mode users). This helps to ensure that emails from test packets are not accidentally sent to production users, and vice versa.
This is where you are able to easily add, edit and delete email addresses to be blocked.
Disable auto-generated emails when creating a new Ticket from this address - the system will allow Tickets to be created for emails arriving from this address but will not send any auto-generated emails out to the address.
Disable auto-generated emails when creating a new Ticket/Case from this address - the system will allow Tickets and/or Cases to be created for emails arriving from this address but will not send any auto-generated emails out to the address.
Auto-reject emails from this address as spam - the system will allow Tickets to be created for emails arriving from this address but once created, the Ticket will be automatically moved to a state of Closed with a resolution method of 'Rejected as Spam'. As Cases do not have a 'Rejected' status, any email from a blocked address will be automatically moved to your 'Unhandled email' section of your email page, rather than creating any work item.
Files can be attached to an email in various ways.
1) You can attach files when composing an email by clicking on the attach files option at the foot of the email section.
Files that are already attached to the work item, and are therefore already in the files tab (including files attached to previous existing emails within the work item) will be available for selection from here. You can use the search function to search for specific files if there are many to choose from.
You can also search for files from your PC to attach from here by clicking on the ‘Browse This PC’ icon.
2) You can add links to an email by clicking on the attach links option at the foot of the email section. Links that have already been added to the work item (and are therefore already in the files tab).
3) You can drag and drop files from your desktop into the email section
4) Files which have been linked to a standard Canned Text will automatically attach to the email when the canned text is selected.
When emails are auto-generated and sent by the system, the email template used may be linked to one or more tags – the system will identify any files currently attached to the work item which have been tagged with this same value, and will auto-attach them to the email before sending.
You can view all the email attachments that have been added to the work item and other related/linked work items in the files tab.
You can see the name of the file, what type of file it is, its size and when and by who it was uploaded and the reference number of the work item it was uploaded to.
You can also see the tags and notes that have been added to the files.
You can download files from an email by opening the email you have received and clicking to download the file attached.
If multiple files have been attached, you have the option to download all the files individually or to download them as a zip file.
It is possible to download multiple attachments with a single click from mails in the comms and timeline section. Clicking on the ‘Download all’ icon will download all attachments present in that Comms / Timeline section item.
You can download individual files by clicking on the the option in the menu on the right.
You can download multiple files at once by selecting the files you wish to download and selecting the option at the top of the screen.
You can download multiple files in a zip file by selecting the files you wish to download and selecting the option at the top of the screen.
If your system has been set up to let you delete email attachments, you can delete attachments that originated from an email in the file card of a work item. This is useful when, for example, you are dealing with sensitive information in email attachments.
The deleted attachment will also be deleted from other related work items such as other Actions in a Case, Sub Cases, child and parent Tickets if a Ticket has been merged, child Cases and parent Tickets if a Ticket has been converted to a Case.
But note that if you delete an email attachment from a Ticket that has been split or is the child Ticket of a split, the deleted file will not be deleted from the other child Ticket(s) or the parent Ticket.
Note also that deleting an attachment from a linked work item will NOT delete the attachment from the work item(s) it is linked with.
Please also be aware that it is not possible to delete an email attachment from a work item that is Closed.
The attachment will be deleted from all parts of the system, so you won't be able to search for it in Quickfind, and it will not be available to attach to a new email relating to the work item.
Any further activity on the work item will not resurrect the deleted attachment and creating a new linked work item will not resurrect the deleted attachment.
You will be notified in the timeline when an email attachment has been deleted, along with the file name of the email attachment that was deleted, the subject of the email it was attached to, who deleted it and when it was deleted.
Enate's Notifications keep you up to date on what's happening with any Tickets, Actions and Cases you're interested in to keep you in the loop at all times. You've got lots of flexibility with how you receive notifications, in terms of which items you follow, what events you're notified about for them and how they're delivered to you.
You've got various options at your disposal:
Follow individual Work Items
Follow all Work in your Work Inbox
Follow all work in your Queues
You can choose to get notifications about a particular work item - just open it in Work Manager and click the 'Follow' option in the header bar.
While you're following a work item, you'll receive a notification whenever any of the events you have selected in your Notification Settings occur - things like changes in state, changes in its assignee, etc.. If you have chosen to also be notified by browser pop-up and /or email, you will receive copies of your notifications via those channels too.
Points to note:
You can follow a work item in any state except Draft and Closed.
You can only follow work items that you have permissions on.
You will never automatically be set to following an individual work item.
You can only follow an individual work item by manually clicking to follow it from its work item screen. The one exception to this rule is when you're following a Ticket and that Ticket is subsequently set to split. In that circumstance you will automatically be set to follow all the Tickets that the original was split into.
When you click to follow a work item, you will only be set to following that work item and not work items that are related to it e.g. other Actions in a Case, or any linked work items.
If you choose to follow an Action and that Action's parent Case gets reworked, you will not be notified when that Action automatically closes as part of the rework, and you will not automatically follow that Action when the new one is relaunched from the new Case. If you want to follow the Action again, you can select to do so manually.
You can 'Unfollow' a work item at any point by clicking 'Unfollow' from the work item screen.
You can only unfollow a work item by manually clicking to unfollow it or if the work item moves to a state of Closed. When a work item moves to Closed, all of the users who were following it will be set to unfollow.
You can choose which notifications you want to receive and how by going to your User Settings and clicking to view your Notification Settings.
In addition to choosing to follow an individual work item, you can also use the notifications settings page to specify more generally which notifications you want to automatically receive. There are two parts to this:
First, you specify which work items you want to receive, e.g. item's in your own Work Inbox.
Further to this, you specify which events about those work items you want to be notified about.
See below for details ..
You can choose to receive notifications for work items in your Work Inbox and/or for work items in your Queues.
My Work Inbox
You will receive notifications for work items that are in your work inbox i.e. work items that are assigned to you.
This is switched on by default for all users.
My Queues
You will receive notifications for work items that are in Queues that you are in and/or manage.
This option is switched on by default for Team Leaders.
In addition to this, you need to choose which events you want to be notified about for these Work Items.
The options are as follows:
New Information Received
A new email or Self Service Note has been received on the work item
Users subscribed to receive notifications for a work item in its related group to this (e.g. Case/Actions or the child/parent of a split Ticket) will also receive the notification.
Work Item Assigned to Me
Assigned user of a work item has changed to me
Only the person the work item is being assigned to will receive the notification.
New Work Item into Queue
Assigned Queue of a work item has changed to a Queue that I am in and/or manage
New File Added
A new file has been manually uploaded by an agent to the files tab of the work item
Users subscribed to receive notifications for a work item related to this (e.g. Case/Actions or the child/parent of a split Ticket) will also receive the notification.
Due Date 'At Risk' Reminder
Due date of the work item is deemed to be at risk. This is calculated by subtracting the expected time for the work item to take with an additional 30 minutes from the due date/time.
E.g. if the work item is due to be completed at 17.00 and the time expected to complete the work item is 1 hour, the Due Date 'At Risk' Reminder will be sent at 15.30.
Note that this notification will not be sent if:
the work item is in a state of Draft
the work item is in a state of In Progress and assigned to a user
the work item is in a state of Waiting AND its due date has been configured with the option 'Add Wait Time To Due Date'
Anyone subscribed to receive notifications for the parent of this work item (if there is one) will also receive this notification.
Work Item is Overdue
The due date of the work item has been missed and it is now overdue.
Anyone subscribed to receive notifications for the parent of this work item (if there is one) will also receive this notification.
Action Rejected
A robot has actively rejected an Action, or repeatedly failed to process it
Anyone subscribed to receive notifications for the parent Case of the Action will also receive this notification.
Case Needs Attention
A Case has encountered a problem and requires intervention before it can proceed.
Users subscribed to receive notifications for a work item Related to this (e.g. Case/Actions or the child/parent of a split Ticket) will also receive the notification. Note that the person who rejected the Action within the Case will not receive the notification.
Peer Review Changes
The peer review of an Action has been marked as 'Passed', 'Failed', or 'Unable to be Completed'.
Note that in order to receive this notification, users must:
be in the Queue that this Action belongs to (or manage it), AND
be subscribed to receive notifications about this Action (being subscribed to the Case is not enough), AND
have the setting to receive notifications from 'My Queues' switched on.
Additionally, the person who completed the peer review will not receive the notification.
Note that you will only ever receive one notification about the same event for a work item.
For each event you subscribe to, you will automatically get notified in Work Manager in the Notifications Centre (via the Notifications icon in the header bar) - with a counter showing the number of unread notifications. However you can additionally choose if you also want to be notified by email and/or by browser pop-up.
The Notifications icon shows you how many unread notification messages you have.
Clicking on the Notifications icon will display your Notifications Centre.
This will show the notification messages you have received (displaying the latest 100 notifications), sorted into 'All' and 'Unread'.
Clicking on the notification will take you to the work item it relates to.
You also have the option to mark individual and (from the ellipses menu) all notifications as read.
The Do Not Disturb option turns off all email and browser pop-up notifications. Note: you'll still continue to receive notifications in your Notifications Centre.
You can adjust your notification preferences by clicking on the 'Notification Settings' option or by going to you User Settings and then clicking to view 'Notification Settings'.
Notifications will be sent in the user's preferred language. If a user switches to a different language, all previous notifications will remain in the previous language, but any new notifications will appear in the new preferred language.
If you have Browser pop-up notifications turned on, whenever a notification is generated they will appear on the bottom-right of your screen. Clicking on the link to the work item will take you direct to that work item.
Browser pop-up notifications will appear on any screen as long as you are logged into a Work Manager session.
You may need to adjust your browser settings in order for browser pop-up notifications to appear. If you need to do this, you will be alerted in the Notifications Centre.
To adjust your browser settings, go to Settings > Privacy and Security > Site Settings > Permissions > Notifications and adjust the settings to ensure that sites can send notifications to your browser.
Note that if Do Not Disturb is on, email notifications and browser pop-up notifications will be disabled and will no longer appear until Do Not Disturb has been switched off. Additionally, browser pop-up notifications will not appear when the browser is in incognito mode.
Email notifications will be sent to the email address that is configured for users in Builder.
The address that the email will be sent from is Unmonitored Email Address that has been configured in Builder.
Email notifications will contain a link to the work item they relate to. If a user is already logged in to Enate, clicking on the link will take them straight to that work item. If the user has logged out, clicking on the link will take them to the Enate log in screen. Once they have logged in, they will be taken straight to the work item.
Note that if Do Not Disturb is on, email notifications and browser pop-up notifications will be disabled and will no longer appear until Do Not Disturb has been switched off.
In addition to seeing your notifications within the Work Manager Notifications Centre, as browser popups and via email, you can also set to see your browser popups within various parts of your Desktop, e.g. in your windows start menu and on your machine's lock screen.
Sounds can also be turned all turned on within your desktop's notifications settings to allow for sounds to play whenever a desktop notification shows.
You can choose to turn off ALL notifications by selecting this option in your User Settings tab at the top of the Notifications Settings section.
While this option is switch on, no notifications will be generated for you. Your preferences will have been saved for when you want to turn notifications back on.
Note: If and when you choose to resume notifications, the system will begin to generate new notifications for you but any which would have been generated in the interim period will not be retrospectively created.
For users on v2024.1, they will be able to use the forecasting feature to provide more accurate estimated efforts for work items, enabling you to plan resource requirements more effectively.
In the long term, this data can be collated and fed back to admin users to adjust estimated effort timers and to provide more accurate forecasting for future work volumes.
Once the 'Forecasting' feature has been switched on, a new ‘Effort Estimation’ tab will appear in Cases in Work Manager.
Here you'll see a summary of the estimated effort for the whole Case, a breakdown of the estimated effort for Actions or Sub Cases that make up the Case, and a breakdown of the estimated effort for Actions or Sub Cases that have not been created yet.
The 'Case Effort Summary' section is where a user can change the estimated time for the Case. It also provides other useful metrics for the Case.
'Total Case Estimated Effort' effort shows the total estimated time that the Case is estimated to take. This can be updated by a user with a more accurate estimate.
It is the sum of the ‘Estimated’ effort of all the created work and the Actions (and Sub Case Actions) that make up the Case and the and the 'Effort for Work Not Yet Created' value
If the ‘Record Count’ gets updated, the ‘Estimated Effort’ for the Case that has not been updated by a Work Manager user will be updated to reflect the change in record count.
Once the Case is in a state of Resolved or Closed, its estimated effort can no longer be changed.
Note that increasing this value will increase the ‘Effort for Work Not Yet Created’ estimate and vice versa.
‘Total Case Actual Effort’ effort shows the amount of time that has been spent working on the Case Effort for Work Not Yet Created.
It is the sum of the 'Actual' effort for all the created Actions and Sub Cases that make up the Case, taken from their respective Time Trackers.
‘Total Case Remaining Effort’ shows the amount of time estimated to be left on the Case.
It is the sum of the 'Total Remaining Effort' effort for all the created Actions and Sub Cases that make up the Case AND the estimated remaining time for work that has yet to be created (therefore it might not always equal the 'Case Estimated' effort minus the 'Case Actual' effort).
Changing the 'Estimated' effort value for a Case has the following effects:
Increasing the 'Estimated' effort for a Case increases the 'Effort for Work Not Yet Created' value by the same amount
Decreasing the 'Estimated' effort for a Case decreases the 'Effort for Work Not Yet Created' value by the same amount
The 'Effort Breakdown for Created Work' section is where a user can change the estimated time for the individual created Actions (and Sub Cases) that make up the Case. It also shows other useful metrics for each of the created Actions (and Sub Cases) that make up the Case.
Note that once an Action is in a state of Resolved or Closed, its estimated effort can no longer be changed.
As Actions (and Sub Cases) get created, the estimated effort for them will be taken from the Estimated effort value from the Work Not Yet Created section below.
Action Breakdown
For each Action, you'll see:
A link to each Action
'Estimated' effort that shows the total estimated time that the Action is estimated to take. This can be updated by a user with a more accurate estimate.
If the ‘Record Count’ gets updated, the ‘Estimated Effort’ for any running Actions that have not been updated by a Work Manager user will be updated to reflect the change in record count.
Increasing this value will decrease the ‘Work Not Yet Created’ estimate and vice versa and therefore might affect the total 'Case Estimated' effort
Note that once an Action is in a state of Resolved or Closed, its estimated effort can no longer be changed.
‘Actual’ effort shows the amount of time that has so far been spent working on that Action
The value is taken from the Time Tracker of the Action.
‘Estimated Remaining’ shows the amount of time estimated to be left on the Action.
It is calculated by subtracting the 'Actual' effort for the Action from the 'Estimated' effort.
The due date of the Action
You'll also see a 'Start By' value if the 'Actual' effort is currently zero. This value show when is the absolute latest that the Action can be started by in order to meet its due date.
The status of the Action
Changing the 'Estimated' effort value for an Action has the following effects:
Automatic update to the 'Effort for Work Not Yet Created' estimated value for the Case.
Possible automatic update to the 'Estimated' effort for the whole Case
Details:
Decreasing the 'Estimated' effort for an Action increases the 'Effort for Work Not Yet Created' value for the Case by the same amount (leaving the 'Estimated' effort for the whole Case the same).
Increasing the 'Estimated' effort for an Action decreases the 'Effort for Work Not Yet Created' value for the Case by the same amount. This may or may not affect the 'Estimated' effort for the overall Case.
If the updated ‘Estimated Effort’ on an Action doesn't increase by enough to cause the ‘Effort for Work Not Yet Created’ value for the Case to go below 0, the 'Estimated' effort for the Case will not be affected
Example: let's say that the 'Estimated' effort for Action 1 is 2 hours, the estimated 'Effort for Work Not Yet Created' is 1 hour and the 'Estimated Effort' for the Case is 3. A user decides that Action 1 is going to take 1 hour more and so updated the 'Estimated' effort for Action 1 from 2 to 3 hours. 'Effort for Work Not Yet Created' will decrease from 1 hour to 0 and the 'Estimated' effort for the Case will not change - it will stay at 3 hours.
If the updated ‘Estimated Effort’ on an Action increases enough to cause the ‘Effort for Work Not Yet Created’ value for the Case to go below 0, the difference should be added to the ‘Estimated Effort’ of the overall Case.
Example: let's say that a Case only has one Action created for it called Action 1. The 'Estimated' effort for Action 1 is 2 hours, the estimated 'Effort for Work Not Yet Created' is 0 and therefore the 'Estimated Effort' for the whole Case is 2 hours. A user decides that Action 1 is going to take 1 hour more and so updates the 'Estimated' effort for Action 1 from 2 to 3 hours. Because 'Effort for Work Not Yet Created' is 0, the 'Estimated' effort for the overall Case is therefore going to increase by 1 hour from 2 to 3 hours.
Example 2: let's say that a Case only has one Action created for it called Action 1. The 'Estimated' effort for Action 1 is 2 hours, the estimated 'Effort for Work Not Yet Created' is 1 hour and therefore the 'Estimated Effort' for the whole Case is 3 hours. A user decides that Action 1 is going to take 2 more hours and so updates the 'Estimated' effort for Action 1 from 2 to 4 hours, causing the 'Effort for Work Not Yet Created' to decrease by 1 hour from 1 to 0 (decreasing as far as it can). The "remaining" 1 hour will effectively be added to the total 'Estimated' effort of the Case that will increase by 1 hour to from 3 to 4 hours.
Sub Case Breakdown
If a Sub Case gets created, you'll see:
A link to the Sub Case if you have permission to access it (otherwise you'll just see the name and reference number of the Sub Case with no link)
A Sub Case "total" row with the following:
'Estimated' effort shows the total estimated time that the Sub Case is estimated to take. This can be updated by a user with a more accurate estimate.
It is the sum of the ‘Estimated’ effort of all the created and yet-to-be created Actions that make up the Sub Case.
If the ‘Record Count’ gets updated, the ‘Estimated Effort’ for the Sub Case that has not been updated by a Work Manager user will be updated to reflect the change in record count.
Once a Sub Case is in a state of Resolved or Closed, its estimated effort can no longer be changed.
Note that increasing this value will increase the ‘Work Not Yet Created’ estimate for the Sub Case and vice versa.
‘Actual’ effort shows the amount of time that has so far been spent working on the Sub Case.
It is the sum of the 'Actual' effort for all the created Actions that make up the Sub Case, taken from their respective Time Trackers.
‘Estimated Remaining’ shows the amount of time estimated to be left on the Sub Case.
It is the sum of the 'Estimated Remaining' effort for all the created Actions that make up the Sub Case AND the estimated remaining time for work that has yet to be created for that Sub Case (therefore it might not always equal the 'Sub Case Estimated' effort minus the 'Sub Case Actual' effort)
The due date of the Sub Case
The status of the Sub Case
A row for each Sub Case Action with the following:
'Estimated' effort shows the total estimated time that the Sub Case Action is estimated to take. This can be updated by a user with a more accurate estimate.
If the ‘Record Count’ gets updated, the ‘Estimated Effort’ for any running Sub Case Actions that have not been updated by a Work Manager user will be updated to reflect the change in record count.
Increasing this value will decrease the ‘Work Not Yet Created’ Sub Case estimate and vice versa and therefore might affect the total 'Sub Case Estimated' effort
Once an Action is in a state of Resolved or Closed, its estimated effort can no longer be changed.
‘Actual’ effort shows the amount of time that has so far been spent working on that Sub Case Action
The value is taken from the Time Tracker of the Sub Case Action.
‘Estimated Remaining’ shows the amount of time estimated to be left on the Sub Case Action.
It is calculated by subtracting the 'Actual' effort for the Sub Case Action from the 'Estimated' effort.
The due date of the Sub Case Action
You'll also see a 'Start By' value if the 'Actual' effort is currently zero. This value show when is the absolute latest that the Sub Case Action can be started by in order to meet its due date.
The status of the Sub Case Action
A row for 'Sub Case Work Note Yet Created' with the following:
'Estimated' effort shows how much effort is estimated to be needed to complete the Sub Case Actions that have not yet been created for that Sub Case. This can be updated by a user with a more accurate estimate.
Changing this estimate will affect the total 'Sub Case Estimated' effort and might affect the effort estimate for the overall Case
Changing the 'Estimated' effort value for a Sub Case Action has the following effects:
Automatic update to the 'Effort for Work Not Yet Created' estimated value for the Sub Case.
Possible automatic update to the 'Estimated' effort for the whole Sub Case
Possible automatic update to the 'Estimated' effort for the whole parent Case.
Details:
Decreasing the 'Estimated' effort for a Sub Case Action increases the 'Effort for Work Not Yet Created' value for the Sub Case by the same amount (leaving the 'Estimated' effort for the whole Sub Case the same and therefore having no impact on the 'Estimated' effort for the whole parent Case).
Increasing the 'Estimated' effort for a Sub Case Action decreases the 'Effort for Work Not Yet Created' value for the Sub Case by the same amount. This may or may not affect the 'Estimated' effort for the overall Case.
If the updated ‘Estimated Effort’ on a Sub Case Action doesn't increase by enough to cause the ‘Effort for Work Not Yet Created’ value for the Sub Case to go below 0, the 'Estimated' effort for the Sub Case will not be affected (and therefore the 'Estimated' effort for the whole parent Case will not be affected).
Example: let's say that a Sub Case only has one Action created for it called Sub Case Action 1. The 'Estimated' effort for Sub Case Action 1 is 2 hours and the estimated 'Effort for Work Not Yet Created' for the Sub Case is 1 hour, therefore the 'Estimated Effort' for the Sub Case is 3 hours. A user decides that Sub Case Action 1 is going to take 1 hour more and so updates the 'Estimated' effort for Sub Case Action 1 from 2 to 3 hours, causing the 'Effort for Work Not Yet Created' for the Sub Case to decrease from 1 hour to 0. The 'Estimated' effort for the Sub Case will not change - it will stay at 3 hours (and therefore the 'Estimated' effort for the whole parent Case will not be affected).
If the updated ‘Estimated Effort’ on a Sub Case Action increases enough to cause the ‘Effort for Work Not Yet Created’ value for the Sub Case to go below 0, the difference should be added to the ‘Estimated Effort’ of the overall Sub Case, (and therefore might impact the 'Estimated' effort for the whole parent Case).
Example: let's say that a Sub Case only has one Action created for it called Sub Case Action 1. The 'Estimated' effort for Sub Case Action 1 is 2 hours and the estimated 'Effort for Work Not Yet Created' for the Sub Case is 0, therefore the 'Estimated' effort for the overall Sub Case is 2 hours. A user decides that Sub Case Action 1 is going to take 1 more hour and so updates the 'Estimated' effort for Sub Case Action 1 from 2 to 3 hours. Because 'Effort for Work Not Yet Created' for the Sub Case is 0, the 'Estimated' effort for the Sub Case is going to increase by 1 hour from 2 to 3 hours.
If there is enough time in the 'Effort for Work Not Yet Created' of the parent Case, this 1 hour increase might be taken from there, therefore there will be no impact on the 'Estimated' effort for the whole parent Case.
If there is isn't enough time in the 'Effort for Work Not Yet Created' of the parent Case, this 1 hour increase will result in an increase in the the 'Estimated' effort for the whole parent Case.
Example 2: let's say that a Sub Case only has one Action created for it called Sub Case Action 1. The 'Estimated' effort for Sub Case Action 1 is 2 hours and the estimated 'Effort for Work Not Yet Created' for the Sub Case is 1 hour, therefore the 'Estimated' effort for the overall Sub Case is 3 hours. A user decides that Sub Case Action 1 is going to take 2 more hours and so updated the 'Estimated' effort for Sub Case Action 1 from 2 to 4 hours, causing the 'Effort for Work Not Yet Created' for the Sub Case to decrease as much as it can - here it will decrease by 1 hour to from 1 to 0. The "remaining" 1 hour will effectively be added to the total 'Estimated' effort of the Sub Case that will increase by 1 hour from 3 to 4 hours.
If there is enough time in the 'Effort for Work Not Yet Created' of the parent Case, this 1 hour increase might be taken from there, therefore there will be no impact on the 'Estimated' effort for the whole parent Case.
If there is isn't enough time in the 'Effort for Work Not Yet Created' of the parent Case, this 1 hour increase will result in an increase in the the 'Estimated' effort for the whole parent Case.
The 'Effort for Work Not Yet Created' section shows how much effort is estimated to be needed to complete Actions (and Sub Cases Actions) that have not yet been created for this Case.
It is calculated by subtracting the sum of the 'Estimated' effort for created work from the 'Estimated' effort for the Case. Therefore, increasing the 'Effort for Work Not Yet Created' will increase the effort estimate for the overall Case and vice versa.
As Actions (and Sub Cases) get created, the estimated effort for them will be taken from the 'Estimated Effort for Work Not Yet Created' value.
Once the Case is in a state of Resolved or Closed, the 'Effort for Work Not Yet Created' can no longer be changed.
Attachments from incoming emails are denoted with a green email icon:
Attachments from outgoing emails are denoted with a blue email icon:
The field will will initially show the manual ‘’ value from Builder (if there is one) multiplied by the
Automatic update to the. This is because the ‘Estimated Effort’ for the Case is a calculated value made up of the sum of the ‘Estimated’ effort of all the created work and the Actions (and Sub Case Actions) that make up the Case and the and the 'Effort for Work Not Yet Created' value.
The field will will initially show the manual ‘’ value from Builder multiplied by the
The field will initially show the manual ‘’ value from Builder multiplied by the
The field will will initially show the manual ‘’ value from Builder multiplied by the
If you wish to quickly re-access a work item (e.g. you wish to re-open a work item tab you’ve just closed down), open the ‘Recently Accessed’ link from the navigation dropdown.
This will display a list of the last 20 items which you have accessed (along with datetime the tab was closed), ordered by most recent first. Click an item to re-open the tab.
Custom Data can be added to Tickets, Cases and Actions to capture bespoke information on these work items as they run through process. The information is displayable via Custom Cards. Custom Cards can be set to display in the main section of the work item, and also as a section of the side panel on the right side of the screens.
Custom Cards can be designed (with HTML, Typescript and CSS) to surface almost any content, e.g. content from other systems.
Custom Cards can be linked up to standard system validation in order to e.g. make filling in of certain data on a card a requirement before you can progress a work item.
If you have a work item open and are modifying custom data, Enate will check for any data conflict when you go to update the work item. Specifically, a check will be made to see if another user has accessed the work item and changed any of its custom data since you opened it. If so, a confirmation message box will be displayed to you asking whether you wish to proceed with your update (which will override their changes) or instead cancel and refresh your screen to see (and keep) those latest changes.
Peer Review Actions are a great way for different members of a team to crosscheck each other's work for key Actions within a Case.
Peer Review Actions involve two parts: the first part is completing the Action, done by one user. The second part involves reviewing the Action to check it was completed correctly, done by a different user.
Watch this video for a quick overview about how to use Peer Review Actions in Work Manager:
The Peer Review Action will first appear in a state of 'To Do' to the user who is tasked with completing the Action.
The peer review symbol will let you know if you are completing an Action that is then going to be reviewed by a peer:
The first user needs to complete the Action as normal and mark it as 'Resolved'.
Once the Action has been completed and marked as 'Resolved', the Action is then assigned to a different user to review, back in a state of 'To Do'.
Note: The person who carried out the manual activity cannot also perform the peer review activity.
The peer review symbol will let you know if you are peer reviewing an Action that was completed by a colleague:
When you are on the screen of the Action which is being peer reviewed, you'll see a Peer Review text box along the top, allowing the reviewer to add any overall comments relating to reviewing how the Action was completed.
The checklist is only available when the Action is in a state of 'To Do' and only the assigned reviewer is able to edit the checklist.
Once you have finished your review activity, switch the status of the Action to resolve and then choose if the review was a Pass, Fail or was Unable to be completed and then click to confirm.
If you're happy to approve the activity, selecting 'Pass' will mark it as such and will close the Action on-screen. You can add a comment, but it is not mandatory.
If you then click to re-display the action, you'll see that next to Peer Review it now says Passed, and any comments entered can be read.
If the Action has not been done correctly, you should select 'Fail' and must add a comment in the Peer Review Comments section with the details of why.
Submitting the review will then return this Action back to the agent who carried out the original activity in a state of 'To Do'.
When that original agent opens the Action, they'll see 'Failed' next to the peer review, and will be able to read all of the comments left by the reviewer.
Their role now is obviously to redo that activity to correct the issues raised, then once again mark it as resolved. It will then be routed through to the reviewer again to carry our another peer review.
The other option is that the reviewer is unable to successfully carry out a review. In this circumstance they should select 'Unable to complete'. The system will then ask the reviewer to provide a reason as to why they were unable to complete the review.
Once that has been provided, they can mark the Action as resolved.
This closes the Action and marks it as 'not done successfully'. This escalates up to the Case, which will now display a warning symbol and the notification that the case needs intervention in order to move forward.
It IS sometimes the case that the peer review activity gets automatically bypassed if it meets certain criteria set as part of the Case configuration.
If that happens, then as soon as the manual Action is completed, the system will move straight on to the next Action and will avoid routing the work to someone to peer review.
Further to this, a note will subsequently be displayed in the Actions list on the Case screen, showing that the peer review activity was not required.
Often within the Case flows of business processes which are built in Enate there are points where external people (i.e. people working outside Enate - this could be business managers within your company or the relevant client company) need to sign off on activities before the process can continue. Payroll processes are good examples of such processes, where client management need to sign off on payroll reports before the process can be allowed to continue.
Enate's Approval Action is built to specifically support these approval request scenarios in a more integrated way - to ensure that this 'approval cycle' is tightly managed and visible within the flow of activities in Enate.
Approval requests get sent out to agents working externally from Enate to approve or decline.
There are a few different types of approval that affect how the decision is made:
In a multilevel scenario, the request email is sent to each new level upon successful approval from previous, up to a maximum of 3 levels. If any person declines, the approval is declined.
In a parallel any scenario, the request email is sent to all approvers and the first decision is taken.
In a parallel all scenario, the request email is sent to all approvers and ALL must approve for the request to be approved. If any decline, the approval is declined.
If the request gets approved by all necessary parties, the approval Action gets successfully resolved and closed automatically, so no Work Manager Agent will need to pick it up, although the closed Action can always be viewed by manually clicking on it.
There are, however, a couple of scenarios where a Work Manager agent might need to pick up and carry out any required activities to further process an approval Action:
The approval has been declined
No approvers (or insufficient approvers) have been determined automatically
In the scenario where an approval request has been declined, the Action will move into a state of 'To Do' and so will ultimately need to be dealt with by a Work Manager Agent. They should review the approval decline reason provided by the approver and decide how to proceed. They can either:
Update as needed and Resend the request by setting the Action to 'Wait'. This will auto-send out the approval request email again** and place the Action in a state of 'Wait for More Information' - since we're waiting for external information (an approval response) to be registered back into the system before activity can proceed.
Mark the Action as Unable to complete. This will alert the Case owner who then needs to decide how to proceed - perhaps by reworking the Case or closing the Case entirely.
Mark the Action as Resolved which will manually mark the request as approved. The Case with then progress to the next Action.
**Note: Approval request email sending will start again from the beginning, i.e. all requesters will be mailed again. If they click on any previously sent emails, they will be met with a message telling them that THAT specific approval request is no longer valid, as the details of what is being requested may have changed).
In the scenario where an agent needs to add in approvers because one or more required approvers is blank (or make changes which result in the approval requests needing to be sent out again), the Agent will pick up the Approval Action in a state of To Do. Once they have finished making any adjustments and / or filling in missing Approver names, the must then place the Action in a state of Wait. Once they do this will auto-send the approval request email and then move the Action to a state of 'Wait for more information' as it is waiting for external info (approval) before proceeding.
Note: While an Approval Action is state of 'To Do', or 'In Progress', external parties who were mailed out approval requests will NOT be able to approve or decline. Instead the will be met with a message informing them that the item in question is currently being processed. Work Manager Agents MUST move the Action back to a state of 'Wait for more information' if they wish the approval activity to recommence.
Another potential scenario is that the approval Action might auto-close because it has timed out as no/insufficient responses were received in time. In this case, the Action will automatically be set to Resolved, and the Case will continue. No Work Manager agent will need to pick up an Action in this scenario, although the closed Action can always be viewed by manually clicking on it.
If issues have occurred during the running of a Case you may wish to rework the Case.
You can do this from the Case by selecting the ‘Rework’ tab. In the resulting panel, you need to choose where you want to restart the Case from. You can choose to rework the Case from a specific Step or from a specific Action. You can also select a schedule if your system has been configured to allow you to do so.
Note: In order to re-evaluate the Case Conditions, rework must be started from the start of a step. Further specifics on this:
You cannot rework from an Action which was started as an ad-hoc Action.
Users are still limited to reworking from steps prior to the current one, and so are also limited to choosing Actions from within prior steps.
If rework is performed multiple times then there may already be downstream steps that were previously completed - however they are not eligible for selection as restart point.
Additionally, if the Case you are wanting to rework has any associated running Sub Cases or manually started Actions (Ad-hoc Actions), you can choose to terminate them as part of reworking the Case.
Once you are happy, click the ‘Rework’ button in the info card to confirm and begin reworking the Case.
The Case will move to a state of In Progress.
All running Actions that are part of the Case will close when the Case is set to rework.
Copies of these Actions will be created in the Case, all in a state of To Do.
An entry will also be added to the timeline showing who set the Case to rework, when it was set to rework, and the Step number and Action it was set to rework from. This will also appear in related work item timelines i.e. its Actions and any Sub Cases if you have selected the Case Rework History filter from the timeline filters options.
You can do this from an Action by selecting the ‘Rework’ tab. In the resulting panel, you need to choose where you want to restart the Case from. You can choose to rework the Case from a specific Step or from a specific Action. You can also select a schedule if your system has been configured to allow you to do so.
Note: In order to re-evaluate the Case Conditions, rework must be started from the start of a step. Further specifics on this:
You cannot rework from an Action which was started as an ad-hoc Action.
Users are still limited to reworking from steps prior to the current one, and so are also limited to choosing Actions from within prior steps.
If rework is performed multiple times then there may already be downstream steps that were previously completed - however they are not eligible for selection as restart point.
Additionally, if the Case you are wanting to rework has any associated running Sub Cases or manually started Actions (Ad-hoc Actions), you can choose to terminate them as part of reworking the Case.
Once you are happy, click the ‘Rework’ button to confirm and begin reworking the Case.
All running Actions that are part of the Case, including the Action you are currently in, will close when the Case is set to rework:
And copies of these Actions will be created in the Case, all in a state of To Do.
An entry will also be added to the timeline showing who set the Case to rework, when it was set to rework, and the Step number and Action it was set to rework from. This will also appear in related work item timelines i.e. its Actions and any Sub Cases if you have selected the Case Rework History filter from the timeline filters options.
When an Action is started in a Case which is currently in rework, the Action will auto-assign to the same user who previously performed the same Action (either the user who completed the Action or, if it was not completed previously, then the last user it was assigned to).
Note: If 'Keep Actions with Me' is selected on the Case, the ‘keep with’ logic will take precedence.
Launching a Case or Ticket from within an existing one creates a 'Linked' relationship between the work items.
Work items with a 'linked' relationship will retain a link to the original Case / Ticket but are completely independent, behaving according to their own specific configuration and not needing to wait for the other to complete before they can complete themselves. This is useful when the original Case/Ticket's due date is not dependent on some sub part being completed (e.g. by a different department).
Linked work items will show on a Linked Work tab in the work item screen, making it easy to track a group of work items which relate to each other.
Note that only Cases and Tickets can be 'linked' and when a work item is linked to another work item and it is subsequently merged, split or converted into a Case, the subsequent work items resulting from this will also be linked to the original work item.
For example:
When a Ticket is linked to another work item and that Ticket is merged in with another work the remaining merged item will be linked to the original work item.
When a Ticket is linked to another work item and that Ticket is split into multiple Tickets, the subsequent child Tickets will also be linked to the original work item.
When a Ticket is linked to another work item and that Ticket is later converted into a Case, the subsequent Case will also be linked to the original work item.
To create a new linked Ticket from an existing Case or Ticket, click the ‘+ Work item’ link shown near the tabs section of the work item and the choose the 'Ticket' option from the dropdown.
In the resulting pop up, you can filter to search for the new type of Ticket process you want to create in two ways:
by searching by email route - you can specify the mailbox address which people would normally send emails into to create work items. Often an email mailbox represent a certain part of the business within which you want to create your new work item. As a useful shortcut we've added a feature here where you can search by mailbox and narrow down straight away the Ticket processes that you can choose from. Selecting a mailbox will filter the dropdown options to only the processes linked to that mailbox.
by selecting a Customer, Contract, Service and a Ticket process to launch (these will default in values if there is only one option to choose).
Please note that the Tickets available for you to launch will depend on the permissions settings in Builder. Additionally, you will also only be able to select a Ticket process from an email route that has been enabled in Builder (see here for more information). You will also only be able to select a Ticket process in Test Mode if the email route for that Ticket process has been configured to run in Test Mode.
You can then adjust the following settings for the Ticket:
Title
You can modify the title of the new Ticket you are creating
Short Description
You can modify the description of the new Ticket you are creating
Category & Sub Categories
You need to select the category & sub categories of the new Ticket
Override Due Date
Copy Defects
You can copy existing defects from the original Case/Ticket to the new Ticket you are creating. Note that making updates to the Defects in the new linked Ticket will NOT update the defects in the original Ticket/Case it was created from.
Copy Files
You can copy existing files (including tags & file notes) from the original Case/Ticket to the new Ticket you are creating. Note that making updates to the files in the new linked Ticket will NOT update the files in the original Ticket/Case it was created from.
Copy Links
You can copy existing links (including tags & link notes) from the original Case/Ticket to the new Ticket you are creating. Note that making updates to the links in the new linked Ticket will NOT update the links in the original Ticket/Case it was created from.
Copy Custom Data
You can copy existing custom data (e.g. custom data fields) from the original Case/Ticket to the new Ticket you are creating. Note that making updates to the custom data in the new linked Ticket will NOT update the custom data in the original Ticket/Case it was created from.
Copy Communications
Send Automated Emails
You can choose to send auto-generated system emails (e.g. Ticket creation acknowledgement emails) to contacts tagged as the the primary contact, requester or subject.
Adding Contacts
Then click to Create. A link to the new linked Ticket will appear in the 'Linked Work' tab.
Linked Cases will retain a link to the original Case / Ticket but are completely independent, behaving according to their own specific configuration and not needing to wait for the other to complete before they can complete themselves. This is useful when the original Case/Ticket's due date is not dependent on some sub part being completed (e.g. by a different department).
To create a new linked Case from an existing Case or Ticket, click the ‘+ Work item’ link shown near the tabs section of the work item and the choose the 'Case' option from the dropdown.
In the resulting pop up, you can filter to search for the new type of Case process you want to create in two ways:
by searching by email route - you can specify the mailbox address which people would normally send emails into to create work items. Often an email mailbox represent a certain part of the business within which you want to create your new work item. As a useful shortcut we've added a feature here where you can search by mailbox and narrow down straight away the Case processes that you can choose from. Selecting a mailbox will filter the dropdown options to only the processes linked to that mailbox.
by selecting a Customer, Contract, Service and a Case process to launch (these will default in values if there is only one option to choose).
Please note that the Cases available for you to launch will depend on the permissions settings in Builder. Additionally, you will also only be able to select a Case process from an email route that has been enabled in Builder (see here for more information). You will also only be able to select a Case process in Test Mode if the email route for that Case process has been configured to run in Test Mode.
You can then adjust the following settings for the Case:
Short Description
You can modify the short description of the new Case you are creating
Schedule
Override Due Date
Copy Defects
You can copy existing defects from the original Case/Ticket to the new Case you are creating. Note that making updates to the defects in the new linked Case will NOT update the defects in the original Ticket/Case it was created from.
Copy Files
You can copy existing files (including tags and file notes) from the original Case/Ticket to the new Case you are creating. Note that making updates to the files in the new linked Case will NOT update the files in the original Ticket/Case it was created from.
Copy Links
You can copy existing links (including tags and link notes) from the original Case/Ticket to the new Case you are creating. Note that making updates to the links in the new linked Case will NOT update the links in the original Ticket/Case it was created from.
Copy Custom Data
You can copy existing custom data (e.g. custom data fields) from the original Case/Ticket with the new Case you are creating. Note that making updates to the custom data in the new linked Case will NOT update the custom data in the original Ticket/Case it was created from.
Copy Communications
Send Automated Emails
You can choose if you want to send auto-generated system emails (e.g. Case creation acknowledgement emails) to contacts tagged as the the primary contact, requester or subject.
Adding Contacts
Then click to Create. A link to the new linked Case will appear in the 'Linked Work' tab.
The User's Overview report displays information regarding the Enate user who's account has been used to sign in. The report shows all work relating to user allowing them to quickly plan their day and week accordingly.
Access to and the ability to edit the User's Overview is controlled by permissions in user roles, in the same way as all other reports within Enate. If users do not have the right permissions enabled, they will not be able to access or edit the report.
Here are some of the type of information which can be found within the report
Pinpoint priority areas with SLA-tracked open work items by queues for efficient task management.
Streamline workload management with monthly counts of started and closed work items, ensuring timely service delivery.
Prioritize corrective actions with counts of resolved and unresolved defects by category, enhancing service quality.
See which defect categories are being used and how many times they are used.
Gauge resource utilization and boost productivity with monthly-tracked active hours logged in Enate.
See below for a complete list of all the available data fields that can be used within the User's Overview report:
If your system has been configured this way (), you can select to override the due date of the new Ticket you are creating.
You can copy work item communications i.e. emails (including email attachments) and notes from the original Case/Ticket to the new linked Ticket you are creating. Note that when choosing to copy communications, you will not only copy communications from the original work item, but you will also copy communications from the original work item's related group, e.g. its Actions if it was a Case, or the parent/child Ticket if it was from a split Ticket. Also note that making updates to the communications in the new linked Ticket will NOT update the communications in the original Ticket/Case it was created from. You can find out more about related groups vs linked work items .
You can choose to add a contact. If have been configured to allow you to do so, you can even choose to add multiple different contacts for the new Ticket and divide the tags between them.
If your system has been configured this way (), you must select a schedule for the new Case you are creating.
If your system has been configured this way (), you can select to override the due date of the new Case you are creating.
You can copy work item communications i.e. emails (including email attachments) and notes from the original Case/Ticket to the new linked Case you are creating. Note that when choosing to copy communications, you will not only copy communications from the original work item, but you will also copy communications from the original work item's related group, e.g. its Actions if it was a Case, or the parent/child Ticket if it was from a split Ticket. Also note that making updates to the communications in the new linked Case will NOT update the communications in the original Ticket/Case it was created from. You can find out more about related groups vs linked work items .
Unless the '' option in the Case type in the Service Line screen has been selected, it is optional for you to add a contact. You can even choose to add multiple different contacts and divide the tags between.
Activity
Total Hrs Logged
Total time (in Hrs) spent by the Agent on all the Work Items he/she worked on for the selected date range
Activity
Activity Type
Type of the activity performed on the Work Item by Agent ('Save' or 'Complete')
Activity
Duration in Sec
Time spent (in seconds) on the Work Item by Agent. Manually entered time is considered if available.
Activity
StartDate
Work Item activity Start Date in date time format
Activity
StartDate_date
Work Item activity Start Date in date only format
Activity
User Name
User who performed the activity
Context
Contract
Name of the Contract
Context
Customer
Name of the Customer
Context
Service
Name of the Service
Context
Supplier
Name of the Supplier
Date
Date
Calendar range of dates for filtering data
Date
Month
Months of the dates
Date
Week
Weeks of the dates
Date
Year
Year of the dates
Defects
Work Item Count
Count of work items that have defects against them
Defects
Date Raised
Date on which the defect was raised for a Work Item
Defects
Defect Category
Category of the defect
Defects
Desciption
Description of the defect
Defects
Status
Stated whether the defect is resolved or not
Process
Process
Name of the process each Work Item belongs to
Process
Work Item Type
Type of the Work Item (Ticket, Action or Case)
Queues
Queue
Name of the queue the Work Item was last present in
Status
Status
Work Item Status (To Do, In Progress, Waiting , Resolved , Closed)
Status Reason
Status Reason
Reason behind the status change of the Work Item (Newly Created, new Info Receieved, Blocked by Business rule etc.)
Wait Status History
Waiting each Day
Count of Work Items that are set to waiting status on a particular day by the Agent (out of the Work Items he/she working/worked on)
Wait Status History
EndDate
End Date in Date time format when Work Item was in waiting state
Wait Status History
EndDate_date
End Date in Date only format when Work Item was in waiting state
Wait Status History
StartDate
Start Date in Date time format when Work Item was in waiting state
Wait Status History
StartDate_date
Start Date in Date only format when Work Item was in waiting state
Wait Status History
User Name
Agent who set the status of Work Item to Waiting
Work Items
Action
Sum of Closed and Waiting work items on a particular day by an Agent
Work Items
Work Items Assigned Today
Count of Work Items that are assgined to the agent today
Work Items
Work Items Closed
Total Work Items closed by agent for the selected date range
Work Items
Work Items Closed Today
Count of Work Items that are closed by agent today
Work Items
Work Items Due Today
Count of Work Items that are due today by agent
Work Items
Work Items Open
Total Work Items that are Open by agent
Work Items
Work Items Overdue
Total Work Items that are Overdue by agent
Work Items
Work Items Reopened
Total Tickets that are reopened for the agent
Work Items
Work Items Resolved
Total Work Items that are Resolved by agent for the selected date range
Work Items
Work Items Started
Total Work Items started by agent for the selected date range
Work Items
Ageing In Days
Aeing in calendar days. For completed Work Items its (end date - start date), for open items its (today - start date).
Work Items
Count of Affected Records
Records affected count
Work Items
Count of Defects
Count of defects each Work Item has (if any)
Work Items
Count of Rework
Count of rework each Work Item has (if any)
Work Items
DueDate
Work Item Due Date in date time format
Work Items
DueDate_date
Work Item Due Date in date only format
Work Items
EndDate
Work Item End Date in date time format
Work Items
EndDate_date
Work Item End Date in date only format
Work Items
Has Defects
Whether the Work Item has defect or not (Yes or No)
Work Items
Reference
Reference number of each Work Item
Work Items
Is Reopened
Tickets that got opened after going to resolved status
Work Items
SLA
Service Level Agreement to indicate where Work Item is Overdue or not
Work Items
StartDate
Work Item Start Date in date time format
Work Items
Start Date_date
Work Item Start Date in date only format
Work Items
Title
Title of the Work Item
The Sentiment Analysis report displays information relating to email sentiment analysis allowing users to quickly and clearly see developing trends regarding incoming emails and take action where necessary.
In order for the Sentiment Analysis report to be available, the EnateAI Sentiment Analysis integration must be enabled (this can be done in Enate's Marketplace in Builder). When this integration runs it generates the data needed for the report. Once this integration has been activated, information will automatically begin to be sent into and displayed in the report.
Access to and the ability to edit the sentiment report is controlled by permissions in user roles, in the same way as all other reports within Enate. If users do not have the right permissions enabled, they will not be able to access the report. To edit the report users will need the 'Create Custom Reports' permission enabled.
Here are some of the type of information which can be found within the report
View the overall share and count of incoming emails analysed as having a positive, neutral or negative sentiment.
Track the fluctuation of email sentiment over time. Look out for any significant changes and address them accordingly.
Compare email sentiment across your companies, regions, services and processes. Take action accordingly.
Identify top senders based on email volume and sentiments to address customer concerns effectively and efficiently.
View the agents that receive the highest volume of positive or negative emails, highlighting areas for improvement or recognition.
View how the number of agents a work item is assigned to affects client sentiment. Take action accordingly.
View how the length of time a work item is open for affects client sentiment. Take action accordingly.
View how meeting and not meeting the SLA on a work item affects client sentiment. Take action accordingly.
View how reopening work items affects client sentiment. Take action accordingly.
View how raising defects on work items affects client sentiment. Take action accordingly.
See below for a complete list of all the available data fields that can be used within the Sentiment Analysis report:
Context
Contract
Name of the Contract
Context
Customer
Name of the Customer
Context
Service
Name of the Service
Context
Supplier
Name of the Supplier
Date
Date
Calendar range of dates for filtering data
Date
Month
Months of the dates
Date
Year
Year of the dates
Feedback
Comments
Feedback comments given on each workitem
Feedback
Logged
Feedback logged date in date time format
Feedback
LoggedDate
Feedback logged date in date format
Feedback
Rating
Feedback rating from 1 - 5
Feedback
6M Moving Avg(Ratings)
6 months moving average over the number of ratings. To be visualised against dates.
Feedback
Avg. Rating
Average ratings given across all workitems
Feedback
Total Ratings
Total number of ratings given
Feedback Types
Feedback Type
Ratings grouped as Happy, Unhappy & Neutral
Process
Process
Name of the process each Work Item belongs to
Process
Process Group
Process group given for Cases / Tickets
Process
Work Item Type
Type of the Work Item (Ticket, Action or Case)
Sentiment Scores
Logged
Email logged date in date time format
Sentiment Scores
LoggedDate
Email logged date in date format
Sentiment Scores
Sender
Email sender's full name or email address (depending on whichever is availible)
Sentiment Scores
Sentiment Confidence
Confidence level of the email classification (or sentiment score) in percentage (0 - 100%)
Sentiment Scores
6M Moving Avg
6 months moving average over the number of emails that have sentiment scores. To be visualised against dates.
Sentiment Scores
Email Count
Total number of emails that sentiment score
Sentiment Scores
Work Item Count
Total number of workitems with emails that have sentiment score
Sentiment Types
Sentiment Type
Types of sentiment (Positve, Negative or Neutral)
Ticket Categories
Ticket Category1
Ticket Category level 1
Ticket Categories
Ticket Category2
Ticket Category level 2
Ticket Categories
Ticket Category3
Ticket Category level 3
Users
User Name
Full name of the user responsible for the work item
Users
Email Address
Email address of the user responsible for the work item
Users
Team Manager
Full name of the manager of the users responsible for the work item
Work Items
Assigned User Count Groups
Grouping of Assigned User Count into different buckets (e.g., 0, 1-3, 3-5, 5-7 etc.). Assigned User Count is the unique number of users assigned to the work item througout it's lifecycle (from start to end).
Work Items
Customer Duration(Hrs)
Total time (in working hours) taken to complete the work item as per the customer calendar. Value will be blank if the work item is still in progress.
Work Items
Customer Duration Groups
Grouping of Customer Durations into different buckets (e.g., 0-24, 24-48, 48-72, 5-7 etc.)
Work Items
DueDate
Work Item Due Date in date time format
Work Items
EndDate
Work Item End Date in date time format
Work Items
Has Defects
Whether the Work Item has defect or not (Yes or No)
Work Items
Is Reopened
Tickets that got opened after going to resolved status
Work Items
Reference
Reference number of each Work Item
Work Items
ResolvedDate
Work Items Resolved Date in date time format
Work Items
SLA
Service Level Agreement to indicate where Work Item is Overdue or not
Work Items
StartDate
Work Item Start Date in date time format
Work Items
Title
Title of the Work Item
Work Items
Supplier Duration(Hrs)
Total time (in working hours) taken to complete the work item as per the supplier calendar. Value will be blank if the work item is still in progress.
If Insights is switched on in your system (see Enabling Insights), when users log into Work Manager for the first time each day, they'll be met with a popup after a short while, asking them to confirm:
Their working hours for the day, e.g. 8 hrs (this may default in a value from their working calendar if one is set for them, or from the previous day's entered value.
a rundown of any non-core activities they may have planned for the day, for example a training session, or 1-2-1 meetings, plus their expected working hours for the day.
optionally, they can note down how they're currently feeling too.
There are three sections to the popup, which will ask Agents about:
Today - what their working hours and break is for today, plus if they have any non-core work activities planned.
Yesterday - confirm if the data tey entered yesterday ended up being correct, amending if needed.
Tomorrow - if they have visibility on what tomorrow looks like, they can fill this in too.
If you are going to be using the Insights feature, every agent should ensure that they have confirmed their data for any day they are working. Team Leaders have visibility on who has not filled in data, and on which days.
Note that agents don't have to fill in their data straight away when the popup appears - they can always revisit the popup later in the day by clicking on the Insights link in their toolbar. If data is incomplete for that user, it will show with a red dot icon..
They can also fill in and amend data via the main 'Insights' page, which they can get to from the nav icon.
The user can either provide the data in the pop-up pages then and there, or click 'X' to close the popup without saving any data. If a user hasn't filled in the data in the pop-up and they they logout and log back in again on the same day, the pop-up will reappear when they log back in.
This section is optional - users can select an emoji to represent how they are feeling. They can also choose to enter an additional comment.
The next section is asking the agent to confirm their overall working hours for the day. There may be defaulted numbers in for your expected working hours (e.g. 8 hours) and expected break (e.g. 1 hour). These may come from the working calendar if one has been set up in Enate, or from whatever values wer entered the previous day. If not such data is available, these will default to 08:00 hrs and 00:00 hrs respectively.
If either of these these need to be changed, clicking the link provided takes the user to the Main Insights Page where they can set this information.
There's also the option to set this day as:
A Non-working day - e.g. a weekend day or time-in-lieu equivalent
On leave - i.e. the agent is on leave / vacation that day.*
*Note that users can set this information a number of days in advance via the main Insights page if e.g. they are going on vacation.
If either of the 'Non-Working Daya / On-Leave' settings are marked for this day, the user won't be asked to fill in a break-out of their time for that day.
The next sections of the pop-up will ask the user for expected time they'll be spending that day on non-core activities. Agents can use the slider or manually enter a value between 0 and 8 hrs.
For clarity here: This section is where you should add any time which you know can't be spent actively working to deliver service because you have e.g a meeting. The expectation is absolutely not that you add in numbers to add up to e.g. 7 hours to 'fill your day' - doing that would signal to your Team Leader that you've no availability to work.
Instead, this is where you enter that e.g. you know you've got 2 hours of meetings today, so your Team Leader will know that of the 7 working hours left in your day after breaks, only 5 of them can be time available to actively work.
Options available to enter for 'Today' are:
Meetings - time spent in any collaborative gathering or group meeting.
Feedback / 1-2-1 - time spent in individual sessions with e.g. team leader, manager, mentor.
Training - time in organised training or knowledge-transfer sessions.
Other - time spent on any other activities which are not listed above, or any additional breaks taken in a day.
When finished filling in data (inlcuding if there are no such activities and the day is fre for active work), users have two options:
Click 'Save & Close' to close the popup and get back to Enate Home Screen OR
Click 'Save & Next' to add further data for yesterday (prev. working day) and Tomorrow.
If they click 'Save and Close', they are done and the system will mark their mandatory Insights data as filled in for that day. Clicking 'Save & Next'
Confirming data for yesterday / the previous working day is much the same as entering for today..
In addition to the categories available for 'Today', two further options are available to confirm where time was spent:
Active Time not tracked by Enate - Time spent actively working to provide service but where a Ticket, Case or Action screen (or Enate email) is NOT open in Enate to auto-track this time.
Examples might be: time spent on the Enate homepage or working in another system where an Enate work item tab is not open and so not auto-tracking time. This does NOT include activities such as meetings or training, which should be noted separately.
Downtime - Time lost due to, e.g. system issues, or non-availability of work.
All data can be modified, including the working hours and break times. If all expected hours entered the day before were correct, the user can hit 'Save and Next'. Otherwise, adjust the data before moving on.
Entering data for tomorrow gives the same options as entering for 'Today'
Once fully complete, users shoud click 'Save and Done'.
At any point users can click back to the popup to adjust data enetered for today, yesterday & tomorrow, and can access the Main Insights Page.
Error Area
Description
Status Error
"not_valid": "Data not valid or Something went wrong"
When wrong information is input into a cell, so work items are not able to be created
"completed": "Completed"
When work items are successfully created
"in_progress": "In progress"
When work item creation is in progress
Error
"1": "Uploaded file is not a *.xls or *.xlsx file"
When the upload file format is other than .xls or .xlsx file
"3": "Workbook has multiple worksheets. Only first sheet will be processed"
When the same file has multiple sheets of work data to be processed
"5": "Master Process Instance not live"
When the process instance is not live or the versions are draft
"101": "Worksheet is missing the required column '{{v0}}'"
When the excel sheet does not have required column to process work items
"102": "Column '{{v0}}' is of type '{{v1}}' which is not supported in Bulk Create"
When we use unsuported dat types like Entity relastionship , Table
"103": "No field found to link Column '{{v0}}' to"
When Validate bulk create api is not able to map the column data with the system data
"200": "Creation of a schedule-driven Case is not supported"
When a Case is linked to schedules and use the Case in the excel
"300": "Title is not unique in file"
When uploaded file has same title for multiple work items in the file
"301": "Title is not unique"
When uploaded file has same title that is already created in system
"302": "Value is blank and column is required"
When there are no input values for mandatory fields
"303": "Value in not valid for data type '{{v0}}'"
When custom field cannot input the particular data or data is not related to custom field
"304": "No person could be found from email address"
When we input a wrong email id or email id is not present in the system
"305": "Customer not found or you do not have permission to see it"
When we input a wrong Customer name or we don’t access to create work items under particular customer
"306": "Contract not found under Customer or you do not have permission to see it"
When we input a wrong Contract name or we don’t access to create work items under particular customer
"307": "Service not found under Contract or you do not have permission to see it"
When we input a wrong service name or we don’t access to create work items under particular Contract
"308": "Process not found under Service or you do not have permission to see it"
When we input a wrong Process name or we don’t access to create work items under particular service
"309": "Ticket Category not found"
When we input wrong tickect category value
"310": "Value is not valid for list"
When the input value doesn’tmatch the configured list/Multi level List data
UI ERROR
"1001": "There are no valid items to process."
Where there is no data to process in excel
"1002": "All valid items have been processed."
When all the valid work items are created
"file_upload_limit": "{{name}} is bigger than the server limit ({{limit}})"
When the uploaded file size is larger than the system configured upload limit
"file_upload_failure": "Failed to upload file"
when file upload is failed
Clicking on the user dropdown will show the following dropdown:
Clicking on your name or picture will bring up User Settings. Here you can select your preferred language, add a profile picture, change your password and select the date and time.
Enate currently supports the following languages:
British English
US English
Spanish
Portuguese (Brazilian)
Romanian
Hungarian
Polish
Russian
French
German
If you choose a non-English language, the UI and labels will be changed to the selected language. If your system admin has configured translation for Case/Ticket/Action in these languages, then all Case/Ticket/Action information will also appear in given language, see here for more information.
Clicking ‘Edit Profile Picture’ will bring up picture control to pick up new image from your machine. Clicking the edit button will allow you to navigate to select picture. You can also delete the existing picture via the delete button.
Enate’s Email Signature feature allows you to configure your own signature for outgoing emails. You can use the Email Signature section to define the signature content to be sent in outgoing emails which you write.
Note: The configured email signature will only be included with the outgoing emails if the ‘Include my signature in the outgoing emails’ checkbox at the foot of this section is checked.
After you have created a signature, clicking on any of the links to bring up the ‘compose new email’ section in any work item will display the configured email signature at the bottom of the email body.
If you wish to reset your password, enter your old and desired new password here, and then click the Save button. After a successful password reset, you will be redirected to the login page to log back in with your new password.
The 'Include my signature in outgoing emails' option lets you choose whether or not to include your personalised signature in the emails you send.
'Don't show create contact popup' lets you choose whether you want to get a Create Contact popup every time you communicate with a contact that isn't already in the system.
The 'Don't show new information warning' option lets you choose whether or not you wish to be notified every time you update a work item and you have not clicked on the new information icon to see the latest changes to the work item.
'Don't show Global agent warning' lets you choose whether or not you want to be notified every time you add a global agent (i.e. an agent who is not linked to a specific company) to a work item.
IF Plus Addressing is enabled in your system to help with matching of emails to work items, then the 'Don't show Check Details warning' option lets you choose whether or not you want to be warned every time you are sending an email to more than one address that is already connected to an Enate mailbox and you have not clicked to view the details for each work item that is being created/linked via that email address.
IF Plus Addressing is enabled in your system to help with matching of emails to work items, then the 'Don't show 'Remove Route Address' warning' option lets you choose whether or not you want to be warned every time you decide to remove an email address when sending an email to more than one address that is already connected to an Enate mailbox.
The 'Open links in new browser tab' option lets you decide how you would like the links you click on in Enate Work Manager to open - either in a new, dedicated browser tab or in your current browser tab. By default, this option is set to OFF, meaning that when you click on a link the new content displays in your current browser tab. If you'd prefer that the links you click on open in new, different browser tabs, switch this option to ON and save your change. Now when you click on links, you'll see that a new dedicated browser tab will open up to show that content.
Clicking on the Logout link will end your Enate session and take you back to the login screen.
If you’ve forgotten your password you can reset this from the logon page by clicking on the ‘Forgot password’ link:
Enter your username in the resulting screen.
If your username is associated with an email address then you will receive an email with a link to reset your password.
Whenever your password is reset via this method, you will receive an email confirming this.
The Undo Send setting lets you add a time delay to when your emails will be sent, giving you the opportunity to cancel sending an email, or reviewing an email before it gets sent, click here fore more information.
You can set an Undo Send time by moving the slider along to the desired setting.
Enate's Notifications keep you up to date on what's happening with any Tickets, Actions and Cases you're interested in to keep you in the loop at all times. You've got lots of flexibility with how you receive notifications, in terms of which items you follow, what events you're notified about for them and how they're delivered to you.
This is where you can choose which notifications you want to receive and how.
In addition to choosing to follow an individual work item, you can also use the notifications settings page to specify more generally which notifications you want to automatically receive. There are two parts to this:
First, you specify which work items you want to receive, e.g. item's in your own Work Inbox.
Further to this, you specify which events about those work items you want to be notified about.
See below for details ..
You can choose to receive notifications for work items in you Work Inbox and/or for work items in your Queues.
My Work Inbox
You will receive notifications for work items that are in your Work Inbox i.e. work items that are assigned to you.
This is switched on by default for all users.
My Queues
You will receive notifications for work items that are in Queues that you are in and/or manage.
This option is switched on by default for Team Leaders.
In addition to this, you need to choose which events you want to be notified about for these Work Items.
The options are as follows:
New Information Received
New information (Email/Notes/Self Service Note) has been received on the work item
Users subscribed to receive notifications for a work item related to this (e.g. Case/Actions or the child/parent of a split Ticket) will also receive the notification.
Work Item Assigned to Me
Assigned user of a work item has changed to me
New Work Item into Queue
Assigned Queue of a work item has changed to a Queue that I am in and/or manage
New File/Link Added
New file/link has been added to the work item
Due Date 'At Risk' Reminder
Due date of the work item is deemed to be at risk. This is calculated by subtracting the expected time for the work item to take with an additional 30 minutes from the due date/time.
E.g. if the work item is due to be completed at 17.00 and the time expected to complete the work item is 1 hour, the Due Date 'At Risk' Reminder will be sent at 15.30.
Note that this notification will not be sent if:
the work item is in a state of Draft
the work item is in a state of In Progress and assigned to a user
the work item is in a state of Waiting AND its due date has been configured with the option 'Add Wait Time To Due Date'
Anyone subscribed to receive notifications for the parent of this work item (if there is one) will also receive this notification.
Work Item is Overdue
The due date of the work item has been missed and it is now overdue.
Action Rejected
A robot has actively rejected an Action, or repeatedly failed to process it.
Case Needs Attention
A Case has encountered a problem and requires intervention before it can proceed.
Peer Review Changes
The peer review of an Action has been marked as 'Passed', 'Failed', or 'Unable to be Completed'.
Note that in order to receive this notification, users must:
be in the Queue that this Action belongs to (or manage it), AND
be subscribed to receive notifications about this Action (being subscribed to the Case is not enough), AND
have the setting to receive notifications from 'My Queues' switched on.
Additionally, the person who completed the peer review will not receive the notification.
Note that you will only ever receive one notification about the same event for a work item.
For each event you subscribe to, you will automatically get notified in Work Manager in the Notifications Centre (via the Notifications icon in the header bar) - with a counter showing the number of unread notifications. However you can additionally choose if you also want to be notified by email and/or by browser pop-up.
There are three useful navigation links:
1. Enate Homepage – This is the Enate Company website. Here you can see latest resources, industry insight and product release info.
2. Enate Academy – Here you can sign up for different Enate learning courses in English, Spanish and Portuguese languages.
3. Enate Help – This is a link to Enate's Work Manager help files.