Freshservice has been in use at our company for more than five years. We have made several attempts to integrate tasks, but ultimately moved away from them due to the following drawbacks:
-
Limited Dashboard Integration: Reporting and visibility within dashboards are very restricted.
-
No Requester Interaction: Direct communication with the requester is not possible via tasks.
-
No Unique Task URL: Tasks lack a direct, shareable URL for easy referencing.
-
Agent Adoption & Visibility: While our agents are highly proficient in managing tickets, tasks are frequently overlooked. This leads to delays as they are not processed as timely as standard tickets.
Consequently, we now rely on sub-tickets automatically created via webhooks.
Our requirements would be best met if workflows natively supported the creation of sub-tickets in addition to tasks and notes.
