---
title: "Brainfish Agent Setting: Include Business Context"
description: "Overview"
canonical_url: "https://help.brainfi.sh/articles/brainfish-agent-setting-include-business-context-ppXnMMJXgK"
md_url: "https://help.brainfi.sh/articles/brainfish-agent-setting-include-business-context-ppXnMMJXgK.md"
---
# Brainfish Agent Setting: Include Business Context

## Overview

The **Include Business Context** switch is an advanced agent setting in the Brainfish Platform that helps an agent stay aligned with a customer’s product, terminology, and knowledge base.

## What the setting does

When **Include Business Context** is enabled, the agent:

* **Learns context from the customer’s knowledge base** by automatically extracting relevant product and business context from available knowledge.
* **Retains domain-specific vocabulary** so responses match the customer’s terminology and naming conventions.
* **Updates context as knowledge changes** (it is **not** a static prompt). As the knowledge base evolves, the business context evolves with it.
* **Reduces answer drift** by keeping responses grounded in the customer’s actual business and product context.

## Where to find it

* Located in **Agent advanced settings**.
* Described as an **L2 (Layer 2) setting**.

## Access and default behavior

* The switch is **currently superadmin-only** (not visible to regular customers).
* There is **no documented policy decision** confirming whether it should be enabled **by default** for all customers.

## Guidance: should it be enabled by default?

This is a **product decision**. Before enabling it by default across customers, align internally on:

* **Readiness for broader rollout** (beyond superadmin-only access)
* **Cost/performance impact**, since enabling the feature may pass additional context to the answer service
* Whether the **superadmin gate** is intentional long-term behavior or a temporary testing/validation precaution

## Additional information

* At the time of this conversation, there were **no existing support docs** for this switch; information was sourced from internal discussion.

## Next steps

* Publish this article (or an expanded version) to close the documentation gap.
* Confirm internal ownership and decide:
  * Whether to keep the setting **superadmin-only**
  * Whether to enable it **by default** for new and/or existing customers
  * Any guardrails (e.g., rollout plan, performance monitoring) needed for wider adoption