It is a risk. I had a problem with my Google account, and while I was able to find a human to email about it, they were completely unable to help. It was literally "you have to do the thing, even though it makes no sense, because that's what our algorithm requires" (in my case it was repurchase an old domain in order to prove that I owned it, so they could cancel the account associated with that domain. Literally makes no sense, but it was the only way their process could work). That was my "ruh-oh" moment when I realised their products are basically unsupported and therefore shouldn't be used in production.
Stating a truism - to make a billion dollars, you either have to get $10 from 100M sales, $10k from 100k sales or $10M from 100 sales. Although each option leads to the same revenue, there are major implications as for the amount of support and attention you can spend on each customer.
Google/Facebook/Twitter obviously run the "$10 from 100M sales" model - meaning the only way they can provide profitable support or moderation is via inanimate algorithms, and deal with the PR fallout when they go wrong.
Moving an email is admitably much harder, but after five years I've managed to do all the major ones.
What happens if the domain-name is repurchased by someone else or claimed by Sedo, etc?
That isn't necessary though - other companies like Microsoft, Oracle, and SAP also have tens of millions - to billions - of customers all with their own support requirements: the solution is simple: make the customer put up their own money as collateral for getting to speak to a human.
Microsoft charges $500 for a single business-class support ticket with ~8 hour return time[1] - and you get the money back if the ticket was not a PEBCAK issue. If you're a company that depends on Azure or Visual Studio or Windows Server then keeping $500 around just makes sense.
I just don't understand why Google and other companies that deal with long-tail customers don't provide this as an option.
[1] In practice, if you have an Enterprise support contract, the effective cost is much lower AND you get a much quicker response time - but there's more paperwork involved.
(Microsoft is just as bad - their sales people can’t be bothered to talk to anyone who isn’t a partner, but that worked out great for me, I wasn’t really feeling azure and it made a great excuse to not consider them. One of their sales people did leave me a VM three or four months later but we had already chosen another vendor by then).
Say what you will about how crappy Win 9x was, but they definitely drove the average tech support load to much less than one call per machine.
(yes, loss from not handling a single .com domain is minuscule for Google - but I wonder how common is to run away from any Google service due to risk to entire account)
File for a C&D and then, if that does not help, a court-issued injunction order ("Abmahnung" followed by "Antrag auf Erlass einer einstweiligen Verfügung"), if you're German. This works somewhat reasonable for Twitter, Facebook and Google.
If I have an issue with Google, I might try starting an adwords campaign and ask to speak to supervisors when their sales calls comes through, and see if there's an in along the way of "we would spend more, but you see you've done X that needs to be resolved first".
My other approach - not tried it on Google, but it worked very well on DHL and Uber so far - is to sign up for LinkedIn's premium subscription and use that to Inmail a bunch of VPs/SVPs and set out my grievance. My experience so far is that you need to find someone high enough up to be under the illusion - from lack of customer contact - that everything is well. They often seem to be shocked to hear that customers hit the wall, and get approached rarely enough that it's a novelty for them to help out (as such, it'll probably stop working if everyone starts doing this...)
With DHL in particular I got an SVP to get his assistant to light a fire under the customer service operation by telling them said SVP wanted to be kept up to date on how it went, and Cc'ing said SVP and me on the e-mails. A package they "could do nothing about" because it was supposedly on a boat back to the US, magically appeared in my office one business day later after it was located in a depot 5 minutes from my office (I wish I could say that was the first time DHL has told me a package was somewhere completely different to where it actually was)
That's why if you have an OEM license for Windows (where the per-unit cost is more like $40/unit rather than the retail $100-$300) your first-line support comes from your OEM, not Microsoft.
It seems that even Googlers themselves cannot get any human contact for account support.
(Sadly I can't find that Twitter thread anymore.)
EDIT: Found it - https://twitter.com/miguelytob/status/1315749803041619981
The latter parts of the story were when I was part of Common Crawl, a public good dataset that has seen a great deal of use. During my tenure there I crawled over 2.5 petabytes and 35 billion webpages mostly by myself.
I'd always felt guilty of a specific case as our crawler hit a big name web company (top N web company) with up to 3000 requests per second* and they sent a lovely note that began with how much they loved the dataset but ended with "please stop thrashing our cache or we'll need to ban your crawler". It was difficult to properly fix due to limited engineering resources and as they represented many tens / hundreds of thousands of domains, with some of the domains essentially proxying requests back to them.
Knowing Google hammered you at 120k requests per second down to _only_ 20k per second has assuaged some portion of that guilt.
[1]: https://state.smerity.com/smerity/state/01EAN3YGGXN93GFRM8XW...
* Up to 3000 requests per second as it'd spike once every half hour or hour when parallelizing across a new set of URL seeds but would then decrease, with the crawl not active for all the month
I am sitting here thinking of what would happen if my Gmail account got blocked. The disruption it would cause to me is enormous.
https://turkishlawblog.com/read/article/221/algorithms-meet-...
I look forward to this getting used against Google and everyone else banning customers without explanation and/or recourse.
Maybe a company at a certain scale should have a legal requirement to get a person on the phone for any support issue, full stop.
All these companies will continue the race to the bottom unless you twist their arm. For PR, sounds like a nice job creator to me!
From recent tweets, it seems he's now leaving Google, and is busy retweeting stuff about people who have been fired and/or are suing Google. Wonder if him leaving has anything to do with that incident and whether it was ever resolved.
> surely I am protected from this, right?
Nope. Google can disable you account at any time, without telling you why, and without giving you any appeal process whatsoever. No free-gmail user is in any way protected against this. People paying for Google Suite accounts are ever-so-slightly more likely to receive some support if anything happens, but that's it.
> The disruption it would cause to me is enormous.
This is why I'm slowly moving away from it (and everything Google, really). The service is extremely reliable, it raised the bar for email services and web UI, what they've done to spam is fantastic, but the possibility of losing such a key account and not have any recourse is now too terrifying to contemplate.
In my direct personal experience, I went on medical leave near the end of my stay there and when I came back over half of my team had quit and bailed for other companies or other orgs (largely over complaints with management).
For any support issue? Given the realities of running a business over the Internet today, that would be a waste of resources and needlessly expensive.
But I do agree with you in principle though: I think there should be a legal requirement that anyone with a dependent business relationship to a service provider should be legally entitled to human review of any automatic suspension decisions within a single business day. This shouldn't affect long-tail businesses because when there's a strong dependency relationship there's definitely large amounts of money exchanging hands - from which presumably a small fraction would pay for the requisite support costs.
I figure that they either never thought through this process, or it was deliberately designed to make the cancelling process as awkward as possible. They're smart people, I think the latter.
So if they're going out of their way to be inconvenient to me, I'm going to go out of my way to never use their stuff.