Activation Issues

Nuvo Support ask me for my number 000. Then I never hear back. Working on it I guess

I had the exact same feeling as you did. Then, many hours, if not a day, later, service was restored without further communication. I'd wait for now, & maybe email support again to just as a friendly reminder in case yours fell through the cracks.

Did u have to try prl update or did it just start working by itself .thanks

@Mark

No PRL update or anything was done to the phones. One phone just started working, then a few hours later, I checked the other 2 phones, & they were working when I checked.

If your ESN / MEID / IMEI shows on Ting BYOD that it's activatable on Ting's CDMA network, then chances are there's nothing you can do to get your phone working on CellNuvo/RedPocket with your original CellNuvo line. You should just send polite email, a "just in case my line fell through the cracks" email.

On the other hand, if your ESN is not activatable on Ting's CDMA network, then check to see if your phone works. If not, try updating PRL & Profile, or simply dial ##72786# (or your device's equivalent for a network reset).

Ok ty. It shows it will activate on ting and tello

@Mark

Probably no comfort to you presently, but in an email communication to me this morning about recovering the original phone numbers, CellNuvo support implied that they're still working on service issues, saying "We are in the process of providing services to all who have been affected first and foremost. We will be addressing specific phone numbers and account details very soon."

That's the same response CN support has been giving out regarding recovering phone numbers as of Friday last week (I received one that said that then). Really hoping for a development on that front soon....

The SOON word always seems to come up with cellnuvo. But very soon? I wonder how long that implies???

"I wonder how long that implies???"

The term "soon" as used here is devoid of meaning.

What is meant is "we do not know when, and while not saying that directly expect you to understand the term in that way."

While I have no personal knowledge of CellNUVO, I have seen this approach used countless times.

If CellNUVO had some specific information to convey, it would do so.

Sometime in the future lolo

Or near future

That's a great summation Oldbooks1.

My LG X charge is arriving tomorrow so the wait is 2 business days. The charge was $1 + tax for the device + the first month of taxes for cell service.

The Virgin sim seems to be about 4 days from order to delivery. However, there is no charge for the sim itself. The $1 per year + taxes are charged once you activate.

And as is frequently the case, it is probably not possible to define "soon" in concrete terms. There is a different issue on the front burner (getting phones at least active with a temporary number), and "soon" can't take place until after that unknown period has been completed.
So, 'soon' is the most accurate answer than can possibly be given, and the answer we should expect. It makes absolutely no sense from a company viewpoint, or from an individual viewpoint, to commit to a timeframe that can not be reasonably predicted. There is no winning side from attempting to do so.
The only 'more concrete' answer that would make logical sense, is 'we will address the issue of number recovery as soon as we have successfully addressed the issue of restoration of service with temporary numbers for all of our customers."

Mark,
I'm wondering too.

Not to mean anything negative, but this thread in many places perfectly illustrates the P.R. peril that a service provider would put itself in if it were to provide updates, for any update provided is bound to be met with barbed responses, justified or not.

The sooner the better.:unsure:

I take a different perspective, both on the facts and the options.

In the first instance, the company has put in place a specific set of arrangements with Red Pocket--that is how users currently have service. There are clear contractual terms associated with that arrangement and the company has not shared them with users. Clearly, whatever Terms of Service users agreed to when joining CellNUVO have been fundamentally modified and the exact nature of those modifications has not be shared with the users.

In addition, it is unimaginable that CellNUVO does not at this stage have an understanding of the scope of the task ahead. If it does not, then the situation is truly dire. An integral component of that assessment is a listing of tasks to be completed by priority order and the expected time frame for completion. Factors that could lengthen the process are also known. To reject this hypothesis means accepting that the company after 12 days of outage has no coherent strategy to resolve the outstanding issues. That is certainly possible, but seems exceedingly unlikely and if it is true then there is genuine cause for concern.

Here is what an orderly process of communication would have looked like:

On Friday August 25, 2017, the company would have explained what actions have been taken and the nature of the Terms of Service that are currently in force. It would have indicated specifically what its current capabilities are by stating whether it could or could not support ports, could or could not effect device swaps, could or could not address individual concerns, etc.

On the same date it could have outlined the remaining steps in the process, which might have included further planning, acquiring additional resources or support from partners etc. At that point it could have sketched out the issues that remained on the user side, the sequence in which they would be addressed, the time frame in which is was hoped to complete them, the possible complications that could arise, and the schedule for providing updates.

That would have been a transparent, effective, and appropriate way to provide the information needed to users so that each user could make an informed decision on how to balance the pros and cons of the choices available.

Well-managed companies follow this type of procedure in circumstances of this type for a very good reason--it addresses the principal concern of users which is having official information that allows the appropriate management of expectations. It also builds good will and promotes the image of a transparent and effective operation.

What has been done instead is to leave users to speculate for themselves as to what may or may not be happening. The result is the countless postings that have arisen in the past 12 days with the run rate at 4 time the average daily volume in the forum. While the postings may have afforded some emotional relief, very little has been learned about the actual situation since the discussion is among users who have no information other than what their device indicate. Such postings as have been made by CellNUVO have simply exhorted users to contact the company for information. Many members have reported the outcomes of such contacts and no substantive information has resulted from that process.

There are effective and ineffective ways to manage unanticipated major problems. The approach followed so far does not comply with the protocols of the known effective methods. That is the company's choice to make and nobody has any right to question it. However, to suggest there is no other choice or that is an optimal choice is simply not accurate.

To give a concrete example, I manage a device that has had no service since August 18, 2017. I am not prepared to leave it without service indefinitely and so I am forced to make a decision (essentially flip a coin) as to whether to continue to wait or to move it elsewhere. If I had even a tentative timeframe from the company, I would be in a position to make a better decision that I am at present. In explaining this, my point is not to complain--I fully understood the risks in managing an account on CellNUVO. However, the company could, should it choose, enable me and others in that situation to make a more considered decision. Of course, CellNUVO is not required to provide that information to me, but it could if it chose to do so.

Yep, right with you Isamorph.

My comments below are specifically related to the concept of offering a concrete timeline. I agree that a lack of communication about a lot of issues is a problem.

"To reject this hypothesis means accepting that the company after 12 days of outage has no coherent strategy to resolve the outstanding issues."

I most definitely reject the hypothesis that having a coherent strategy implies in any way that it is possible to offer a concrete timeline instead of "soon" I also reject your apparent hypothesis that not being able (or perhaps willing) to provide a firm date implies that there must be no coherent strategy.. The 2 are not fundamentally the same, and do not need to be tied together.
.
I don't know if you work in an industry where unexpected technical issues that require the cooperation of multiple vendors and/or entities to solves is an issue. I do work in such an industry.
Even when I have a clear strategy, and a 'drop-dead' target date, I'm still at the mercy of any one of those other entities or vendors giving me a reply of 'soon' when I ask for a concrete timeline. As soon as that happens, my only possible timeline becomes "soon", unless I can be prepared with a contingency plan for every possible scenario that precludes the possibility of 'soon' as an answer. .(In fact, I do work in these scenarios all the time, with back-ups for back-up plans.) No matter how drastic my need or expectation is, it is not realistic to assume that every other vendor or entity necessary for the project agrees with the priority of my project over other projects also on their plates.

I just received the "out of data" message from Red Pocket on my phone. Does anyone know how we're supposed to go about checking our CellNuvo account, now that it's partnered with Red Pocket? Do we (should we-or should I wait until after Friday when hopefully our numbers will be restored and/or get a service update from CellNuvo ) go onto Red Pocket's website and create an account?
Thanks,
Seh-hee