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

# Ask Lane

> Ask questions across your whole workspace in plain language — and get answers grounded in your real feedback, signals, and customers.

Ask Lane is where you interrogate your workspace in plain language. Instead of building a filter or scanning a list, you ask — "what are enterprise customers frustrated by this quarter?", "which accounts are behind the SSO requests?" — and Lane answers from your real [Feedback](/insights), [Signals](/signals), [Customers](/customers), and [Plans](/docs).

It's the home surface of Lane, and the fastest way to get your bearings: what's coming in, what's rising, and where to look next.

## What you can ask

Ask Lane reads across everything in your workspace, so a single question can pull from feedback, signals, and customer data at once:

* "What are the top themes from enterprise customers in the last quarter?"
* "Which customers are behind the reporting complaints, and what's their revenue?"
* "Summarize what we've heard about onboarding since the last release."
* "What's the highest-priority Signal we haven't acted on yet?"

Because it searches by meaning as well as keywords, you don't have to phrase things the way the data was written — describe what you're after and Lane finds it.

## Where you'll find it

* **On the home surface** — open Lane and ask anything to start. It's also where the **Priority** list lives: a short, ranked list of the surfaced Signals most worth your attention right now, so you land on what matters instead of a blank page.
* **Anchored to a Signal or Plan** — open **Ask Lane** from a [Signal](/signals) or [Plan](/docs) to ask questions scoped to that item and the data behind it.

## Bring in outside context

Some answers live outside Lane. Connect a source once in **Settings → Integrations** and Lane can draw on it in a conversation:

* **[GitHub](/github)** — connect a repository and ask questions about your code. Most useful for non-engineers who need answers that live in the codebase — "is this already built?", "what does the enterprise tier actually include?" — without pinging engineering. Lane reads code; it never writes back.
* **[Google Drive](/google-drive)** — attach files to a conversation — call transcripts, research, strategy docs — and ask across them. "Pull the product requests out of last week's calls." Files stay in Drive; Lane reads them on demand.

## From a question to a decision

Ask Lane is read-only — it answers, explores, and summarizes, but it doesn't create or change anything. Acting on what you find happens where the record lives: open the [Signal](/signals) or piece of [feedback](/insights) Lane surfaced and use its **Plan** action to draft a [Plan](/docs). Exploring first, then drafting from the right record, produces far sharper Plans than starting cold.

## Getting better results

* **Be specific.** "Top feedback from enterprise accounts last quarter" gets somewhere; "what's important?" doesn't. Segment, timeframe, product area — the more context, the better the answer.
* **One ask per turn.** Lane is sharpest when each turn has a clear goal. Bundling "find X, summarize Y, then draft Z" dilutes the result — break it into steps.
* **Explore before you draft.** Ask questions to refine your direction, then move into a Plan. One-shot "write the whole thing" prompts produce thin results because no thinking happened first.
* **Say what's off.** If an answer isn't quite right, reply with what to fix — narrower scope, a different angle, more detail on one point — rather than starting over.

## Credits

Ask Lane uses AI credits. See [Billing](/billing) for your plan's allowance.

## AI privacy and data usage

* Lane does **not** use your data to train its own AI models.
* Data processed for AI features is shared only with trusted partners to deliver those features.
* Your data is **not** used to train external models without permission.

Questions? Contact us at [**support@laneapp.co**](mailto:support@laneapp.co).

## FAQs

**Q: Can Ask Lane change my data?**\
A: No — it's read-only. To act on something, open the Signal or feedback it surfaced and use that record's **Plan** action to draft a Plan.

**Q: Why did it ask me a clarifying question?**\
A: When a request could go several ways, Lane asks first to avoid wasted work.

**Q: Why didn't it find something I know is there?**\
A: Try rephrasing — Lane searches by meaning as well as keywords, and a small change in wording can surface it.

**Q: Does it work on data I haven't imported?**\
A: Only what's in your workspace, plus connected sources like GitHub and Google Drive.