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

# Add business context

> Explain your offer and sales process where website copy leaves gaps.

<div className="darwin-location"><strong>Find it in Darwin</strong> Settings → Knowledge → Business context <a href="https://app.meetdarwin.ai/admin/settings/knowledge">Open this screen ↗</a></div>

Business context gives Darwin the facts it needs alongside your website pages. Keep facts here; use [Identity & behavior](/assistant/identity-and-behavior) for instructions about how to respond.

## A useful starting template

Copy this outline, replace each bracket, and remove anything that does not apply:

```text theme={null}
What we do: [A plain-language description of the product.]
Who we help: [Best-fit companies, teams, and use cases.]
What customers ask: [Common questions and accurate answers.]
Pricing context: [How pricing works and where current prices live.]
Good reasons to book: [When a conversation with sales is useful.]
What we do not offer: [Clear limits and unsupported capabilities.]
If the answer is unknown: [How to acknowledge the gap and offer help.]
```

Select **Save changes**, then test questions that rely on the new information.

## Write for accurate answers

* State capabilities directly: “We support X” is more useful than “We are the most powerful platform.”
* Keep plan names, limits, and commercial terms consistent with your live website.
* Explain fit without asking the assistant to invent a qualification score or a promise.
* Include the next useful step when a visitor needs a person.
* Remove contradictory or outdated facts instead of appending a second version.

Do not include passwords, API keys, payment information, or confidential details that should never appear in a visitor-facing answer.

## When to update it

Review business context whenever pricing, packaging, supported integrations, positioning, or your sales process changes. Refresh affected website pages too, then run the same test questions again.

[Build a repeatable assistant test →](/assistant/test-assistant)