Hacker News new | ask | show | jobs
by jessriedel 750 days ago
It’s untenable from a marketing perspective to advertise a phone line that just talks about the services you don’t offer. One could maybe hope for a statement on a help page that says “Facebook will never ask you to call a support number”.
3 comments

I think what you've gotta do is say, "You can't call, but here is the number anyway," because customers aren't necessarily interacting with your page anymore. They're interacting with AI summaries of your page. Those AIs might be in house, or might be provided by a search engine. What is tenable or untenable will have to shift to the realities of how users are interacting with the information you present.

If you can't provide their AI with text answering their direct question (eg, "what is the support number for Facebook"), they'll find a document which does provide such text. If it's not you then it's a scammer or competitor. UX for these customers means presenting information in a way that sorts high in a semantic search and is robust to transformation.

If you provide text indirectly answering the question ("that number doesn't exist" rather than a literal number), you're liable to be scored as less relevant than a wrong but direct answer ("the number is 1555 SCAMMER"). You're also less robust to transformations, because you can't pull a valid phone number out of the text.

Or maybe I'm wrong, take any certainty implied by my language as rhetorical. That's just the pattern I'm seeing in these tea leaves.

Also, realistically, I don't imagine the phone number literally just telling you that the service wasn't available and hanging up. I imagine it would offer you options to get various pieces of information (the URL of the website, the legal address of Meta, how to navigate to the support knowledge base on the website, ...) and let you draw your own conclusion about how useful it was. Maybe it's occasionally handy to someone. At worst it's harmless.

I think in an ideal world, you could use speech recognition to let people leave a message, and open a ticket, as if they had emailed support@. When someone responds, the system gives them a call them back and delivers it using text to speech.

I like how we've suddenly accepted "AI" "summaries" as simply the way of the future, despite the inherent problems and repeatedly botched rollouts.
It could be rejected for sure. I personally don't think it's working well. I don't support it really.
I once had a Facebook rep I could call (they later ended this), and they didn't know that were two online newsletters about changes to internal Facebook apps used by advertisers (we used to be able to see who had clicked "interested" on an event). So they put in a bug report when the app stopped working, etc., but we later found it had been deprecated. All to say that dedicated support is often a cause of issues or confusion.
It is easy as hell