Phone calls don't fit neatly into this scheme because they demand a lot of attention, but it's easy to get out of one if you realize it's not something critical. I generally pick up and the moment I get the slightest whiff of spam, I just hang up.
A 15 second phone call probably goes straight to my voicemail and there's no read receipts if I have read the voicemail transcription yet, much less tried to listen to it. It might be hours until I'm in a quiet enough space to try to listen to it, because I don't carry headphones with me most of the time, don't listen to speakerphone in public, and the "phone speaker" on an iPhone is generally hard to hear for me, no matter how I awkwardly position the phone. The transcriptions are usually not good enough to action directly so I do usually need to do that dance of find a way to listen to it. Calls to me are a UDP hole with fewer acknowledgements and a lot of inconvenience.
Unless you've prescheduled a call with me, in which case maybe I do answer and maybe it is quick enough to be a 15 second phone call. But the easiest way to schedule that call with me is going to be to text me "Hey can I call in an hour about X?" and I'll ACK it soon after, and probably then likely spend 45 minutes looking for a quiet place to take a private phone call.
But, yeah, different perspectives for different sorts of people. Phone calls are taxing to me and the real world is a loud place and I don't carry headphones and I like to control the environment in which I try to answer a phone call, but also I find finding such quiet environments stressful enough to want to schedule them ahead of time.
If it is an emergency, it is a voice call. It is both immediate and conveys urgency. If it is something that you need to talk through, it is a scheduled voice call. Asynchronous communications may demonstrate respect for a person's time since it does not (need to) interrupt them in the moment, but the inefficiency results in a disrespectful waste of time for bidirectional conversations.
If it is something where you need a simple response by the end of the day, it is a text. If it requires a lengthy response, email. Never expect a lengthy response by the end of the day, or for it to be handled on devices with terrible input methods (like phones).
Anything that isn't covered by those scenarios will be largely dependent on the person.
I think even for emergency situations the relationship between voice calls and text messages is flipping. Text messages are immediate and can convey urgency. Phone calls are for private, quiet spaces, which take time to find (or schedule). With the death of the private phone booths in public spaces, phone calls are inconvenient to take almost everywhere now outside of one's home, but urgent text messages can be read and even acted upon just about anywhere.
Phone calls have so much ceremony and ritual and take so much time to play phone tag, and every single part of that, especially the phone tag, has gotten so much worse because of spammers. Phone calls just don't feel reliable anymore. It's easier to assume you are more likely to hit someone's voicemail than reach them many hours of the day. It's easier to assume people don't even check their voicemail in some cases, because they expect a text message if it was important.
If it is an actual emergency, I need to know that they have received the communication in real time. I'm never leaving someone a voicemail in an emergency situation.
In an emergency, I can often text 15-20 people in the time it takes to try to get a phone call through to a single person. (Especially with the multiplying effects of copy and paste and group chats.) I'm still probably going to follow up with a bunch of people by phone calls after the texts go out, but most of that will be by request ("can you call me when you get a chance?" texts) for details or shared emotion bonding after the key points are already distributed (and possibly some emergency conditions better).