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

# Widget Modes Explained

> Understand the differences between Chat, Voice, and Chat & Voice widget modes and choose the best one for your website.

Every VozAgent widget operates in one of three modes: **Chat**, **Voice**, or **Chat & Voice**. The mode you choose determines how visitors interact with your AI assistant on your website. This article explains each mode in detail and helps you decide which one is the best fit.

***

## The Three Modes

### Chat Mode

In Chat mode, visitors interact with your assistant through text messages only. They type their questions and receive written responses -- similar to a live chat experience, but powered by your AI assistant.

**What visitors see:** A chat bubble that opens into a text conversation window with a message input field.

**Best for:**

* Websites where visitors prefer a quiet, text-based experience
* Situations where visitors may be in public or at work and can't speak out loud
* Businesses that want to avoid microphone permission prompts in the browser
* Mobile visitors who may not want to use their microphone

**Trade-off:** Visitors who prefer speaking over typing may find this mode less convenient.

### Voice Mode

In Voice mode, visitors speak directly to your assistant through their browser microphone. It's like a phone call that happens right on your website -- no dialing required.

**What visitors see:** A voice interface that prompts them to speak. The browser will ask for microphone permission on first use.

**Best for:**

* Businesses that want a phone-like experience on their website
* Assistants that are primarily optimized for voice conversations
* Visitors who prefer speaking over typing
* Situations where hands-free interaction is valuable

**Trade-off:** Visitors need to grant microphone access in their browser, which some may decline. This mode also doesn't work well in noisy environments.

### Chat & Voice Mode (Default)

Chat & Voice mode gives visitors both options. They can type messages or switch to voice -- whichever they prefer. This is the **default mode** when you create a new widget key.

**What visitors see:** A chat interface with the option to switch to voice interaction.

**Best for:**

* Most businesses, because it lets each visitor choose their preferred method
* Websites with a diverse audience (some visitors prefer typing, others prefer talking)
* When you're not sure which mode to choose -- this covers both bases

**Trade-off:** Slightly more complex interface than a single-mode widget, though the visitor experience is still straightforward.

***

## Mode Comparison

| Feature                        | Chat | Voice  | Chat & Voice    |
| ------------------------------ | ---- | ------ | --------------- |
| Text-based messaging           | Yes  | No     | Yes             |
| Voice interaction              | No   | Yes    | Yes             |
| Microphone permission required | No   | Yes    | Only for voice  |
| Works in noisy environments    | Yes  | Poorly | Yes (via chat)  |
| Hands-free interaction         | No   | Yes    | Yes (via voice) |
| Default for new widgets        | No   | No     | Yes             |

***

## How Modes Appear in the Dashboard

On your **Widgets** page, each assistant card displays a **mode badge** so you can see at a glance how each widget is configured:

* **Chat** -- Text-based chat only
* **Voice** -- Voice-based interaction only
* **Chat & Voice** -- Both options available

The badge also includes a small icon (a message icon for Chat, a phone icon for Voice, or a globe icon for Chat & Voice).

***

## Changing the Mode

When you first create a widget key, it defaults to **Chat & Voice** mode. Currently, the mode is set at the time of key creation. If you want to change the mode:

1. Open the widget detail view by clicking on the assistant's card.
2. The current mode is displayed at the bottom of the **Tracking Code** tab.
3. To switch modes, delete the existing widget key and create a new one with the desired mode.

**Important:** Deleting a widget key immediately disables the embed code using that key. Make sure to update the embed code on your website after creating the new key.

***

## How the Mode Affects the Embed Code

The embed code snippet is slightly different depending on the mode:

**Chat & Voice:**

```html theme={null}
<!-- VozAgent Chat & Voice Widget -->
<script
  src="https://api.vozagent.ai/widget.js"
  data-widget-key="your-key-here"
></script>
```

**Chat Only or Voice Only:**

```html theme={null}
<!-- VozAgent Chat Widget -->
<script src="https://api.vozagent.ai/widget.js" data-widget-key="your-key-here"></script>
```

The widget script automatically adjusts its behavior based on the mode associated with your key. You don't need to add any extra configuration.

***

## Recommendations by Business Type

Here are some general guidelines based on common business scenarios:

**Home service businesses (plumbing, HVAC, electrical):**
Use **Chat & Voice**. Many of your website visitors are homeowners who may want a quick text chat during the day or a voice conversation when they have a moment.

**Professional services (law firms, accounting, consulting):**
Use **Chat** mode. Visitors to professional service websites often prefer the privacy and formality of text communication.

**Restaurants, salons, and retail:**
Use **Chat & Voice**. Give visitors the flexibility to quickly type a question about hours or availability, or speak if they prefer.

**If you're unsure:**
Start with **Chat & Voice** (the default). You can always narrow it down later based on how your visitors actually use it.

***

## Related Articles

* [Widgets Overview](/help/widgets/widgets-overview) -- What widgets are and how they work.
* [Creating a Widget](/help/widgets/creating-a-widget) -- Step-by-step guide to creating your first widget.
* [Installing and Customizing Your Widget](/help/widgets/installing-and-customizing) -- Customize appearance, behavior, and embed the code.