Best chances are if you know someone inside to get traction or you have a dedicated account manager (if you are a large company with lots of money to burn).
When I was as Tumblr we were just as helpless and subject to the whims of Googlebot as a mom and pop. One day Google decided to ramp up our Googlebot rate ten times. This significant because they were already a double-digit percentage of our traffic, so going 10x placed an unexpected and worrisome strain on our backends. They only way we could get them to throttle back was through personal contacts people had with people over there. We didn’t want to tweet out to them and advertise we were under stress because it would bring out all the weirdos to ddos us (we even had to adopt rules to not talk about company holidays and offsites until after they happened because people would monitor our blogs and ramp up their bots when they thought we were out of the office)
Adopting Kubernetes at my current employer we had many discussions about going with AWS or Google Cloud. What it always came down to is AWS has support where we can write/chat/phone someone at any time and get a solution to your problem, and Google Cloud can only offer our account rep’s email address.
On consumer side, if you buy Google drive you get phone, email, and chat for all questions. Google Fi is the same.
But, some years back when I discovered problems with an online service of theirs, I cold called the switchboard, asked for the VP of the business unit, who picked up on the first ring, chatted for a few minutes, told me to expect a call from the product manager, who rang within 15 minutes, and worked with me for 6 weeks as they addressed (and I monitored) the problem, to satifaactory resolution.
Entirely unlike Google.