Calls & Runs

Every time a agent executes, Tigy AI creates a run. The run is the record of that execution: what was said, what data was collected, how long it took, and what it cost.

Calls vs runs

A call is the audio connection — whether over the phone via a telephony provider, or through the browser via Web Call.

A run is the Tigy AI record of the agent execution. Every inbound phone or browser conversation creates a run containing its transcript, recording, gathered context, usage, and cost.

Call lifecycle

The call lifecycle tracks the telephony connection — from the moment a number is dialed to when the line drops.```mermaid stateDiagram-v2 [] --> Ringing: Number dialed Ringing --> Connected: Caller answers Ringing --> Ended: No answer Connected --> Ended: Conversation completes Connected --> Ended: Error or disconnect Ended --> []

## Inbound calls

Inbound calls are initiated by the caller. Your telephony provider routes incoming calls to a Tigy AI agent via a webhook URL. Use them for support lines, hotlines, and IVR replacement.

## Web Calls

Web Call lets you talk to your agent directly from the browser — no phone number or telephony setup required. It runs the full pipeline: STT, LLM, TTS, recording, and transcript, exactly the same as a phone call.

Use it to try out your agent before going live. The run view shows the live transcript as the conversation progresses, any tool or function calls the agent makes in real time.

## What a run contains

After a call completes, the run record includes:

| Field | Description |
|---|---|
| `status` | Final run state |
| `recording_url` | Download URL for the call audio |
| `transcript_url` | Download URL for the conversation transcript |
| `gathered_context` | Structured data extracted by the agent during the call |
  | `initial_context` | The data available when the conversation starts |
| `usage_info` | Duration in seconds, token count |
| `cost_info` | Cost in USD |