Mikester wrote:
Hello Priya
Thank you for the response!
What I mean is, that when a technician goes to a store and have to assess or repair more than 1 item it becomes challenging. We have a dependent field property that can accommodate 1 item, but this is not enough for stores. So, this means that the technician has to record the item information in a free text field. When he returns to the depot, someone else then has to capture the items into our system. As you can imagine, this is not very productive as two people are doing the same work.
Hope this makes more sense?
Hi @Mikester .
Thank you very much for clarifying this.
Your scenario suits what Priya suggested:
FreshDesk is currently more targeted to Help Desk.
But FreshWorks have another solution called FreshService.
With this, among others, you can have Service Request, and these SRs can be created with several items, and you may have status by every independent item. For instance, you have SR-01, with Item 1, Item 2 and Item 3, and have Item 1 Delivered and Item 2 and 3 in Process, and when all items are served, you can Resolve/Close your Service Request.
Your use case seems more like using FreshService instead of FreshDesk, or using both depending on your scenario, which can be integrated.
I also suggest to contact your Account Manager in order you can have more details about it, and even get a demo.
Sincerely,