I Built a Sourced FAQ With Perplexity So Support Stopped Answering the Same Thing

It writes the question, cites the page, and I trim the hedging. Reusable answers.

I listed the ten questions support gets weekly and had Perplexity draft an answer for each with a source.

Because it reads the web, the answers reflected current pricing and docs, not a model's stale guess.

A few citations pointed at pages that didn't say that, so I swapped in the ones we actually trust.

I cut the hedging language; customers want a straight answer, not a weather report.

Published it as a help page. Support tickets on those topics dropped, which is the only metric I care about.

その他のガイド

AI ドラフトは送信ボタンではなく出発点です。これが、人間味を保つ 3 パスルーチンです。

避けていた研究論文が徒歩25分かかることになった。ワークフローは愚かですが、それがうまくいった理由です。

受信箱ゼロではありません。何が本物かを判断するループなので、メールに触れるのは 1 日に 2 回だけです。