Connor, thank you so much for making these videos. We're evaluating HaloPSA and all of your videos have been so helpful to give us an idea of what HaloPSA would look like for different use cases.
Great video. Real world examples would be helpful and more relatable. I agree all MSP do things different, but I also believe there is a lot of things we do the same.
Can we add "Customers" as companies and not as single users? If so can we set up rules that, when new tickets are automatically created by receiving support request via email, are assigned under the customer (company) previously registered? Thanks in advance.
Hi Alessandro, You build HaloPSA however you desire honestly. You can even rename Companies to Customers if that terminology better suits you and the business.
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
Connor, thank you so much for making these videos. We're evaluating HaloPSA and all of your videos have been so helpful to give us an idea of what HaloPSA would look like for different use cases.
Great to hear!
Great video. Real world examples would be helpful and more relatable. I agree all MSP do things different, but I also believe there is a lot of things we do the same.
You've explained this all perfectly, thank you so much!!!
Our pleasure :) Thanks!
at 5:10 You mentioned that you remove showing the workflow in the Ticket Info section. Can you let me know how to do this?
Really enjoy your videos, and well done you have really made a good conscious decision to slow down a bit :)
I try so hard :( haha! Thanks
Can we add "Customers" as companies and not as single users?
If so can we set up rules that, when new tickets are automatically created by receiving support request via email, are assigned under the customer (company) previously registered? Thanks in advance.
Hi Alessandro,
You build HaloPSA however you desire honestly. You can even rename Companies to Customers if that terminology better suits you and the business.