not speaking for Amazon or any other FAANG entity, but one fun and important thing to do when thinking of an idea is to imagine the risks and downsides. For ex

not speaking for Amazon or any other FAANG entity, but one fun and important thing to do when thinking of an idea is to imagine the risks and downsides. For example, let's say someone uses your service to steal money or personal information from unwitting customers who think they're dealing with official 'FAANG support', or the bad actor provides erroneous information that ends up causing harm or death. Where do you think that open-ended liability would be assigned, were the legal system(s) to get involved? For another, let's assume for a moment that there's an unfilled demand for FAANG support. Most interesting support calls likely require customer identification and also, crucially, internal backend access (e.g. to account systems, server logs, billing systems, and so on). Your site will not have that capability. That limits you to the boring support calls, which might as well be a wiki or stackoverflow, raising the question of whether you were able to address this unfilled demand.