Jump to content

Sprint to start enforcing charging for using "Good for enterprise" in 2015/2016? (Corporate email ala blackberry)


bitslizer

Recommended Posts

Understood. Those of us impacted by this surcharge are just trying to piece the facts together slowly as they are learned publicly until we completely understand what the truth is. Each piece of the puzzle moves us closer it seems.

Link to comment
Share on other sites

Agreed. Good seems to have recognized that it's a mess and started to address it with official information within about 5 days. This got the attention of Good's CEO on Twitter. So far there are no external signs that this is being addressed by Sprint beyond front line CSRs.

Link to comment
Share on other sites

Marcelo Claure responded to this issue on Twitter this morning: "Good is being fixed as we speak."

  • Like 2
Link to comment
Share on other sites

I'd hate to be the middle manager at Sprint that thought adding this fee was a good idea (after Marcelo got involved).

  • Like 1
Link to comment
Share on other sites

Good move for them to drop it (no pun intended). If they didn't implement a way to actively block access to the service, people would have just dropped the fee from their accounts and still be able to use it, making Sprint and the fee look silly. If they had tried to actively block it for those not paying the fee, it would have angered valuable business customers and, as a net neutrality violation, opened Sprint up to more scrutiny. It was a lose-lose situation. It's a good sign that Marcelo recognized the mistake and worked so quickly to fix it.

  • Like 1
Link to comment
Share on other sites

Agreed. It only took about 5 days to get that reversed. Shows the power of social media when you have a CEO willing to directly listen.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...