No local user-override for Live Caller Id Lookup?

Question

Created Jul ’24

Replies 2

Boosts 0

Participants 2

If an app has a Live Caller ID Lookup extension and the lookup server indicates that a caller is identified and not blocked, then if the user wished to locally block that number they can do so either via the iPhone call block button, or via the app's Call Extension block list.

However there's apparently no way for the user to do the inverse. i.e. if Live Caller Id Lookup indicated that a number should be blocked, then how could a user indicate they don't want that number blocked for them?

If they added it to the Call Extension as an identified number, but live lookup is saying the number should be blocked, then what does the OS do? Give priority to the blocking instruction from the live lookup server, or give priority to the fact its in the Call Extension's Identified list?

Answered by Technology Evangelist in 797162022

Hi there!

Being able to provide user feedback about blocked calls isn't something that is currently possible, but we'd love to capture that as feedback. Would it be possible to create a feedback report detailing your use case?

If they added it to the Call Extension as an identified number, but live lookup is saying the number should be blocked, then what does the OS do?

The system would query both, and would block the call. As a result, it would appear in "Recents" as having been blocked by the extension. However, if someone were to create a contact from the recent call, it would be identified and the name would be automatically supplied.

Boost

Answer 1

Technology Evangelist OP

Apple

Jul ’24

Accepted Answer

Recommended

Hi there!

Being able to provide user feedback about blocked calls isn't something that is currently possible, but we'd love to capture that as feedback. Would it be possible to create a feedback report detailing your use case?

If they added it to the Call Extension as an identified number, but live lookup is saying the number should be blocked, then what does the OS do?

The system would query both, and would block the call. As a result, it would appear in "Recents" as having been blocked by the extension. However, if someone were to create a contact from the recent call, it would be identified and the name would be automatically supplied.

0

Answer 2

mungbeans OP

Jul ’24

Hi,

Submitted a feedback report as FB14539432.

FYI the use case is "The use case for this is if a Live Caller ID server has marked a number(s) as being blocked (due to them being indicated as being malicious, spam etc.) but an individual user wishes to ignore that and permit the caller to ring. (The user could do this by adding the call as a contact, but they may not wish to pollute their contacts this way, if adding the number as identified to the Call Extension enabled the call to ring, it would mean the application can override the server's blocking indication on the user's behalf)."

0