You can think of a task as a checklist that you can delegate with other teams. Let’s say you receive a ticket that requires an agent from another team to complete certain things before you can actually resolve the issue. You can add a task, assign it to the appropriate agent and even set a due date for it.
You can create tasks even if you want to split a complex ticket among your fellow agents for a faster resolution.
Yes, we can assign a task to a group while creating it or later by editing the task.
Operational Level Agreements (OLA) policy lets the support team have internal agreements with the teams that they collaborate with. Admins can configure OLA Policies that dictate the time within which Agents should complete ‘Tasks’ within Tickets or Problems or Changes Releases, ensuring continuous service delivery and compliance.
Please refer to our solution article on Creating a task OLA policy in your service desk : Freshservice for more detailed information.
A task can be assigned to only one particular agent. If you need to create a task for multiple agents, we recommend creating multiple tasks and assigning to different members
We can automate the creation of Tasks based on specific conditions using the workflow automation. You can navigate to Admin-->Workflow Automator and create a new automator and setup the same
Yes, we do have email notifications which are sent to agents based on the task events. You can check these from Admin-->Email Notifications-->Tasks
Tasks can be assigned to a different group apart from the group to which the ticket is assigned to.
Yes, you would be able to view the tasks based on the agent by clicking on the tasks icon on the navigation header and view the tasks based on the group or agent assigned to the task.
While creating the task, you will be able to select the notify before option which will send you the reminder notifications for the task.
Yes, we can configure Ticket Closure rules which prevent the ticket to be resolved or closed unless all associated tasks have been marked as completed. You can navigate to Admin-->Ticket Closure Rules to configure the same. For more information on Ticket Closure Rules refer to the article here
Yes, you would be able to run reports on tasks from the analytics module. Navigate to Analytics and create a new report and choose the widget type to be as Task Widgets. This allows you to filter based on the task properties.
When creating the time entry in the ticket, you can choose which task is the time information to be added to. This information can later be reported on as well.
In Freshservice, the task is a standard module and is not part of the ticket SLA. Tasks have their own due date setup, separate from the ticket SLA. Follow the steps below to set up a due date for tasks and receive timely notifications:
- Go to the ticket, and under the Tasks tab, click on the task for which you wish to set a due date.
- Click on the 3 dots and select Edit.
- Scroll down to the Due Date field and select the desired due date and time using the provided date picker.
- Click on Update to save the changes.
By following the steps outlined above, you can set up due dates for tasks and receive breach notifications, enabling effective task management and timely completion.
We don’t have an option to modify the fields under Task section
We will not be able to re-order the tasks once they are added. While automating the task creation, the tasks are created in the order in which they are set up in the action block of the workflow automator.