Claude Research Button: Start With a Clear Question

The Claude Research button starts an investigation that can search across multiple sources and follow up on what it finds. In the interface described by Claude’s current help page, open the plus menu beside the chat composer and choose Research. Check the instructions for your account if the control is absent.

The button starts the search; a clear question and a source review make the result useful. Tools like fenbs keep the research question, checked findings, and remaining tasks with the project after that conversation ends.

Where do you start a Research session?

1. Open the account and workspace you intend to use. Check that this is an appropriate place for the material you will provide.
2. Look in the plus menu for Research. Claude’s documented interface shows an indicator when it is enabled.
3. Check the web search setting where your interface provides one. Research requires web search to be available.
4. Enter a focused question with the audience, scope, and kind of evidence you need, then review the sources in the result.

Claude’s Research help page↗ (opens in a new tab) is the reference for availability and current controls. Access depends on your account and organization settings. Avoid instructions that assume every account has an identical button or offers the same source connections.

Start with a small question whose answer you can inspect. For example, ask which official documents explain a particular application requirement, rather than asking for a complete strategy for a new organization. The smaller task makes it easier to notice a missing source or an answer to a different question.

Which sources should the investigation use?

Decide whether the question concerns public information, internal documents, or both. Tell Claude which sources belong in the answer and which should be excluded. A focused instruction helps, but it does not replace checking which connectors are actually enabled for the chat.

Claude’s documentation says Research can use enabled connectors on the web and desktop; a session started in the mobile app searches the web without those connectors. If internal documents are necessary, choose a supported starting point and confirm that the relevant material was used.

• For public requirements, request the responsible organization’s own guidance and the relevant version or effective date.
• For an internal question, identify the approved documents and the team or project they concern.
• For a comparison, give the same criteria for every option so the assistant does not change the question between sources.
• For sensitive material, follow your organization’s rules about what can enter the account and which tools may access it.

Do not connect a whole workspace merely because one document might be useful. Start with the smallest appropriate source set. When a source was unavailable, ask Claude to identify the gap rather than infer what the missing document probably says.

What should you type after enabling Research?

Give the investigation a purpose and a stopping point. Say what you need to decide, which geography matters, and what would count as sufficient evidence. A question about a US nonprofit application should not drift into unrelated advice for commercial businesses or other countries.

Use Research to answer this question: [specific question].
Audience: [who will use the answer].
Scope: [US location, subject, and relevant period].
Use these approved sources: [links or document names]. Prefer original guidance.
For each finding, include the source and the passage or section that supports it. Separate evidence from interpretation.
Identify disagreements and missing information. Do not make the final decision for us.

Replace the placeholders with concrete details before sending. If you have no approved sources, ask Claude to identify candidate primary sources first, then inspect them before requesting a broad synthesis. That gives you an early chance to correct the direction of the search.

Include exclusions when the question has tempting detours. A hypothetical question about a university’s submission process might exclude advice on choosing a degree program. Keeping the boundary explicit reduces the chance that a long answer hides the one requirement you actually needed.

Save a successful question and its source restrictions in fenbs Skills and prompts; how it works describes how connected assistants can read that shared starting point.

How can you tell whether the result answers your question?

Begin with the claims that could change your next action. Open each supporting source and check that its wording, scope, and date match the answer. A page can be authoritative about one program while saying nothing about the program you asked about.

Claude’s web search documentation↗ (opens in a new tab) recommends cross-checking sources for important information. Ask follow-up questions about conflicting evidence, but do not resolve a conflict by requesting a more confident tone. Record the disagreement when the available material cannot settle it.

For example, if a general help page and a specific application notice differ, keep both links and identify exactly what disagrees. The responsible office may need to clarify the answer. The useful outcome is a precise question for that office, not a blended rule that neither source actually states.

What if the control is missing or the session seems wrong?

Compare your account and interface with the current official help page before searching through old screenshots. Organization controls and access changes can affect what you see. If web search is available but Research is not, narrow the request and review the resulting sources as a separate workflow.

An unavailable feature and an investigation that stops midway need different checks. The guide to Claude Research getting stuck covers an interrupted run. If the entire app is unavailable, use the separate Claude service-status guide.

How to do this with fenbs

1. Create a free account and add the project that needs the research answer.
2. Write the research question and source boundaries in an AI context note. Add the primary sources you already trust to Links and listings.
3. After reviewing Claude’s findings, record the supported conclusions and create tasks for unresolved questions. Record a decision only when a person makes it.
4. Connect your supported assistant through Integrations. Ask it to read the project context before continuing and save progress with the next check when it stops.

fenbs is free for one person, with no credit card. It does not enable Research in Claude or verify research results for you. If you need one quick answer and have no follow-up work, the Claude conversation may be enough; fenbs fits when the question continues across several sessions.

Save one checked finding and one remaining question as your starting record. For orientation beyond this control, see what Claude is and the AI at work topic hub.