Users Pricing

forum

Home Forums How should I ask Perplexity to distinguish an unsupported feature from an undocumented one? – MindStick

How should I ask Perplexity to distinguish an unsupported feature from an undocumented one?

Waldemar Thiessen 72 18 Oct 2026

I’m comparing project-management tools and need to know whether guests can export a project’s audit history. The public help pages discuss exports and guest permissions separately, but I haven’t found a statement connecting the two.

That leaves several possibilities: the feature is unavailable, restricted to a particular plan, controlled by an administrator, or simply not explained in the public documentation.

What counts as enough evidence for “not supported”?

How would you phrase a Perplexity research request so that a missing search result does not become a definite “no” in a comparison table?

I’d like the response to distinguish between:

  • An explicit limitation stated by the vendor.
  • A community report about a particular account or plan.
  • No relevant documentation found.

For software feature verification, should I request a supporting quotation for every negative claim? And where would you draw the line between more web research and a question that needs vendor confirmation or a trial-account test?


0 Answers

Markdown for AI

A clean, structured version of this page for AI assistants and LLMs.

Open .md