OFCOM drop the ball?

OFCOM have created a new system for migrating broadband lines, harmonising it with phone lines. The system is called Gaining Provider Led (GPL) because you simply order service with a new provider - no need for a Migration Code (MAC).


Many of us think this is a bad idea. Broadband is not like electricity or gas, where an incorrect migration does not disrupt the actual service, it simply creates billing differences which can always be sorted later. With broadband you could find you inter office leased line that works using Ethernet over FTTC circuits suddenly changes to some generic residential broadband service, taking 10 days to fix, simply because someone put a wrong digit on their order with an ISP and somehow your organisation missed the "Notice" that was sent to the account department in another office. There are real danger of some ADR or suing if this were to happen. There is also the fact that it will now take 10 days, not 5, to migrate services, which seems a backwards step.


However, looking at this in practical terms, as it all kicks off in June, we did consider that it should be relatively easy:-
  • Orders to BT are the same, except we don't send a MAC, simple enough
  • Notices from BT are the same, as we get them for migrate-out using a MAC, some fields will be a tad different, but we already get these notices, we just need to email the customer
  • Cancelling a migrate-out is something we could do already, but don't have to as a MAC is used. We'd have to integrate it a bit more in to our systems and make it easy for customer to cancel.
Of course we expected a few other changes:-
  • Update details of how to migrate on web site
  • Change order form not to ask for a MAC
  • No longer offer people option of getting a MAC
Not so simple!

Unfortunately, now we are working on some of the details, it is far from simple.

For a start, we have a couple of places where we have to send letters which then have a detailed list of things we have to say. Most are simple, but not all. For example, our billing system (priceless) can work out what to charge people for a minimum term when it picks up that a line has ceased and raises a bill - easy. However, the broadband management system which deals with these messages (clueless) does not have billing/pricing data, so for it to tell people the exact amount they will pay for the remainder of a minimum term (Early Termination Charge) means it needs to somehow ask the billing system, but not actually raise a bill (not something the billing system usually does). So not as simple as it sounds, so that will be fun.

Also, these letters need to go by post unless the customer has agreed we contact by email. Well, all of our customers have agreed this. It is in our terms and very clear, and we email invoices and DD notices and so on. But OFCOM are saying that being in our terms is not good enough, we have to have explicit consent from the customer for this. Well, that is easy for new orders, but are we going to have to contact all existing customers to get this explicit consent - that will be a pain for us and them. We're asking OFCOM to confirm.

We also can't talk to the customer to even ask why they are leaving as that could be seen as a reactive save (retentions call).

Anyway, obviously. we are working hard to ensure we follow all these crazy rules to the letter by the time the new process starts in a few months...

But what of OFCOM dropping the ball?

Well, this is where it gets interesting, and we hopefully get reaction from BT and OFCOM today on this. These rules are imposed by OFCOM General Conditions. GC22 covers the migration. 22.30(s) defines "End-User" such that it excludes large businesses (those with more than 10 people doing work for them). 22.30(n) defines "Customer" as an "End-User", so that excludes large businesses. 22.30(j) defines "Communications Provider Migration" as an "End-User" or "Customer" changing provider, so that excludes large businesses. Even 22.30(gg) defining "Migration" as a word, excludes large businesses by use of "End-User" or "Customer". Pretty much all of GC22 uses these terms which exclude large businesses. Even 22.25 which is a catch all for cases not using BT, etc, and basically says ISPs have to work together to facilitate a migration fairly/quickly uses the "Migrate" definition which excludes large businesses.

The whole of the migration process does not apply to large businesses!

This is new. This is different. This is a surprise. I am happy that such a dangerous system does not apply to large businesses, but there is no alternative. The old MAC based system is stopping, so that does not apply either.

Large businesses may simply not be able to migrate phone line or broadband services now. Obviously there will be cases where providers co-operate and do this, using the underlying BT/carrier mechanisms, the same as small businesses, but they don't have to. If a large business asks us to take over a line, the losing provider could just cancel the migration as it is not covered by the migration process at all.

Obviously if I have missed a step here I hope someone will tell me, but I can't see it.

Is this what you meant OFCOM? If not, please let us know when you consult on a new version of GC22 to fix this as we'll be happy to comment.

I'll update if I get responses from BT and OFCOM on this.

Update: No word from OFCOM yet. BT have a relatively easy job of the various messages and process changes, but are not sure of the "point of no return" and cancellations at the last minute. They also get the impression that OFCOM are being a tad wooly on several points. They were interested in the large businesses issue and they too have asked OFCOM for comment.

Update: OFCOM have apparently confirmed to BT that the new migration process does nt cover larger businesses.


  1. > by email ... we have to have explicit consent from the customer

    Consent given. Now it's just (entire AAISP broadband base - large businesses - 1) remaining :)

  2. So a “Small Business Customer”, in relation to a public
    communications provider, means a customer of that
    provider who is neither himself a communications provider,
    nor a person who is such a customer in respect of an
    undertaking carried on by him for which more than ten
    individuals work (whether as employees or volunteers or

    So do we have to now tell you whether we are a "small business" (or not) now? How can you possibly know or monitor this?

    Broadband migration slamming protection implementation:-
    Step 1: Tell AAISP "I am a large business"
    Step 2: Done!

    1. When we joined AAISP 10+ years ago, there was 3 of us. Now there are 7 and I can see in the next year we may hit 10. I don't remember being asked what our size was when we joined, but a decade will have that effect :) However I'm sure there are plenty of businesses that have crossed this threshold since they started a service with any ISP.

      Do businesses now have to keep track of this and inform their ISP? As you say, these new rules seem like nonsense.

      Also, since I see "Techie", "Business" and "Legal Status"(Subscriber/Communications provider/Internet service provider) in clueless. Perhaps it would be an idea to also have "large business (10+ people)" now too?

      (to be fair, no business should be relying on one line or one service from one provider anyway, there should always be a contingency - but still... nonsense)

    2. We did not ask back then - we started asking when ADR started, as the same rule applies as to whether you can use ADR or not, so we need to know. But yes, I'll check clueless - that change (subscriber, etc) was for Digital Economy Act which works on different set of rules.

    3. Interesting then.. So any business that reports itself as"large / 10+ people" gets "anti-slamming protection" and forgoes its right to ADR (which we've established is a farce anyway)

      On a different side, if we assume a large business cannot migrate or is onerous in some other way (I'm looking forward to the clarification on that, maybe they think that any business with 10+ employees will find cancelling the old service with installing new lines + broadband service etc a tiny cost compared to home users?) since only "self-reporting" on staff numbers can work, then a company simply stating "Our company now has less than 10 staff members" to you (via a handy checkbox) can then get a GPL migration?

  3. Wouldn't the 'slamming' isp be guilty of 'interference with a public telecommunications network'? I remember when we got (phone) slammed by Toucan (now owned by talktalk) I simply told BT that we'd never agreed to it, BT somehow clawed the line back. The overall effect being that this Toucan outfit gave us free international calls for a month

    1. Well, this is one of the grey areas OFCOM are not defining - responsibility and liability for various types error or malice.

  4. Can I instruct you up front to reject all migration requests I haven't preauthorised? I'd even pay a nominal fee for this service as a fraud protection service if it helped.

    1. Ditto

      Once OFCOM go ahead with this idiocy, why not insert into invoices a link that the customer can follow that explains the danger of slamming, and allows them to request a call in the event of a migration being started? If the customer specifically asks for a 'reactive save' call, I can't see any objection OFCOM may have standing up, as you are merely responding to a customer request.

      Last year, my line was migrated away against my wishes. Support stopped the process, but BT went ahead and moved it anyway, and actually switched my line with the flat downstairs in quite an amazing display of corporate incompetence. I got reconnected after nearly a month.

  5. When do you think isp's are going to pass on the reduced migration fee for FTTC and the new 1 mth contract terms? looks like ofcom drop a ballock there two IMO


Comments are moderated purely to filter out obvious spam, but it means they may not show immediately.

ISO8601 is wasted

Why did we even bother? Why create ISO8601? A new API, new this year, as an industry standard, has JSON fields like this "nextAccessTim...