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.

More guides

The AI draft is the starting point, not the send button. Here is the three-pass routine that keeps it human.

A research paper I'd been avoiding became a 25-minute walk. The workflow is dumb, and that's why it worked.

Not zero-inbox. A loop that decides what is real so I only touch email twice a day.