12 October 2020. Answer. @Moose70. Thank you for reaching out. Caller ID name can only display wireless callers with Cricket service. Remember to always mark posts that resolved your issue with Accept as Solution. You can even mark multiple posts in a single thread. This will help other users find this information too!
Thank you in advance. HI, I just spent a fun 45 minutes with a rep then a supervisor at what Cricket calls customer service. The best that Cricket can offer us is to put "Wireless Caller" in our outgoing Caller ID, even though they list Caller ID as a "feature" of the basic rate plan. Extremely poor service.
Anybody who calls from cricket is identified on the caller ID as a "Wireless Caller" and not with their real name. 1. Continue this thread. View Entire Discussion (5 Comments) More posts from the NoContract community. 92. Posted by. u/MR_CoolFreak. 12 days ago.
How do I turn on Caller ID on incoming calls? To display the caller’s identity on your phone’s call screen, dial *234#. To check whether your phone is set to display the caller’s identity, dial *#234#. To hide the caller’s identity on your phone’s call screen, dial #234#. Note:
Call Cricket Wireless (or chat) and have them change the outgoing Caller ID Name. EDIT: Even better, contact their e-mail support people at email@example.com with your request. Include your phone number, Cricket account # and security PIN in the email with your request.
Ready to change your number? Call 1-800-CRICKET (1-800-274-2538) or chat with Customer Support.
jeff1f1racer. · 1y. Unfortunately, this is normal for Prepaid carriers. You may turn off outbound Caller ID so it’ll say Unknown instead. Typically, it’ll show the name of a prior subscriber to the number. 2. level 2. Firexxik.
The problem that I'm trying to get addressed is not with a Cricket Wireless customer's outbound caller ID, it is with an incorrect inbound caller ID from one of our phone customers to a Cricket user. I really don't expect to have this resolved by customer support at this level- this is a NOC or operations problem with the cached CNAM database ...