# Create a research journey

import { Steps } from '@astrojs/starlight/components';

A Research journey is a question, or a short conversation, that EkLine puts to AI assistants such as ChatGPT and Claude, checking every answer. Create one to learn what assistants say about your product.

## Before you begin

- **Journeys** in the app sidebar. See the [Journeys overview](/journeys/).
- Any member of your organization can create and run journeys.
- Recommended: your brand names, competitors and documentation sites in your Company Profile (**Settings** > **Organization** > **Company Profile**). Brand checks need your brand names, and the report uses your documentation sites to mark which cited pages are yours. See [Company Profile and Domains](/agent/company-profile/).

## Steps

<Steps>
1. Open **Journeys** and click **New journey**.

2. In **What do you want to find out?**, write what you want to learn in your own words.

3. Optional: click **Create scenario with AI** to fill in the rest of the form from your sentence, including three or four checks, an agent and 5 runs. It asks before replacing anything you wrote. Read every field it fills in.

4. Under **Kind**, keep **Research**. To give a coding agent a task instead, see [Agent Task journeys](/journeys/agent-task-journeys/).

5. Under **The scenario**, write the question in the first turn field, the way a buyer would ask an assistant. Click **add a turn** for a follow-up, up to 20 turns.

   Each run asks every turn in order, as one conversation. The reply to the last turn is recorded as the run's answer, and checks such as **mentions a term** read only that reply.

6. Under **Who's attempting it**, select a persona saved in your Company Profile, or select **Write your own** and describe who is asking. The agent acts as that person throughout.

7. **What it can reach** shows your documentation sites and **open web · always on**. There is nothing to set. Agents find your docs through the public web, as any assistant does, so they read only public pages.

8. Under **What we'll check**, choose how each answer is graded. A new journey starts with **it hit no contradictions** and **it never gave up or asked for a human**. Click **N more we can check** for the library, or **add a custom check** to write your own. See [Write checks that mean something](/journeys/write-checks/).

9. Under **How we'll run it**, click the assistants that should answer. To change an assistant's model, click the model name on its chip and select one from the **Model for** menu. See [Choose agents and models](/journeys/agents-and-models/).

10. Set **Number of runs** to 1, 3, 5 or 10 times. Each run is a separate conversation, so 5 runs on two assistants gives 10 answers.

11. Keep **Let the agent search the web** on unless you want answers without searching. **At most** caps searches "where the agent supports a limit".

12. Click **Run 5 times** (**Run 5 times per agent** with more than one assistant). To test your setup first, click **Try it once**, which runs once per assistant. Both save the journey first. **Save draft** saves without running.
</Steps>

## Check it worked

- The journey's **Reports** tab opens with "Run queued. This page will update as soon as it starts."
- A report row appears, marked **Running** until every assistant has finished. Click **Open** to read it. See [Read a Buyer questions report](/journeys/read-a-report/).
- On the **Journeys** list, the journey moves from **Drafts** to **Published** after its first run with a finished answer. There is no publish button. Only published journeys can join a [collection](/journeys/collections/).

## Troubleshooting

| What you see | What to do |
| --- | --- |
| "Fill in the missing fields above, then run again." | Fill in **What do you want to find out?** and at least one turn. |
| "We couldn't draft the scenario." | Try again, or fill in the form yourself. What you wrote is kept. |
| A brand check is grayed out | Add your brand names to your Company Profile, then reopen the journey. |

## Next

- [Write checks that mean something](/journeys/write-checks/)
- [Collections and sharing](/journeys/collections/): run several journeys together and share one report.
- [Turn a gap into a fix](/journeys/turn-a-gap-into-a-fix/)