At KAYAK we had these red phones that would ring loudly until someone picked them up, and some technical worker would have to answer it and solve a customer's p

At KAYAK we had these red phones that would ring loudly until someone picked them up, and some technical worker would have to answer it and solve a customer's problem. This was controversial to say the least, for many reasons, but it was also extremely educational to see the misconceptions or worries or troubles that people had about the product you create. I enjoyed these even as a backend developer - often a problem or annoyance that manifests as a very surface-level thing to someone has deep code/architectural implications, and it grounded us to the people we were building things for, instead of striving for the perfect internals and architecture in la-la land.