> For the complete documentation index, see [llms.txt](https://learn.moselle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.moselle.io/mo/tips/mo-context-panel.md).

# Give Mo Context About Your Business

{% hint style="info" %}
**Quick Answer:** Open Mo, click the three-dot menu **(⋮)** in the top right, select **Settings**, and add a Company Description in the **Mo Configuration** panel. Describe your business model, custom terminology, sales channels, and how you define key metrics.
{% endhint %}

## What is the Mo Context Panel?

The **Mo Context Panel** — officially called **Mo Configuration** — is where you teach Mo about your business. It's a free-text field where you describe your company, products, sales channels, and the terminology your team uses.

By default, Mo only knows what's in your Moselle data. It doesn't know that you call your retail locations "doors," that "GWP" means gift with purchase, or that you're a DTC brand shipping through Shopify. The Context Panel changes that.

Think of it as a standing briefing that Mo reads before every conversation — so it can interpret your questions accurately, use the right terminology, and focus on what matters most to your business.

{% hint style="info" %}
**Why this matters:** A question like "Which SKUs are underperforming?" means something very different for a DTC skincare brand vs. a wholesale CPG company. The Context Panel is how Mo tells the difference.
{% endhint %}

***

## Where to find the Context Panel

**Time required:** 2–5 minutes

You can open Mo — and its Context Panel — from two places in Moselle:

**Option 1 — Ask Mo page** Navigate to the Ask Mo page using the first icon at the top of the left-hand sidebar (the glasses icon). This opens the full Mo chat interface as a dedicated page.

**Option 2 — From any page** Click the **"Hello! How can I help you?"** widget in the top right corner of any page. This opens Mo as a side panel without leaving the page you're on.

Once Mo is open:

{% stepper %}
{% step %}

### Open the menu

Click the **three-dot menu icon (⋮)** in the top right corner of the Mo chat window.
{% endstep %}

{% step %}

### Go to Settings

Select **Settings** from the dropdown menu.
{% endstep %}

{% step %}

### Add your Company Description

The **Mo Configuration** modal opens, showing the Company Description field. Add or update your context, then save.
{% endstep %}
{% endstepper %}

***

## What to include in your Company Description

There are no required fields or rigid format — write it like a short briefing note. Here's what makes Mo most useful:

| What to include                    | Why it helps Mo                                                                  |
| ---------------------------------- | -------------------------------------------------------------------------------- |
| Business type & model              | Frames analysis correctly (e.g., DTC vs. wholesale, B2B vs. B2C)                 |
| Product categories & key brands    | Helps Mo understand how your SKUs are grouped                                    |
| Sales channels                     | Retail, Shopify, Amazon, wholesale accounts — Mo will reference these accurately |
| Industry-specific terminology      | Custom terms like "doors," "GWP," "sell-in," "sell-through," etc.                |
| Seasonality & key planning periods | Helps Mo contextualize trends and forecasts                                      |
| How you define key metrics         | e.g., your definition of "sell-through rate" or "weeks on hand"                  |

### Example Company Descriptions

{% tabs %}
{% tab title="Beauty Brand" %}
*We're a DTC and wholesale beauty brand. Our product lines include skincare, body care, and fragrance. We sell through our own Shopify store, Sephora (where we track locations as "doors"), and a small number of specialty retailers. We use "GWP" to refer to gifts with purchase. Our planning year runs from February to January. We measure sell-through as units sold divided by units received at retail. Our peak season is Q4, starting in late September.*
{% endtab %}

{% tab title="Food & Beverage Brand" %}
*We're a CPG beverage brand focused on functional drinks. We sell B2B to grocery chains and DTC through our website. We use "velocity" to refer to units sold per store per week. Our key channels are Whole Foods, Sprouts, and Amazon. We track performance by "sell-through rate," which is sell-out divided by sell-in. We have two main SKU lines: sparkling and still. Our fiscal year starts in January.*
{% endtab %}
{% endtabs %}

***

## Quick reference: what to include vs. skip

| ✅ Include                                  | 🚫 Skip                                      |
| ------------------------------------------ | -------------------------------------------- |
| Business model (DTC, wholesale, B2B, etc.) | Full SKU lists (already in Moselle)          |
| Product categories & key brands            | Channel names already visible in your data   |
| Custom terminology & abbreviations         | Descriptions of every product variant        |
| How you define key metrics                 | Technical integration details                |
| Key channels & planning periods            | Anything Mo can already infer from your data |
| Seasonal patterns                          |                                              |

***

## Best practices for keeping your context current

**Update it when your business changes** Launched a new sales channel? Added a product line? Changed how you define a key metric? Update the Company Description to reflect it — Mo won't know unless you tell it.

**Keep it concise but specific** A few focused sentences are more useful than a wall of text. Lead with details most likely to affect how Mo interprets your data questions.

**Add terminology before you need it** If you're starting a new planning cycle where "sell-in" becomes a key term, add it to the context before you begin asking Mo about it.

**Review it each season or quarter** A 2-minute review at the start of each planning period can prevent weeks of miscommunication.

**Don't duplicate what's already in your data** You don't need to list every SKU or channel name — Mo can already see those in Moselle. Focus on what Mo can't infer: your terminology, business model, and metric definitions.

***

## Related guides

{% content-ref url="/pages/HNe3qiLOPZnSe0stHRX3" %}
[Get Better Results with Mo](/mo/tips/tips-for-better-prompts.md)
{% endcontent-ref %}

{% content-ref url="/pages/DAsnRIRTbbjM6bgR0RLM" %}
[Save Your Favourite Prompts](/mo/tips/save-favourite-prompts.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.moselle.io/mo/tips/mo-context-panel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.