I would agree that sometimes a call or videoconf is necessary (which should be scheduled for only as much time is as absolutely necessary and the output of the meeting well documented), but it's good to flex the remote/async muscle to encourage communications best practices across an org. Communicating is a critical skill.
A lot of folks are used to being lazy intra communications in an org, and imho, that shouldn't be an excuse to dissuade remote work when the benefits are incredibly clear. If you suck at comms or management in a more flexible work arrangement environment (which is okay! to get better at something you must first suck at it), it's time to get better.
The scheduling is a pain point now though. I'm blocked until I can get a slot in your diary, which could mean I'm blocked for hours. And that's if you even accept my invitation or don't get delayed by something else.
Maybe a drop-in thing could work, like Clubhouse. But then that's kinda invading your privacy if you have to stay on that.
Your pain point is valid, I want to make clear that I'm absolutely not minimizing it, but I have worked remote for almost a decade and I want to stress that it can be solved (as long as you're operating in a competent organization) and it pays off to solve it. There are many technological mechanisms by which to solve this, but it's primarily an organizational and cultural challenge.
A lot of folks are used to being lazy intra communications in an org, and imho, that shouldn't be an excuse to dissuade remote work when the benefits are incredibly clear. If you suck at comms or management in a more flexible work arrangement environment (which is okay! to get better at something you must first suck at it), it's time to get better.