> For the complete documentation index, see [llms.txt](https://support.kea.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.kea.ai/kea-brand-portal-setup/how-to-customize-your-brand-tone-with-kea-ai.md).

# How to Customize Your Brand Tone with Kea AI

Have your Voice AI emulate your brand persona and tone using Kea's Brand Tone Configuration.

With Kea AI, you can make your voice assistant truly sound like your brand. The **Brand Tone** space lets you define how your AI should speak and behave — from word choice and personality to the overall “feel” of the interaction. Whether you want a warm Texas hospitality vibe, a coastal surfer style, or something uniquely your own, this feature ensures every customer call matches your brand identity.

{% stepper %}
{% step %}

### 1. Log into the Kea Brand Portal

Go to <https://app.kea.ai> and sign in with your account credentials.
{% endstep %}

{% step %}

### Navigate to Brand Overview

From the **Brand Overview**, click the **Edit** button to open your brand details.

<figure><img src="https://634693676-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fld1rf8bDr2mdDP0MIP%2Fuploads%2FZSGCHafyMO26XWj4LYdV%2FScreenshot%202025-09-17%20at%209.37.47%E2%80%AFPM.png?alt=media&amp;token=aa28ac4b-257c-441b-9f1e-e6185d5d34e4" alt="" width="188"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Open the Brand Tone Section

Scroll down to the **Brand Tone** text box.\
This is where you’ll define your assistant’s personality, word choices, and speaking style.
{% endstep %}

{% step %}

### Write Your Brand Tone Guidelines

In this space, describe exactly how your AI should sound.\
For example:

* “You are from Texas, born and raised. Use words like howdy, y’all, darling, or sweetie, and speak with Texas warmth and charm.”
* “You are a surfer from the California coast. Use casual phrases like dude, chill, and hang loose, with a laid-back coastal vibe.”
* “You are a high-end French café. Speak with elegance, poise, and hospitality, always polite and professional.”

The more detail you provide, the more your AI will emulate your brand.

<figure><img src="https://634693676-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fld1rf8bDr2mdDP0MIP%2Fuploads%2FmXqRp4dv5UxHRGnUN4uG%2FScreenshot%202025-09-17%20at%209.35.23%E2%80%AFPM.png?alt=media&amp;token=a672aa88-c7c6-4695-baaa-5f696aabfb9a" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Save Your Changes

When finished, click **Save changes**. Your updated tone will immediately apply to customer calls going forward.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
✅ **Pro Tip:** Pair your Brand Tone with a curated AI voice from the **Voice Selection** menu to give your assistant both the right sound and the right personality.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.kea.ai/kea-brand-portal-setup/how-to-customize-your-brand-tone-with-kea-ai.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.