Because, you bring up sales, I am assuming that is your area of expertise. If a big sale can be unblocked by asking some specific employee an important question now, do it. If that happens five times a day, those sales are neither big nor are these very specific questions. Developers are most productive when in deep working mode. A simple question like "What time is it?" can be answered in 5 s, but it may cost a developer 30 min when in deep working mode. Because of the lost focus. On the other hand, many questions (not onboarding questions) could be answered by the colleagues themselves, if they would spend a bit more time on them. Thereby, they would learn more than just by getting the answer.
> Because, you bring up sales, I am assuming that is your area of expertise
I'm not in sales at all. Having an overview of the different bits of the business isn't a sales attribute. It's just an example of "what your job is" - which might range from weeks of uninterrupted detailed technical work at Microsoft Research, to presenting to clients, to running teams, to making technical decisions and getting agreement, to writing code.
Thinking every engineer's job is "writing code" and anyone who thinks wider is wrong is what the pushback in this thread is all about.