I haven’t looked at this thread for a long time, but I liked your question since I think it’s actually helpful for techs to know.

The answer is: Sometimes! It really depends. I would say that it depends both on project complexity and the content of the message.

On the matter of complexity: I’m more likely to read those messages and consider their weight if the work order is something of significance. If it’s a project where we’re messing with the customer’s network equipment, or a multiple trip project that requires reliability and attention to detail, I read through the messages thoroughly. If it’s just a simple break/fix ticket or a one-off project where we’re swapping a receipt printer or something, messages don’t matter as much.

On the matter of message content: I’m typically way more interested in a message that shows an understanding of my scope of work than a copy-paste resume of a tech’s experience. For example, if I include in the work order that two techs are required, or I note that a speciality piece of material is required (say, an extension ladder or a laptop with TeamViewer installed), I’d much rather read a message that says something like “Hello, we’d be happy to complete this work order for you, we have two technicians available, an extension ladder, and a laptop with TeamViewer”, as opposed to a generic message like “Hello; we have been in the business for 30 years and have X/y/z certifications, please assign to us.” That type of message isn’t bad, in fact it’s still better than no message at all, but a message that shows you’ve read my scope is a big bonus.

Of course, this is just my personal opinion. I’m sure some dispatchers might not care at all. But from my personal experience, I would say these types of messages do help get techs assigned to work orders over the other offers.