Official documentation checked October 14, 2026.
Continue a Perplexity conversation by opening the relevant session and entering your next question in its reply field. The product now uses “session” in its Help Center, while older pages and links may still say “thread.” A useful follow-up names the point you want to investigate and preserves the constraints that matter.
You do not need to rewrite the entire original question. However, an earlier answer is not proof of a fact, and keeping a conversation open does not guarantee perfect recall or unlimited usage.
How Perplexity Handles Follow-Up Context
Perplexity’s session capabilities guide describes contextual follow-ups and recommends guidance when topics change. It does not establish a universal 2,000-word cutoff. The Pro Search guide also describes follow-up exchanges; you can ask a further question about a Pro Search answer.
Reference the idea itself rather than only saying “that.” After comparing two project-management methods, ask “For a five-person team with a fixed launch date, what would make the second method unsuitable?” This identifies the comparison, team size, and decision you need.
Steps to Ask a Useful Follow-Up Question
- Open the intended conversation. Check its initial question and most recent answer. If you are returning later, use History to locate it rather than starting an unrelated search accidentally.
- Choose one purpose. You might request a definition, test an assumption, narrow a date range, or compare a specific alternative. Write that purpose before adding more background.
- Enter the question in that session’s reply field. Use the send control shown in your web or mobile client. Read any dictated text before submission where the interface allows it; do not assume gestures or microphone behavior are identical across clients.
- Restate essential constraints. For example: “Keep the same five-person team and June deadline. Compare only the two methods already discussed.” Include a short source passage when its precise wording matters and you are permitted to share it.
- Inspect the new answer. Check whether it kept the scope, answered the question, and cited evidence for new factual claims. Correct a misunderstood premise before adding another branch of discussion.
For a research task, a practical sequence is: identify the options, ask for evidence about one uncertainty, then compare the options against explicit criteria. Keep your own note of which claims you have verified. A fluent later answer can still repeat a mistake from an earlier response.
Common Follow-Up Problems and Corrections
The answer changes subject: name the relevant item and repeat the missing constraint. If several unrelated tasks have become mixed together, start a new session with a concise brief. Check that brief yourself before using it.
You need another source selection: the technical guide says Focus must be chosen at the start of a new session. Preserve the original and start a separate comparison with the intended sources. A sentence asking for “different sources” is not proof that a source-setting control changed.
Important earlier evidence is omitted: point to the exact statement or source and ask a narrower question. Do not diagnose a precise memory cutoff from one omission. Ask the service to identify uncertainty, then verify against the original material.
A limit message appears: retain the unsent question and read which feature is limited. Follow-ups should not be assumed exempt from usage limits. A new conversation is an organizational choice, not a documented way to reset an allowance.
Choose the Next Question for the Result You Need
| Goal | Example | Check |
|---|---|---|
| Clarify | Define the second criterion using a small example. | The example matches the definition. |
| Verify | Which original source supports that date? | The linked passage supports the date. |
| Compare | Compare these two options against our stated deadline. | The deadline remains unchanged. |
Use the smallest follow-up that resolves the next uncertainty. If the answer introduces new assumptions, address them explicitly rather than allowing them to become the foundation of the rest of your research.
Glad it helped. Take a short break with a game:
Sorry about that. Search for the exact error message, or look for a tool that checks your device: