|
|
|
|
|
by maxbond
745 days ago
|
|
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. |
|
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.