"V" ON MY BUSINESS CALLER ID

Hello @MYWEIGH

Thank you for your recent posting, we appreciate your participation within the Business Community. I will be glad to assist with your concerns. Can you please provide your account details and contact info so we can get started. Thank you, Lisa

FISCHER WEIGHING SYSTEMS  ACCT# 117214413

MARC FISCHER

561-748-1599

Marc, sorry to hear about your caller ID display issue. I will be glad to assist. What would you like the caller ID update too? Please let us know when you will be free and provide your best contact number just in case my team needs to speak with you. Thank you, Lisa

as mentioned in the original post "Caller ID displays a "V" instead of the actual call id name".  if that's an update, is there a cost to that?  it used to work when we did the original digital upgrade. my analog coreless phone (AT&T Brand) shows the call id name after the  first ring.  i would like that also on the business phone's display.

561-748-1599

Marc, so you would like for the business name to display or the number? I will have my team look into getting this corrected. -Lisa

i would like the name - business or personal  to display on all IN coming calls.

Marc, thanks for the info. I am reaching out to my team. I will follow up with you shortly. -Lisa

thank you

Marc, my team was able to correct the caller ID info. Please check it out today and tomorrow and let us know if it shows correctly. I will follow up with you tomorrow. -Lisa

still get the "V" on the phone display.  does it take time to activate.  like i said before, my portable phone on line 1 works fine.  just not on my system phones.

Hello, the team stated it can take sometime see by tomorrow if it fixed if not we might have to put in a report ticket. Thanks, Lisa

will do - thanks 

Hello, please let us know if the caller ID is correct at this time or do we need to escalate the case. Thank you, Lisa

still getting a "V"

Hello, sorry to hear this which line are you seeing this on? We will have to port a work order in for this issue. The team stated they fixed it but seems not to be the case.