Cannot make outgoing call using Be Anywhere Feature

Hi there, thanks so much for taking the time to reach out to us in regard to your be anywhere feature concerns. We are more than happy to help get this resolved for you. Can you please send over a private message with your name, the full address, and phone/account number? 

Before you send the private message, you did follow this link https://business.comcast.com/help-and-support/voice/manage-be-anywhere-settings-for-business-voiceedge to make sure all the settings were correct from your end? 

Yes, I have done all of those things. As I said, this worked fine until about a week or so ago. Then something changed and it stopped working. 

I'm new to this forum. How do I send a private message to you? 

Good evening, and thanks for taking the time to reach out to us tonight. I'd be glad to look into yourservice issue for you. Can you please send me a PM with your full name, and address including city, state, zip code exactly how it reflects on your bill? –Rob K.

Hi Steve! Thank you so much for your patience. I see that you were previously working with my colleague via private message. My name is Gabriel and I am with the corporate Digital Care team and I would like to help with the Be Anywhere feature from here. Would you mind sending this handle a private message with the affected TN so we can further assist? -Gabriel

I too am also not able to place outbound calls from my cell using Be Anywhere app feature. The call initiates. The "number you won't recognize" appears, then it won't connect. If I need to PM you, could you also explain how to do that? Thanks

Thanks for taking the time to reach out to us through the business forums. I know how important the phone service is to your business and I would love to get to the bottom of this with you. Can you please send a private message by clicking on my handle and messaging directly with your first and last name, full service address and account number or phone number? 

If you have your caller ID blocked, you will not be able to call through the Be Anywhere feature. I finally found a representative who knew what he was talking about and told me to turn off blocking caller ID and then it worked fine. That is because Comcast needs to now verify you are making the call from a valid mobile number you have designated on their system (to stop others from making calls through your number).

Hope this helps. Good luck.

Thanks so much for taking the time to reach out to us regarding your be anywhere services. I very much appreciate your patience and greatly apologize for the delay in our response. I know how important the services are to your business and we want to do all that we can to assist. I would love to get to the bottom of the outgoing call issues. I cannot even imagine the strain to your business during this time that this feature not working is having. Can you please reach out through private message with your first and last name, business service address and account number or phone number? 

Mine is working OK now. One thing - I didn't realize that when the "number you wont recognize" appears, one has to click on that button for the call to proceed.  When I do that, the call usually goes through. Sometimes I still get the error message you had, and in that case logging out, quitting the app, and logging in again usually works. Good luck!

Wow, so this issue has been going on for over 9 months! Comcast....get it together please. I know you're a monopoly but that is no excuse. When you do have competition you will lose everyone because your service and products are so POOR 😐

Thank you so much @AndrewLC. We had this exact issue and now it works. I couldn't find where that number came from, but googling made me think they are some sort of "reserve" that comcast uses to bounce the calls? I guess the app has trouble initiating via the number on the mobile, so it must first initialize via that random number. So strange. Thanks again!! Much better help since all Comcast did was give me a ticket and send it up. It seems they also had no idea this is happening...