Forum Discussion

AMO's avatar
AMO
Newbie Caller
3 years ago
Solved

Enhanced Caller ID

I am unable to enable enhanced caller information on my galaxy s21. I keep getting the message an error occurred while trying to start Enhanced Caller Information. I have tried the solutions I saw posted, removing the SIM, clearing the data, and reinstalling the app. Nothing worked. Any additional suggestions?

Thanks

  • After weeks of working with T-Mobile to resolve the issue, their answer is the “feature” has been moved to the Scam Shield app:

    Hi Xxxxxxx, Thanks for reaching out to T-Force and sorry to see you've had ongoing issues with Enhanced Caller Information feature. I was having a difficult time finding really any information on our side for that feature- and believe i found out why, which would also appear why it's not working for you.

    Enhanced Caller Information (ECI) was actually rebranded to Verified Business Calls (VBC) and this rebranding was right around a year ago. With the rebranding to VBC, this feature can be located and managed within the Scam Shield App by following the instruction below.

    Open the Scam Shield app. Tap Settings. Tap Verified Business Calls. Click toggle to turn on. If contact permissions are not enabled, click Go to Settings to allow permissions and click Got it. Toggle will be magenta color to indicate VBC is turned on.

    Additionally, VBC is pre-enabled on some Android devices. If it is a pre enabled feature, you can mange it via your on-device settings below.

    Open the native dialer app. Tap Settings. Tap Verified Business Calls. Click toggle to turn on. ^XxxxxXxxxxxxxx

  • robbadob's avatar
    robbadob
    Network Novice

    Same here. Exact same problem with same phone GS21, and same error message. 

     

    Samsung has a similar feature built-in to this phone -- maybe it's that feature interfering with this app? I forget what Samsung calls it. 

     

    I think I'm just going to leave TMobile Enhanced Caller Protection OFF and use the built-in Samsung version. But you could try disabling the Samsung feature and then rebooting/reinstalling. Might fix this issue?