Perplexity Computer query best practices
The strongest queries for Computer give it a strong starting point. A specific request helps Computer move faster, ask better follow-up questions, and return something closer to what you need. To get started, think of your query as an assignment with a goal, supporting context, and a clear result.
Start with the task itself: Say what you want Computer to do, not just the topic you want to explore. “Analyser customer churn from our CRM data and summarise the top three drivers” gives Computer a clearer starting point than “help me understand churn.”
Include the context Computer needs to do the work well: If the task depends on a file, upload it. If it depends on a connected tool like Google Drive, Slack, Snowflake, or Notion, make that clear. If the output is for a specific audience, say that too. For example: “Use the launch brief in Google Drive and turn it into a one-page summary for the sales team.”
Be specific about the output: Computer can create reports, dashboards, summaries, presentations, redlines, websites, apps, and other deliverables, so it helps to say what format you want. “Create a five-bullet summary” or “Build a dashboard spec” is more useful than leaving the format open-ended.
Keep the task focused: Computer can handle complex work, but it still works better when the goal is well defined. If several things are needed, give them in a clear order. For example: “Review the file, pull out the key findings, and turn them into a short executive summary.”
Use the same thread to improve the work: If the first result is close but not right, follow up in the same conversation instead of starting over. Ask Computer to make it shorter, change the tone, turn it into a table, or go deeper on one section. That works better because Computer keeps the context from the earlier task.
Use credits carefully: Keep tasks focused, use the same thread when refining the same work, and start a new task when the goal changes. Upload relevant files, connect the right tools, and use Skills for repeated instructions so Computer has the right context from the start.
Expect some back-and-forth: For more involved work, Computer may ask follow-up questions before it starts. That usually means it’s trying to get the task right instead of that the query failed.
For work that’s repeated often, use Skills: If you keep giving the same instructions for tone, structure, formatting, or workflow, turn them into a reusable Skill so Computer can follow the same process each time.
