Mh, for me it's a bit of a process of getting to know people, and to educate people how to get what they want from me quickly. Somehow that sounds arrogant.
The thing is, if people ask me a direct, simple question via chat, I can answer many things without even losing my train of thought. Something like "Hey where do I configure DNS records for XYZ" or "where in ansible is X" and such often get answered while thinking about other stuff. Some new employees are kind of hesitant because it seems rude to them to just poke me with questions like that straight up, but that's the getting-to-know part. I don't need cuddling, and tea, and house shoes, and comments about the weather if you just need some simple information.
Or, if they are unsure about the entire situation, be straight about it. Let me dig myself out of my hole, tell me the context you're in and then let's have a call and screenshare about the entire thing. I still prefer to know what this is about, because it allows me to prepare for a call, to make our call more effective for both of us.
But the thing is, those kind of ticks and preferences I have are a relationship thing with other employees. People just start polite and careful and might just be like "Hello" and such - developers write less, marketing writes more. Usually they just aren't sure how to approach me. So I can't really be to mad at them. Just answer with a funny smiley or a waving one when your heads context is switched to chat, their first message won't be business critical.
And the latter is another important point. We have escalation and communication channels and communication and escalation plans for different severities of problems. Someone saying "Hi" to me cannot be a critical incident by internal definition, so it has a few hours of SLA at minimum and might be forgotten at worst. If it was critical, our head of support would call me directly. If it was more than critical, our head of operation would call my physical phone.