Why it can ‘take a few days’ to be unsubscribed from an email list (2019)
I have a <i>thousand</i> similar stories (my comment history will turn up several of them).<p>For context, in the late 90s, I started at &quot;the first iteration of&quot; Frontier Communications, not long after it transformed from Rochester Telephone and Telegraph[0], before its acquisition by both Global Crossing and Citizens (I went with the Global Crossing side).<p>We were a ~20,000, no 5,000, no 15,000, no 10,000, well, somewhere in there depending on what part of any given year over the 2 decades that I worked for the variety of companies that started, for me, there.<p>On one occasion, we had a process for collecting tariffs.  That term isn&#x27;t exactly right, but it describes it best.  Basically, when a phone call is placed in the US, if it does not terminate with your carrier, your carrier is paying a fee to another carrier, or to a long-distance provider[1].  For call termination purposes, Global Crossing was almost always the long-distance provider, not the local provider[2] and we were paid an amount by one of the larger players that doesn&#x27;t go unnoticed when it&#x27;s missing from the balance sheet.<p>The finer details are in a previous comment of mine, but the end result was my discovery that the process for getting paid was tied to a decade old desktop PC sitting on a shelf in the main data-center with a USR modem attached to it which was recently moved from Green Bay, WI to Detroit, MI (and none of the original staff came along with it).  It was sitting at a boot screen asking for hard disk parameters.  I reported to a VP at the time who came to know me as the guy to go to for the strange stuff, and having spent my teens building PCs and inputting those parameters I recognized label with the odd acronyms&#x2F;numbers on it as the parameters it was complaining about -- clearly the last guy noticed the dead battery and the label maker, not a replacement battery, was available.<p>Up until a few years before I left, the &quot;trouble-ticketing&quot; system used for all <i>customer</i> and IT support was purchased, source code and all from a bankrupt ISV[3].  It used a Java fat client that talked SOAP, I think, to the worlds most normalized, awful performing database I&#x27;ve ever encountered.  I saw queries coming from this app where the UI indicated date ranges like &quot;1&#x2F;1&#x2F;2003 - 1&#x2F;1&#x2F;2005&quot; and the app would spit out a query with &quot;BETWEEN&quot; statements for each day, with nested parenthesis.  It was clearly the worlds ugliest ORM, and trying to make sense out of the over 2,000 tables that made up the application was, barely possible.<p>To resolve this grief, our <i>internal development team</i> undertook writing a web UI for it.  At a certain point, I want to say we had twice as many <i>physical</i> hosts operating our <i>internal</i> ticketing system than we did hosting <i>everything</i> we exposed externally, and not just &quot;more boxes&quot; but <i>the most powerful hardware in the DC</i>.<p>There seems to be a lot of sentiment, here, that if this were a &quot;sign-up&quot; process, it&#x27;d be far faster&#x2F;better.<p>Anecdotally, my experience leads me to think this is more &quot;laziness&#x2F;enterprise inertia&#x2F;large-company edge-cases&quot; than it is &quot;it&#x27;s not bringing in money, so we&#x27;ll do it the dumbest way imaginable&quot;.  At least, I know for a period of time large pieces of the on-boarding had the appearance to the customer of being highly automated, but at the end of the day, it was a Clarify ticket passed between several hands who made phone calls&#x2F;sent faxes.  They&#x27;d certainly allocate larger staff to something that brings in revenue, but anything <i>regulatory</i>-related, at least where I was (and probably similar in all Telecom -- almost certainly <i>more obnoxious</i> in anything banking-related) was taken <i>very</i> seriously.<p>The fact that <i>they have contract staff in India</i> handling the process <i>manually</i> says two things to me: (1) somewhere, there&#x27;s a fine&#x2F;other <i>clear</i> risk if they don&#x27;t and (2)  someone decided this was the cheapest way to do it.  I&#x27;d challenge whether that last part is <i>actually</i> true, but I&#x27;ve seen so many <i>strange</i> things where the reason turned out to be &quot;there&#x27;s some lawyer&#x2F;some rule somewhere that says we have to <i>also</i> do <i>this</i> odd thing when we unsubscribe a user and writing a tool to access the system that <i>does</i> that one thing will cost us $150,000&quot;.  Usually that &quot;odd thing&quot; is some form of tracking for auditing purposes and the system that would be used for tracking whatever that odd thing is ends up being either ancient&#x2F;impossible to interface with or comes with some insane Enterprise-y license model that results in costs doubling whenever you want to do anything useful.<p>[0] Name escapes me.<p>[1] I have been out of Telecom since just before Level 3 became CenturyLink (now Lumen).  This was the case when I left, it is probably still the case, today, but someone might have fixed that by now, too.<p>[2] This was GC days, still operating a few actual termination points, most of the business was IP or traditional long-distance; Technically, though, GC was a CLEC.<p>[3] My memory is foggy, I may have details incorrect here but the product was called Clarify.  To make matters worse, there was at least three <i>different</i> vendors out of ... eight or so? ... that called their product &quot;Clarify&quot; or used that in its name.  I&#x27;m not even sure if <i>ours</i> was just &quot;Clarify&quot; because by the time we were done with it, its UI was entirely internal and it had an (ugly) internal logo.