Answer a research question
Ask a specific question with its scope and depth. It researches across sources, reconciles what it finds, and cites everything.
Copy this prompt to start your first task:
What is this workflow?
Answering a research question means giving a teammate a specific, scoped question instead of a vague topic, and letting it check multiple sources in parallel rather than one at a time. It merges repeated content across those sources, and flags conflicting reports instead of silently blending them into a single answer. The result is an answer where every claim links back to where it came from, so you can check the reasoning instead of just trusting it.
How to use this workflow
Hire a research teammate
Open AI Teammates in the sidebar, click Hire AI Teammate, and pick the Researcher template. Confirm the name and click Create teammate. They land in their own channel, which is where you'll send everything below. More on hiring →
Ask a specific question, with scope
A vague ask produces a vague answer. Give the scope, time window, and depth you need:
For example:
For an evolving topic, track it instead of asking once
Open Automations in the sidebar and click Create via Chat. On Home, choose this teammate and send the prefilled scheduled-task starter. When the interview asks what to schedule, answer with the recurring job below:
Nothing here needs your approval: searching, reading sources, and drafting the answer are all routine read actions, which run on their own. See Control for what does pause for sign-off.
Tips for Better Results
| Tip | Description |
|---|---|
| Give scope, time window, and depth up front | A bare topic gets a generic answer. Naming what to focus on (and what to exclude) gets a usable one the first time. |
| Ask for a source on every claim | Lets you check the reasoning yourself instead of just trusting the answer. |
| Expect conflicts to be flagged, not resolved for you | Contradictory reports are surfaced, not silently blended into one answer — read those flags before treating the answer as settled. |
| Track evolving topics instead of re-asking | Set up a weekly check via Automations and get only what's new since last time, not the whole history repeated. |
Common Questions
Research
Back to the research use case overview.
Watch competitors weekly
Track named competitors instead of a general question.
Gate-check usage data
Push back on what "active" means before pulling a single number, catch a suspicious zero before it ships as a finding, and never call an automation "running" without a schedule ID and a run record to prove it.
Organize feedback into docs
Chat messages, an interview transcript, or a meeting recording all become the same kind of tracked, prioritized item, filed and routed automatically.