Schedule some time, maybe call it a meeting on your work-wide-visible calendar.
This is exactly what I am talking about: a set of infrequent, mandatory meetings with most/all other comms on a high latency async channel.
It takes significantly more discipline for a PM to run things this way, but the reward is often better productivity and happier, less frazzled developers.
While this can work for some people, such "interruptible anytime" mentality may not be good for many workers. For example, when I am most productive I need to minimize, and ideally eliminate, disruptions. Such periods are short (2 hours at most for me), but I could do 90% of day's technical work in those 2 hours. If someone wants something, unless it is a blocker for a large team, I will put it away and get back to it later.
This has nothing to do with being remote or local, this is just the mode at which I am productive. I try to treat folks who work for me the same way: we can still meet daily in the morning I try to give them enough structure so I do not need to preempt them every hour. Things happen, there are failed systems that need to be fixed now and other fire drills, but I find most people in technology development more productive when on an async comm channel. I am.
Maybe I am just old and you youngsters do not need to do it this way :)