> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firstresonance.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Overview
> What ION Intelligence is, where it appears, what it can see about the page you are on, and who is allowed to reach it.
ION Intelligence is a conversational assistant that answers questions about the work in front of
you, grounded in your organization's own records.
The assistant is a **companion** rather than a page. It rests as a pill in the bottom-right corner
of every screen and expands into a floating box, or into a rail docked to the left or right edge
that the page reflows beside. Either way the record you are asking about stays on screen while you
talk about it. For the steps, see
[Ask ION a question](/automate-with-ion/ion-intelligence/ask-ion).
## Where the assistant appears
| Surface | What it is |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The pill and the expanded companion | On every desktop page. Open it from the pill, from **ION Intelligence** in the sidebar, or with `⌘I` (`Ctrl+I` on Windows and Linux). |
| The **ION** tab in the mobile bottom navigation | A full-screen conversation, with the same voice dictation as the desktop composer. |
| Suggested-action cards | Tiles on **Kits**, **Purchases**, and **Inventory** that hand the assistant a set of findings. See [Suggested-action cards](#suggested-action-cards). |
| Suggested prompts | Starting prompts for the page you are on, listed above the composer until you pick one or hide the row. |
| Suggestion pills on a draft procedure step | Labels such as **Improve**, **Add safety warnings**, and **Add quality checkpoints** ask the assistant to rewrite the step. The answer arrives as a proposal you review rather than as an edit. |
## What the assistant can see
Two channels feed a question, and both render as chips above the composer.
**Page context** comes from the URL, so the assistant knows which record you are looking at without
you attaching it. Depending on your settings, it may not be released to your organization yet:
| Page | What it contributes |
| ----------------------------------------------------------------------------------------- | ------------------------------------------ |
| A procedure, and the step selected on it | The procedure, and the procedure step |
| A run's **Overview**, **Steps**, or **Dependencies** tab, and the run step selected on it | The run, and the run step |
| A part in the parts library | The part |
| An issue | The issue |
| A purchase order | The purchase order |
| A standard step | The step |
| A list page | Nothing, because no single record is named |
**Attached context** is what you add yourself, from **Add** or by typing `@`. A page-derived chip
carries no remove control, so the two are told apart on sight.
A chip's label needs a lookup, but the record behind it does not. A label that loads slowly, or
fails to load, costs the chip and never the record the question is grounded on.
## Conversations
A conversation is a thread the assistant follows for its own duration. **New** starts a fresh one,
and **Recent conversations** lists the ones you have already had, so you can reopen or delete one.
Reopening replays the thread as it was, including the tables and cards a turn drew, rather than as
flat text.
Conversations are private to your account. The **Add** picker's recent picks are remembered in the
browser you used, so they do not follow you to another device.
## Suggested-action cards
Three tiles put a queue in front of you and hand the assistant the findings behind it, so the
conversation opens on specific records instead of on a blank question. Each shows a count and one
line of detail, and clicking it opens the companion with those findings already sent. The assistant
recommends and links; it changes nothing on its own. A tile appears on its page only when it has
something to show, and **Stale purchase orders** also needs in-app analytics turned on.
| Card | Page | What it counts |
| ------------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Kits ready to build** | **Kits** | Your open, fully fillable kits whose parts cleared an inspection run in the last seven days |
| **Stale purchase orders** | **Purchases** | Open purchase orders past their expected arrival with overdue lines still awaiting receipt, ranked by outstanding value |
| **Released inventory** | **Inventory** | Available inventory that became available because its run was canceled or partially completed |
Clicking **Kits ready to build** also filters the **Kits** table to exactly the kits it counted, so
the rows match the number on the tile.
**Released inventory** is a review queue rather than a defect list. Returning a canceled run's
stock to **Available** is intended behavior, and a lot whose other run completed is legitimately
available, so the assistant asks you to confirm before recommending a move or a scrap.
## Getting help from a person
The support chat lives inside the companion. **Contact support** sits in the context row beside the
composer and opens the support panel over the conversation, so the thread you were describing stays
on screen. When you tell the assistant that something is broken, or ask for a person, it offers the
same control as a **Contact support** chip in the thread. The chip only offers, and dismissing it
stops it coming back for the same reason in that conversation.
## Availability
ION Intelligence is off until an admin turns it on for the organization, and which surfaces you see
then depends on what First Resonance has released to it. See
[Turn on ION Intelligence](/administration/organization-settings/enable-ion-intelligence).