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

# Calls Overview

> Understanding the four types of calls in Orova

## Call types

Orova supports four ways to communicate with an agent:

| Type      | How to use             | Use case                                |
| --------- | ---------------------- | --------------------------------------- |
| **Phone** | API or Dashboard       | Inbound/outbound phone calls via Twilio |
| **Web**   | Widget                 | Browser-based voice calls               |
| **Video** | Widget or Meeting Link | Video avatar calls                      |
| **Chat**  | Widget                 | Text-based conversations                |

## How calls work

### Voice engine

All voice-based calls (phone, web, video) flow through a real-time engine:

1. User speaks → speech is converted to text
2. The LLM generates a response based on the conversation
3. The response is converted back to speech
4. If tools are needed (CRM lookups, calendar bookings, etc.), they run during the conversation

### Chat engine

Chat uses a simpler text-in, text-out flow with streaming responses.

## Call history

All calls are automatically logged with:

* Full transcript
* AI-generated summary
* Sentiment analysis
* Call outcome and disposition
* Call duration and cost
* Recording (if enabled)
* Contact information and custom fields

View call history in the dashboard under **History**, or query via the [API](/api-reference/history/list).

## Next steps

<CardGroup cols={2}>
  <Card title="Phone Calls" icon="phone" href="/calls/phone-calls">
    Inbound and outbound via Twilio
  </Card>

  <Card title="Web Calls" icon="globe" href="/calls/web-calls">
    Browser-based WebRTC calls
  </Card>

  <Card title="Video Calls" icon="video" href="/calls/video-calls">
    Video avatar calls
  </Card>

  <Card title="Chat" icon="message" href="/calls/chat">
    Text-based conversations
  </Card>
</CardGroup>