| User | Post |
|
2:20 pm May 30, 2011
| kittkatt0
| | | |
| Newbie | posts 2 |
|
|
For the past few days I've tried to activate a voucher that I bought a couple of months ago from 7-11 on the website but when I press "go" it returns with a Internal 500 service error. I tried doing the same thing on firefox, IE and Chrome. Just wondering if anyone else has had this problem? Thanks
|
|
|
3:19 pm May 30, 2011
| andy123
| | Ottawa, ON | |
| Member | posts 14 |
|
|
Yes. I had the same problem as you so I added the airtime voucher another way.
This is what it says on the official SpeakOut wireless website FAQ:
“How do I add airtime to my SpeakOut Wireless account?”
"To activate airtime vouchers from your SpeakOut Wireless phone, dial *888 and follow the prompts. Have your SpeakOut Airtime voucher ready when calling.”
|
|
|
6:48 am May 31, 2011
| walter_wpg
| | | |
| Member | posts 57 |
|
|
I haven't used the web method yet, but I did have problems adding a top-up on Sunday, using the standard phone method, dialing *888. When I entered the 12-digit number, it said the PIN was invalid. Repeated several times with same results. I then called up Speakout customer service, waited just 30 seconds to talk to a person, explained my problem, and gave her the 12-digit PIN. She had no problem entering it, and my $25 top-up was added to my balance.
|
|
|
7:14 am May 31, 2011
| pathfinder35
| | Regina | |
| Member | posts 50 |
|
|
Yes, I had same problem – using Firefox 4.0 – didn't get an error just a blank page. So I added it the old fashioned way (dialing *888) and it worked.
Remember today is last day for buy $100 voucher and activate voucher today and get $25 bonus…
|
|
|
8:49 pm May 31, 2011
| call44
| | | |
| Member | posts 12 |
|
|
i had the same problem yesterday.Safari gave me a blank screen. I tried a few times. *888 worked fine but if web activations are offered, they should work
|
|
|
11:52 am June 4, 2011
| iamdrumming
| | Niagara Falls | |
| Moderator
| posts 1531 |
|
|
I just activated a voucher through the site with no problems. I'm using Firefox 4. Looks like it was a temporary glitch.
|
|