> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/device-applications/voice-chat.md).

# Voice Chat

The BlueFletch Chat application integrates with the Twilio API to enable users to have audio and video calls with each other. Users can initiate and accept calls through BlueFletch Chat, with the call type (audio or video) determined by the selected option in the app.

### Audio Call

**Buttons:** Users can answer or end a call, mute or unmute the microphone, or switch to speakerphone mode.

**TextViews:** This provides visual information or prompts, such as displaying the caller's name or indicating call status.

**Select Speaker Dialog:** This allows users to choose the audio output device (the earpiece speaker or the device's external speaker).

### Video Call

**Buttons:** Users can initiate or end a video call, toggle the camera on or off, mute or unmute the microphone, or switch between front and rear cameras.

**TextViews:** This provides visual information or prompts, such as displaying the caller's name or indicating call status.

**Select Speaker Dialog:** This allows users to choose the audio output device (the earpiece speaker or the device's external speaker).


---

# 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://docs.bluefletch.com/bluefletch-enterprise/product-guides/device-applications/voice-chat.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.