> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Ask Ellie web quickstart

> Ask a grounded question in the Entelligence web app, inspect the source scope, and verify the answer.

Start with a question whose answer you already know. This tests source access, freshness, identity, and interpretation without requiring a write action.

## Prerequisites

* Access to the Entelligence workspace
* At least one connected engineering source
* Permission to view the repository, team, project, or incident you will ask about

## Run the first query

<Steps>
  <Step title="Open Ask Ellie">
    Go to [**Ask Ellie**](https://app.entelligence.ai/ask-ellie). Complete the brief first-run tour if it appears.
  </Step>

  <Step title="Choose a known scope">
    Pick one repository and a short time range with a known pull request or incident.
  </Step>

  <Step title="Ask for evidence">
    Ask: “In repository OWNER/REPO during the last 7 days, list the pull requests that merged and include the title, author, merge time, and source link.”
  </Step>

  <Step title="Verify">
    Compare the returned items with the Git provider. Check missing items, timezone, repository scope, and links.
  </Step>
</Steps>

## Refine a question

If the result is too broad:

* Name the repository or service.
* Add an exact date range.
* Ask for a table.
* Specify the metric or event.
* Request source links.
* State that no action should be taken.

If the result is incomplete:

* Confirm the connector is healthy.
* Check repository or team permissions.
* Refresh or synchronize the source.
* Check user and project mapping.
* Ask Ellie which source or time range it used.

## Test a cross-source question

After one-source verification, try:

> For the three pull requests with the longest review cycle in OWNER/REPO this month, show the linked tickets and whether any related incident pattern is active.

The answer should clearly distinguish available context from missing ticket or incident data.

## Test an action safely

Use a reversible, low-impact action such as drafting a reminder or report instruction. Review the destination and content before confirming. Do not test ticket creation, external updates, fix generation, or broad channel delivery in production.

## Verify success

* The answer uses the intended workspace and source.
* Dates and timezone are understood.
* Returned links open the expected items.
* Missing context is stated rather than invented.
* A requested no-write boundary is respected.
* Any proposed write presents a clear destination and action.

## Next step

Browse the [prompt library](/ask-ellie/prompts) or configure [Slack](/ask-ellie/slack).