Hey Connor, we have a perfect use case for this. We have a customer which requires us to liase with the vendor for diagnosis, after which, we will go down on-site to do the hardware replacement. I have a question here. In cases where we don't have the supplier reference from the "Log to supplier" action when we log the ticket, we will need to merge it manually right? Is there a better way to do this? We find that merging to be a little confusing especially when there's multiple tickets. E.g. Tech A logs to supplier and then when the supplier responds, it creates a new ticket, then when Tech B reads it, he would not know which ticket to merge it to.
We are in the UK and we use vendors, suppliers so far I understand provide raw materials and are deeply integrated into your supply chain. Vendor is someone you buy something and resell, and to me that is all our vendors like Microsoft, acronis, sentinel one, etc...
Great video! We've debated moving our vendor conversations to Halo away from personal emails as well. Any other downsides you see from doing that other than just getting the setup correct?
Put me on the spot why don't you haha! I mean, for basic vendor communication it's great, I'm obviously not aware of how you currently operate but it's fine for 1-1 communications.
Thank you for your helpfull videos. It helps us a lot for configurating our Halo environment. Is the Supplier Ref field a standard or custom field? I can't find it and I want to add it at a ticket type.
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
Hey Connor, we have a perfect use case for this. We have a customer which requires us to liase with the vendor for diagnosis, after which, we will go down on-site to do the hardware replacement.
I have a question here. In cases where we don't have the supplier reference from the "Log to supplier" action when we log the ticket, we will need to merge it manually right? Is there a better way to do this? We find that merging to be a little confusing especially when there's multiple tickets. E.g. Tech A logs to supplier and then when the supplier responds, it creates a new ticket, then when Tech B reads it, he would not know which ticket to merge it to.
Thanks for all of your videos. They have been extremely informative.
Thank you David
We are in the UK and we use vendors, suppliers so far I understand provide raw materials and are deeply integrated into your supply chain. Vendor is someone you buy something and resell, and to me that is all our vendors like Microsoft, acronis, sentinel one, etc...
Great video! We've debated moving our vendor conversations to Halo away from personal emails as well. Any other downsides you see from doing that other than just getting the setup correct?
Put me on the spot why don't you haha! I mean, for basic vendor communication it's great, I'm obviously not aware of how you currently operate but it's fine for 1-1 communications.
Thank you for your helpfull videos. It helps us a lot for configurating our Halo environment. Is the Supplier Ref field a standard or custom field? I can't find it and I want to add it at a ticket type.
Supplier Ref should come when you add the field 'Supplier' this is a system field not a custom field :)
Promo'SM