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

# Configuring a Copilot

> Define your Copilot's name, instructions, and personality

## How configuration works

When you describe the assistant you want, Gainable's Copilot Planner analyzes your request and the Copilot Builder creates it. The Copilot stays synced with your app. As you add data models or features, you can update the Copilot to work with them.

<Steps>
  <Step title="Describe your Copilot">
    Tell Gainable what kind of assistant you want, what it should know, and how it should behave.
  </Step>

  <Step title="Planner analyzes">
    The planner determines the Copilot's name, instructions, data access, and configuration.
  </Step>

  <Step title="Builder creates">
    The builder sets up the Copilot with all its properties and connects it to your app.
  </Step>

  <Step title="Stays synced">
    As your app changes, you can update the Copilot through follow-up prompts.
  </Step>
</Steps>

## Properties

| Property                  | Description                                                               |
| ------------------------- | ------------------------------------------------------------------------- |
| **Name**                  | Display name shown in the Copilot header (e.g. "Sales Coach")             |
| **Description**           | Short summary of what the Copilot does, shown to users                    |
| **Instructions**          | System prompt that defines behavior, tone, and rules                      |
| **Conversation starters** | Pre-defined prompts displayed as buttons to help users begin              |
| **Web search**            | Whether the Copilot can search the web for additional information         |
| **Data access**           | MCP Server connection to your app data. Optionally restricted with scopes |
| **Knowledge**             | Uploaded documents the Copilot can reference when answering               |

## Writing good prompts

Be specific about what the Copilot should do, who it helps, and what data it needs.

<CodeGroup>
  ```text Good prompt theme={null}
  Create a Sales Coach Copilot for our sales team.
  It should:
  - Help reps find deals by status, company, or amount
  - Answer questions about our sales process
  - Use a friendly, encouraging tone
  - Start conversations with: "Show my open deals",
    "What deals are closing this month?",
    "Find deals over $10k"
  - Have access to deals and contacts data
  - Be able to search the web for company information
  ```

  ```text Vague prompt theme={null}
  Add an assistant to help with sales stuff.
  ```
</CodeGroup>

## Writing effective instructions

The Copilot's **instructions** act as its system prompt. They define how it behaves in every conversation. Good instructions include:

* **Role definition.** Who the Copilot is and what it specializes in.
* **Tone and personality.** How it should communicate.
* **Rules and boundaries.** What it should and shouldn't do.
* **Data awareness.** What data it has access to.

### Example instructions

```text theme={null}
You are Sales Coach, a helpful Copilot for the sales team.

Your role:
- Help reps find and analyze their deals
- Provide pipeline insights and status updates
- Suggest next steps based on deal stage

Tone:
- Friendly and encouraging
- Concise, prefer bullet points over long paragraphs
- Use data to back up suggestions

Rules:
- Always confirm before making changes to deals
- If you don't know something, say so
- Focus on deals and sales, redirect other questions
```

## Conversation starters

Conversation starters are pre-defined prompts displayed as clickable buttons when the Copilot opens. They help users discover what the Copilot can do.

### Best practices

* **Keep them short.** 3 to 8 words per starter.
* **Make them varied.** Cover different capabilities.
* **Be domain-specific.** Match your Copilot's purpose.
* **Use action language.** Start with verbs.

<CodeGroup>
  ```text Good starters theme={null}
  "Show my open deals"
  "Deals closing this month"
  "Find deals over $10k"
  "Pipeline summary"
  ```

  ```text Weak starters theme={null}
  "Help me"
  "What can you do?"
  "Tell me something"
  "Hi"
  ```
</CodeGroup>

## Web search

Enabling web search lets the Copilot look up external information during conversations.

**When to enable:**

* The Copilot needs current information (news, market data, company details)
* Users might ask questions beyond your app data and documents

**When to skip:**

* The Copilot only works with internal data
* You want to keep responses focused on your content
* Sensitive contexts where external information could be misleading

## Updating a Copilot

You can update Copilots through follow-up prompts at any time:

```text theme={null}
Update the Sales Coach Copilot to greet users by name
and add a conversation starter for "Top deals this week"
```

```text theme={null}
Change the support Copilot's tone to be more formal
and remove the web search capability
```

```text theme={null}
Add a new conversation starter: "Check order status"
```

## Tips

<AccordionGroup>
  <Accordion title="Be specific about the domain">
    A Copilot that "helps with everything" is less useful than one focused on a specific area like sales, support, or HR.
  </Accordion>

  <Accordion title="Define tone and personality">
    Copilots feel more natural when they have a consistent personality. Specify whether it should be formal, casual, encouraging, or direct.
  </Accordion>

  <Accordion title="Mention data access explicitly">
    Tell the Copilot what data models it should use. "Give it access to deals and contacts" is much clearer than "let it see the data."
  </Accordion>

  <Accordion title="Test with real questions">
    After creating a Copilot, try asking it the kinds of questions your users would ask. Refine instructions based on the results.
  </Accordion>
</AccordionGroup>

## Learn more

<CardGroup cols={2}>
  <Card title="Data access" icon="database" href="/copilots/data-access">
    Connect your Copilot to app data via MCP
  </Card>

  <Card title="Knowledge bases" icon="book" href="/copilots/knowledge">
    Upload documents for your Copilot
  </Card>

  <Card title="Embedding" icon="message-bot" href="/copilots/embedding">
    Place the Copilot chat in your app
  </Card>

  <Card title="Overview" icon="comments" href="/copilots/overview">
    Back to Gaia Copilot overview
  </Card>

  <Card title="Gaia Autopilot" icon="robot" href="/autopilot/overview">
    Looking for the autonomous side? Agents run on their own
  </Card>
</CardGroup>