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

# Chat and the assistant

> Use Project context to ask sourced questions, teach missing knowledge, create durable assets, and collaborate.

Chat is the main way to work with Cromo. Start with the result you need, then give the assistant the Project context and constraints required to produce it.

A conversation can remain exploratory or create durable assets such as Knowledge, Data, a Dashboard, a Process Skill, a file, or a Workflow.

## Ask mode

Use **Ask** when you want Cromo to reason over the Project's existing context.

Examples:

* “Summarize the escalation policy and cite the relevant Sources.”
* “Which renewal records have no next action?”
* “Compare this uploaded contract with our standard renewal terms.”
* “Create a dashboard for renewals due this quarter.”
* “Draft a workflow for the weekly renewal review.”

The assistant can cite Project Sources and Knowledge so you can inspect the evidence behind an answer.

## Teach mode

Use **Teach** when your team knows something that is missing from the Project.

Good Teach requests are explicit and bounded:

> Enterprise renewals require a 90-day review. The Account Owner is responsible for the commercial proposal, while Customer Success provides the risk note.

Cromo turns the conversation into Source material that can feed the same Knowledge review process as uploaded or synced content. Teaching requires permission to write Knowledge.

## Attach the right context

You can attach files and Project references to a message, including:

* Sources and Knowledge pages;
* team files;
* data tables and models;
* Workflows;
* local file uploads.

Attach references when a request depends on a specific document, table, or definition. This narrows the task and makes review easier.

<Note>
  Chat uploads are limited to 10 MB per file. Source uploads use a separate ingestion pipeline and can be up to 50 MB.
</Note>

## Write better requests

A useful request normally includes four parts:

| Part        | Example                                      |
| ----------- | -------------------------------------------- |
| **Outcome** | Prepare the weekly renewal review            |
| **Scope**   | Customers renewing in the next 90 days       |
| **Rules**   | Group by owner and flag missing next actions |
| **Output**  | A concise summary plus a CSV file            |

A complete prompt might be:

> Using the Renewals table and the Renewal Policy page, prepare this week's review for customers renewing in the next 90 days. Group records by account owner, flag high-value contracts without a next action, cite the policy rule, and create a CSV of the flagged records.

## More prompts to try

### Support triage

```text theme={null}
Using the complaint email and Escalation Policy, classify the issue, cite the
rules that apply, calculate the response deadline, recommend an owner, and draft
an acknowledgement. Keep customer claims separate from verified facts.
```

### Operations review

```text theme={null}
Review the open purchase requests. Group them into incomplete, ready for
approval, and exception. For each request, cite the applicable policy threshold
and state the exact next action. Do not approve any request.
```

### Finance exceptions

```text theme={null}
Find open invoices that are overdue, missing a purchase order, above the review
threshold, or possible duplicates. Return a table with the reason, policy
citation, owner, and next action. Do not change payment status.
```

<Card title="Browse complete examples" icon="lightbulb" href="/examples/handle-customer-complaints">
  See how prompts become reviewed Knowledge, Data, Skills, Workflows, and Dashboards.
</Card>

## Review the response

For important work:

* open citations and compare key claims with the Source;
* inspect generated files before sharing them;
* verify dates, amounts, and owners against structured Data;
* review any proposed Dashboard, Skill, or Workflow before publishing or activating it;
* test external actions with a safe case.

## Conversation controls

Cromo keeps conversation history inside the Project. You can rename and pin conversations, keep them private, or share them with Project members.

Use a shared conversation for a decision or repeatable team process. Keep temporary investigations private until the context and output are ready for others.

## From conversation to system

Use chat to discover the process. Preserve the result when it becomes valuable:

* save a stable explanation as Knowledge;
* put changing records in a Data table;
* publish a Dashboard for recurring review;
* capture a reusable human-readable routine as a Process Skill;
* create a Workflow when the steps should execute consistently.

<Warning>
  The assistant can be wrong or work from outdated context. Check important answers against their Sources and keep the underlying Knowledge current.
</Warning>