Note to Lucky Mobile, Bell Mobility, and other communications or tech services who think they can get away with support services that do not provide any actual support: do not annoy and ignore grieving widowers. They are already mad at the world, and they have an awful lot of time, and no restraining influences to prevent them from doing the most detailed and damaging review of your so-called services.
When Gloria died, I had this spare cellular phone. I quickly realized that I didn't want to simply use it as is: it irked the girls, and there was too much danger of accidentally calling the grandkids, and freaking them out with calls or texts from their dead Grama. At the same time, my baby brother, who had had a side business selling SIM cards for travellers, and knew a thing or two about the rates and services of the various mobile or cellular service providers, told me about Lucky Mobile, which you could get by buying a SIM card at Dollarama for four dollars, and signing up. He suggested the $25 per month plan, which provides for unlimited (no long distance) voice calling across Canada, and unlimited SMS texting to the United States and around the world. (I haven't tested the international texting part yet, but possibly by the time I've finished this review.) So far, the Lucky Mobile cellular service seems to be working fine calling across Canada. (They have a "refer a friend" program, so, if you want to try it out, let me know and we'll both get a discount.)
Now, my baby brother doesn't have any friends in the United States, and so he hadn't looked into the costs or capabilities of calling there. But I *do* have lots of US contacts, so I tried to find out how much it would be to call them. I couldn't. Lucky seems to have a number of long distance calling plans, but they all seem to be for the Philipines, or Hong Kong, or other distant regions. None covered the US.
When searching through the Lucky Mobile site, I saw mention of a "Lucky Community Forum," so I went on to that. Searching for US calling found a question that mirrored my concern. A couple of replies simply echoed that issue, but one merely contained a URL. The URL was to an app in the Google Play Store. The app, variously called the Lucky Wi-Fi Calling app, or Lucky Wi-Fi Talk & Text, promises, if you are in a location with wifi service, that you can place unlimited voice calls and send (and receive) SMS texts anywhere in the United States and Canada.
The process has multiple steps, but is not too terribly complicated. You download the app from the Play Store. Then you install it. During installation it asks you to set various permissions, all of which seem to be reasonable. (The only one that might cause trouble is the one that asks for permission to appear on top of other activity on the phone, which would be required for receiving calls. When this permission is requested, you have to "back out" of the permission screen in order to continue the installation process.) At one point in the installation process, the app asks that you provide your Lucky Mobile cell number, and they then send you a code that you enter in order to prove that, yes, you do actually have a Lucky Mobile service plan. The system then gives you a choice of five phone numbers, which, once you have chosen one, becomes the number for your wifi calling service. It works fairly well, and uses your contacts list on the phone. (Although, the first time you try it, it says you have no contacts, and you then have to give it permission to read your contacts. It might make sense to make this part of the installation process, rather than making it a separate process.)
The wifi phone, or "softphone," as it would more generally be known in the VoIP world, seems to work fine. I've made numerous calls with it in the course of testing and retesting during the period of this review, both to Canada and to the United States. You can call landlines, cell/mobile phones, and even other softphones. There have not been any particular problems. The softphone even works well with incoming calls on the smartphones own cell phone system, and you can take a call on the cell phone, deal with it quickly, and return to the softphone without any problems. The one issue that I have noted, is that the softphone, unlike the cell phone, does not blank the screen during the call. This means that, since the screen is *always* the biggest power draw on the smartphone device, regardless of what else is going on, Lucky's Wi-Fi Talk and Text is a real power hog, and will run your battery down quite quickly. I estimate that about two hours of wifi calling, on my phone, will run you from 100% to dead.
Actually, the code doesn't quite prove that you have a plan with them. I have the two phones, so I installed the app on both, and it did install on both. When I entered the Lucky number [hmmmm] on the second phone, it "remembered" that I was registered, and so gave me the same number. Fair enough. As far as I can recall, when I started testing the wifi calling service, it worked fine on both phones. But then it didn't. And that's when the support hell started ...
First off, one phone seemed to stop working. It suddenly starting showing that it was "Unregistered," but there was no explanation of why, or how to re-register it. My first reaction was, fair enough. They don't want you to have two phones using the wifi calling service if you only have the one mobile plan. But I was interested in how to switch back and forth between the two phones, even if I could only use one at a time.
Support for Lucky Mobile seems to be limited to the various simplistic pages that they've put up on their Website, and a text chat function. In terms of the Lucky Wi-Fi Calling app, there is one page that explains the installation process, and provides a little bit of explanation of how to use it. That's it.
So I tried the text chat function. This is painful. First off, you are answered (eventually: the system seems to be pig slow, and that's probably not fair to pigs) by a bot. It asks you, in different ways, mostly about marketing type issues: do you want to activate a new phone, do you want to upgrade your service, that type of thing. Eventually it asks if those lists of options were helpful, and, when you tell it no, it finally offers to connect you with an agent.
Well, it *might* connect you with an agent. Most of the time (so far I've made eight calls through the chat function) you get put on a sort of hold waiting for the next available agent. This is an interesting exercise in trying to figure out how many agents there are, and how many customers are calling in at any given time. The hold function seems to keep some activity going on the chat line, and sometimes tells you that X people are ahead of you in line. But, once you are actually interacting with an agent, you get a lot of canned responses, and the agent seems to be distracted, and I wonder how many customers a given agent is interacting with at any given time.
It's actually difficult to tell when you've got a live agent, and not a bot. The agents obviously have a script, and boilerplate responses to use in a variety of situations. Over the number of calls I've had to make, it strains credibility that so many different agents would, in similar situations, use *exactly* the same text to tell you that, for example, they are going away to check something but that you should stay on the line, or that, "I can help you check the best option for that."
It's also an exercise in frustration. You can wait a long time for an agent to finally acknowledge you. But if you don't acknowledge right away when they do, they drop the call. And it's not easy to get back into the chat when they drop the call. You basically seem to have to sign out of the system and back in again to be able to do so. And then you are dealing with the bot, and then you have to wait, and then ... Of the eight calls I've made so far, three terminated at this point. Two terminated prematurely after I started talking with an agent because of a server failure or disconnect (and, of course, nobody ever calls back). Two finally got punted to the next level. The next level is Bell's first line support, and two of my calls got through to that point, but were then terminated prematurely by some failure without resolving the issue (and, of course, nobody ever calls back on those, either). At this point, the issue is still not resolved, but I have finally been punted to Bell's *second* level of support, and, supposedly, somebody is going to call me back. (Some time in the next three days.)
Over some of the calls, the agent asked me to uninstall and reinstall the app, and to reboot my phone. This got to be interesting. Normally, on an Android phone, when you want to uninstall an app, you go into settings, select apps, select the app you want to uninstall, and select or click uninstall. This doesn't work with the Lucky Wi-Fi Calling app. If you do it that way, the app will disappear from the apps list under settings, but it is definitely still installed on your phone, and can be accessed in a variety of ways. I was beginning to wonder if I was going to have to blow the whole phone off. However, if you look into the Google Play Store app, and access your own account, and, under "Manage your apps and devices," find the list of all your installed apps, you can then select the Lucky Wi-Fi Talk & Text app and *successfully* uninstall it that way. (But this is definitely strange behaviour, and a *very* good reason to install the app via the Google Play Store rather than directly from Lucky.)
In the meantime, the Lucky Wi-Fi Talk and Text has gotten flakier. Now *neither* phone will send SMS text messages. A large red dot, with two curved white arrows on it, also now appears on the screen. (It was also there when the first phone "unregistered," so I can't help thinking that it has something to do with the problem. But it isn't active, and there is no indication of what it is or what it is supposed to be indicating. I keep offering to send people screenshots of it, but Lucky's first level support and second level support [Bell's first] keep saying that they aren't allowed to receive email.) (When I eventually started posting about this publicly on Twitter, I did have a conversation with someone at Lucky through Twitter DMs, and sent it via that. Supposedly this has now gone to Lucky's third level support [Bell's second].) By this time I had confirmed that at least US text messaging is available with the original Lucky Mobile cellular plan that I have (still haven't confirmed international SMS texting), so by now this is no longer about a communications requirement, and has simply become an exercise in determining just how bad Lucky and Bell's "support" actually is.
I haven't yet made contact with Bell's second (Lucky's third) level of support. They may be trying to contact me: my home number's answering machine (I told them to call my home number, since they only wanted one number to call) recorded two blank calls while I was out on an errand yesterday morning, and another while I was out for my doctor mandated walk in the afternoon. However, no message was left in any of those calls, so I doubt they were from Bell.
Posting a question or issue on the Lucky Community Forum seems to be a useless proposition. I did not receive any help via that route. Because of duplication in my replies, as I posted my query under various other queries that seemed to be related, the moderators almost instantly responded by deleting some of my posts, and moving others, but no answers or help were provided. Because I followed up with additional details, as I found out more, the system sent me an email asking me to accept one of my followup posts as an "accepted solution," which makes no sense at all, except to a bot. (Which seems to be what most of Lucky Mobile's support is run by.) (The email came from an address which, of course, is used only for sending out this type of spam, and does not receive replies.)
By the way, when I posted this review to the Lucky Mobile Community Forum, it was *IMMEDIATELY* marked as "spam" (and so, presumably, made unreadable by their users).
About a day later a moderator did post a reply to one of my queries, asking if my phone software was up to date, and asking me to accept that as a solution. I had, of course, already done this, and much more in regard to the uninstalling and re-installing of the app, and rebooting the phone, and, no, it didn't solve the problem.
At this point in the saga, there is a bit of a delay. I don't know what was happening on the Lucky or Bell side, but, on my side, I had to get some other work done, and spent an absolutely horrible day doing accounts (which is another story). So I was not pursuing Lucky or Bell about the problem. I did continue testing the Lucky Mobile cellular plan that I was on, and confirmed that texts to and from US and international cellular/mobile phones and numbers did happen, and generated no extra charges.
As previously noted, I had, through dint of persistence and multiple attempts, been able to get to the third level of Lucky support, the second level of Bell's support. I had been given an escalation number, and some contact numbers if they did not call me back. However, my public postings on both Twitter and the Lucky Community Forum had also sparked interest. In both cases I was contacted privately (Direct Message on Twitter, and the private message function on the Lucky Community Forum), asked for additional details on myself and my plan, and promised that the problem would be escalated to a higher level of support. In the case of Twitter, the person contacting me was aware that I already had an escalated call open: in the case of the forum, they did not seem to be aware of this. I have frequently found, with companies facing the retail market, that posting the details publicly is an effective way to get attention for your problem.
(I might also note, as an interesting side issue, that the base software licensed for the Lucky Community Forum is obviously the same as that licensed by (ISC)^2 for *their* Community, so the similarity in names is unsurprising.)
Another interesting side issue: When my baby brother put me onto Lucky Mobile, they had a "refer a friend" promotion, which I alluded to earlier. It provides a discount for both the referring and referred friends. A couple of days after I started all this hassle with Lucky's support, and started publicly posting about it, I got an email saying that my Refer-A-Friend submission was not successful, despite all the information submitted being correct and within the terms of the promotion. (Maybe my public postings about them got them mad?) I posted this paragraph on the Lucky Community Forum, as a separate posting (as a separate issue), and the moderators moved it to be a reply to a different posting (although on the same topic), but also editted my posting, and took out some material.
I have now had a call back from, well, someone who said he was calling from Lucky. (Whether that is actually Lucky or Bell was not specified.) He first called my cell, which was not the instructions I had left in regard to contact for the Bell second level people, so that seems to indicate that he is someone in Lucky, rather than the escalated call to Bell. However, even though he left messages on both my cell and home phone (which he did call after calling my cell), he didn't provide any information that could help. Instead, he wanted to know what the error message was that I was seeing. Now I'd specified that many times in the "chats" I had with support, and I've now sent a screenshot (showing the error message "No account available for SMS") through two different channels. Obviously, Lucky and Bell, even though they are in the communications business, don't talk to each other.
The next contact was via Twitter, and said, verbatim (except for Xing out the agents initials), "Hi! I just wanted to follow up and make sure your concerns have been addressed. If you still need our help, please let us know. We’re here to help you out. Thank you. > XX"
On both messages, left on both phones, the support person had said that I would be contacted again within 24 hours. They were about six hours late on that self-imposed deadline. But I did finally get a call (on the cell, not the home phone, as I had instructed). Again, the support person asked for the information that I had previously given, about the error message. This time, however, when I said that I had a screenshot, he was willing to give me an email address in order for me to send it. I also provided the complete account, up to this point, of the support saga. He said that this would be passed along to the Lucky Wi-Fi Calling app "team," and that I would be contacted.
After the weekend, during which absolutely nothing had been done and nobody had contacted me, I was again contacted via Twitter: "Hi! I just wanted to follow up and make sure your concerns have been addressed. If you still need our help, please let us know. We’re here to help you out. Thank you. > XX" Apparently, this assumption that all of my problems had been solved was generated by an internal message (which, of course, had not been communicated to me) that "I called customer and escalated ticket Id #12345 to CounterPath Team." (I note that "ticket Id #12345" had nothing to do with the escalation number which I had previously been told.) However, this, and a little Google Foo, indicated that yet *another* party, besides Lucky Mobile and Bell, had entered the picture.
CounterPath is a Vancouver company, with offices in one of the Bentall towers, with interests in voice over IP, videoconferencing, and "unified communications technology." They were acquired by Alianza in March of 2021, at which time their corporate blog pretty much went dark. They have a "softphone" (Bria) that combines voice and video, developer tools (Bria and Stretto), and do "white label" softphones for companies that do not want to bother developing their own. I haven't yet downloaded a free trial of Bria Solo, but it seems pretty clear that Lucky Mobile Wi-Fi Talk & Text is simply a branded version of Bria. (CounterPath *does* do APIs and SDKs, but the problems I am encountering are unlikely to reside in the back end of the app, and are much more likely to be in the interface.) So, in addition to this saga being about the support failures of Lucky and Bell, this is now also about the support failures of CounterPath and Alianza.
In the meantime, my baby brother (who sorta started all of this), has become more interested in the app. He is having vision trouble, and has a tablet with voice recognition and other aids. The tablet, being a tablet, doesn't make phone calls, but, since he has a Lucky account anyway, he is interested in using the Wi-Fi Calling app (*IF* we can get it to work) to place calls through the tablet. (We have also discussed a hack: my niece is currently in Foreign Climes, and, again, *IF* we can get the app to work, she can place calls back to Canada using it.)
Meanwhile it's presumably five days since the problem was "escalated" to CounterPath, and still nothing seems to be happening ...
On the morning of January 13th, I suddenly "received" a text that someone tried to send me on January 4th. Also, the big red dot at the bottom right of the screen has disappeared. Trying some calls and sending some texts did seem to be successful, although the test wasn't terribly conclusive. Trying to get the other phone to work was not successful, but, this time, resulted in an error code of #CV007. (Very James Bond?)
On the morning of January 14th, I did receive a call from Lucky's (or Bell's) support. The call wasn't very informative, including where the caller worked. He simply said that some other team had said that my account had been reset. What was the problem? He couldn't say. If this happened again, was it going to take another two weeks to get it fixed? He couldn't say. What about the problem with the app on the other phone? That wasn't supported. Why? He couldn't say.
Overall, the app does seem to work. Over the weekend I placed a call of over an hour in length, with no problems. However, if you *do* have problems, don't expect Lucky or Bell or CounterPath or Alianza to respond in any timely way, or with any details when they do.
