Disable call back from lockscreen

[GtrDude]

Is it really not possible to disable auto call back from the lock screen?
When I press any notification wahtever the app is, it always takes me to the app.
Not so with the phone app, press it and it calls back.
I have disabled Settings>Face ID and Passwords>Return Missed Calls and it still will call back when I tap the phone notification.

Any way to change this?
IOS 16.1.1 iPhone XS-Max

 

[usagora]

Not that I know of. You can either long-press it to give you the additional option of sending them a message, swipe left from the middle of the notification to access Phone notification options, or swipe left from the right of the notification to quickly dismiss it. The option you mentioned (Settings>Face ID and Passwords>Return Missed Calls) only applies when your phone is locked, which it won't be if you're looking at it (because Face ID unlocks it). That just prevents an unauthorized user of your phone from returning calls without unlocking the phone first.

What is your primary concern here? That you're accidentally going to call someone back?

Aside from disabling lock screen notifications for the Phone app, I'm not sure what else you can do unless/until Apple decides to give more options.

 

[addamas]

Check this?

 

[usagora]

Check this?

View attachment 2117242

As he stated, he's already done so. And as I explained in my reply, this isn't going to work for him because his face will unlock the phone when he looks at the screen . . . these settings in your screenshot only apply when the phone is locked.

 

[GtrDude]

What is your primary concern here? That you're accidentally going to call someone back?

Yes, that's it.
So annoying that this one app would be inconsistent with all other apps where when you tap the notification it only takes you into that app to to that email and nothing else, doesn't just automatically reply or anything.
In this case it dials the phone number automatically, then spammers and robo callers can see this is an active number.
It's not like that on Android, where on top of that you get a lot fewer spam calls to begin with, but that's another post...lol
All the notifications on Android do the same thing, should be like that with Apple too.
Be consistent throughout.

 

[usagora]

Yes, that's it.
So annoying that this one app would be inconsistent with all other apps where when you tap the notification it only takes you into that app to to that email and nothing else, doesn't just automatically reply or anything.
In this case it dials the phone number automatically, then spammers and robo callers can see this is an active number.
It's not like that on Android, where on top of that you get a lot fewer spam calls to begin with, but that's another post...lol
All the notifications on Android do the same thing, should be like that with Apple too.
Be consistent throughout.

I get why they do it (efficiency), but I agree that the user should be given more control here. And really, two taps (one to take you to recent calls and the another to call back a recent number . . . or just one "call xxx-xxx-xxxx?" confirmation dialogue) is not that less efficient unless you're just constantly returning tons of missed calls during the day.

But as long as your mindful of it, I don't think you should have too much trouble not calling people back, though it may occasionally happen if you get in a hurry.

 

[JM]

Yes, that's it.
So annoying that this one app would be inconsistent with all other apps where when you tap the notification it only takes you into that app to to that email and nothing else, doesn't just automatically reply or anything.
In this case it dials the phone number automatically, then spammers and robo callers can see this is an active number.
It's not like that on Android, where on top of that you get a lot fewer spam calls to begin with, but that's another post...lol
All the notifications on Android do the same thing, should be like that with Apple too.
Be consistent throughout.

Yeeeeeep. I’ve called back scammers twice now because of this stupid Lock Screen behavior.

EXACTLY because the phone app is the only notification that acts this way. All the others have one tap to expand or open the app. NOT act on anything.

 

[GtrDude]

But as long as your mindful of it

Those are the key words because you can never relax just go over your calls calmly, some calls you want some you don't, and you can never make a minor mistake and tap the screen a little weird and suddenly a spam call is being called back when you're going over your missed calls. All it takes is touching the screen wrong and boom now it's dialing a spam caller.

 

[Vlad Soare]

If I had one dollar for each instance when I inadvertently called back by touching that notification, I would be rich. I hate this stupid "feature". I get why Apple thought it would be useful, but it actually isn't. It's a bloody nuisance. It should be optional.

 

[ManuCH]

I hate this feature too and I wish they added a toggle to turn it off. I open notifications by mistake all the time when scrolling through them, but calls are the only ones that have a behavior I don't want.

I guess a working solution would be to remove call notifications from the notification center altogether and only rely on the badge on the app icon.

 

[usagora]

Those are the key words because you can never relax just go over your calls calmly, some calls you want some you don't, and you can never make a minor mistake and tap the screen a little weird and suddenly a spam call is being called back when you're going over your missed calls. All it takes is touching the screen wrong and boom now it's dialing a spam caller.

I don't believe I've ever inadvertently tapped a notification when I actually intended to swipe it. Just rest your finger on it and don't lift it off until you swipe to dismiss it. If there's still an issue, it sounds like the best solution for you is to remove lock screen and notification center notifications for the Phone app. Just use the badge notification and go over your missed calls directly in the Phone app.

 

[Vlad Soare]

I don't believe I've ever inadvertently tapped a notification when I actually intended to swipe it. Just rest your finger on it and don't lift it off until you swipe to dismiss it. If there's still an issue, it sounds like the best solution for you is to remove lock screen and notification center notifications for the Phone app. Just use the badge notification and go over your missed calls directly in the Phone app.

I didn't mean tapping the notification inadvertently. I actually tap it deliberately, with the intent to open the Phone app. it's only then that I remember that this particular one doesn't work like the others, and I start swearing.
Yes, I know this one behaves differently, but it's easy to forget. All the notifications open their respective apps when tapped. I tap them all the time. So when one of them does something completely different, I get annoyed. Building the entire OS and all of your apps in a certain way, then making a special one that does something completely different, is stupid to say the least. People form habits, muscle memory, they don't always want to think hard about each and every minor task they do every day.

 

[usagora]

I didn't mean tapping the notification inadvertently. I actually tap it deliberately, with the intent to open the Phone app. it's only then that I remember that this particular one doesn't work like the others, and I start swearing.
Yes, I know this one behaves differently, but it's easy to forget. All the notifications open their respective apps when tapped. I tap them all the time. So when one of them does something completely different, I get annoyed. Building the entire OS and all of your apps in a certain way, then making a special one that does something completely different, is stupid to say the least. People form habits, muscle memory, they don't always want to think hard about each and every minor task they do every day.

I was replying to the OP, who was referring to inadvertent tapping.

However, technically Phone notifications work the same way as Messages notifications do. When you click on a Messages notification, it opens the Messages app right to that message and you can immediately start typing a reply without tapping anything else. Well, when you tap on a Phone notification, it opens the Phone app and immediately calls that number, which is the logical equivalent of replying to a text message.

So the issue isn't Apple being inconsistent--they actually are being more consistent. The issue is obviously that a returned phone call can't (normally) be cancelled without notifying the other person that you tried to call, whereas a message reply can be cancelled without notifying anyone. But that's just the nature of phone calls vs. text messages. The only thing I can fault Apple for is--in light of this crucial difference in the nature of a phone call--not giving the user a choice for what happens when you tap on a Phone notification. I think the choices should be:

1. immediately call
2. confirm before calling
3. open recent calls

 

[GtrDude]

I didn't mean tapping the notification inadvertently. I actually tap it deliberately

i've done it both ways.
Happens all the dang time.
So annoying.
Apple should make this an option.
Be consistent throughout the app notifications.

 

[usagora]

Be consistent throughout the app notifications.

As explained in the post above yours, it actually is consistent; it's just the consequences of the consistency aren't always desirable 😉

 

[JM]

I hate this feature too and I wish they added a toggle to turn it off. I open notifications by mistake all the time when scrolling through them, but calls are the only ones that have a behavior I don't want.

I guess a working solution would be to remove call notifications from the notification center altogether and only rely on the badge on the app icon.

I think I may do this actually

 

[GtrDude]

I guess a working solution would be to remove call notifications from the notification center altogether and only rely on the badge on the app icon.

I like this. Good idea.
It's a workaround and Apple should give us options.
Thanks