> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/ai/using-console-for-natural-language-search.md).

# Using Console for Natural Language Search

### Overview

Console supports natural language queries across Project content.

It returns answers with links to source items.

{% hint style="info" %}
Screenshot placeholder: Console panel showing a query, answer, and source links.
{% endhint %}

### Key Concepts

* **Query**: natural language prompt
* **Answer**: generated response
* **Sources**: item links used to support an answer
* **Scope**: Organization and Project boundaries for results

### How It’s Used

Use Console to answer questions without locating the source item first.

Use it for cross-item questions, such as blockers, approvals, and overdue work.

### Benefits

* Faster discovery of decisions and rationale
* Better traceability through source links
* Reduced manual navigation across Projects

### Setup Steps

#### What Console can search (typical)

Depending on Account configuration, Console may include:

* requirements
* tasks
* tests
* comments and activity
* meeting summaries (if enabled)

Results respect Account, Organization, and Project access.

{% stepper %}
{% step %}

### Open Console

1. Open **Console**.
2. Confirm Organization and Project scope (if prompted).
   {% endstep %}

{% step %}

### Ask a focused question

For example:

* `what tasks are overdue this week`
* `show blockers for order-to-cash`
* `summarize progress for acceptance testing`
* `find requirements that mention the ERP system`

Include an object type (tasks/requirements/tests) for cleaner results.
{% endstep %}

{% step %}

### Open the source items

1. Review the answer.
2. Click a source link to verify details.
3. Share the source link, not a copied answer.
   {% endstep %}
   {% endstepper %}

### Best Practices

{% hint style="info" %}

* Add time windows: “last 7 days”, “this month”.
* Add owners: for example, “assigned to a Teammate name”.
* Ask for “sources” when traceability is required.
  {% endhint %}

### Troubleshooting

<details>

<summary>I get no results</summary>

Try:

* removing extra constraints
* searching for one unique keyword
* confirming the correct Project scope

</details>

<details>

<summary>Results don’t include an item I can see elsewhere</summary>

Possible causes:

* the item is in a different Project
* Console indexing hasn’t caught up yet
* access permissions differ by object type

</details>

### Summary

Console queries should be focused and validated using sources.

Use Save Views to track follow-up work surfaced by queries.

Related:

* [Console Search Tips and Examples](/ai/console-search-tips-and-examples.md)
* [Finding Decisions and Approvals](/ai/finding-decisions-and-approvals.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/ai/using-console-for-natural-language-search.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.