Skip to content
Tigy AI
/
Legal centerDashboard
OverviewDeveloper
Overview

Get started

  • Introduction
  • Overview
  • First agent
  • Tools and data
  • Concepts
    • How it works
    • Calls and runs

Configure

  • Behavior
    • Prompting
    • Conversation flow
  • Voice and models
    • LLM
    • Voice
    • Transcription
    • Fallbacks
    • Audio library
  • Tools
    • Tools
    • HTTP API
    • MCP
    • Credentials
    • Call transfer
    • End call
  • Knowledge base
  • Testing
  • Agent ID

Deploy

  • Publishing
  • Versions
  • Telephony
    • Introduction
    • Connect telephony
    • Inbound calls
    • Twilio
    • Telnyx
    • SIP

Monitor

  • Runs and usage
  • Reports
  • Troubleshooting

Workspace

  • Workspace
  • Members and permissions
  • Billing
  • Security
  • Privacy

Developer

  • Call data
Dashboard
Explore pages
Overview

Get started

  • Introduction
  • Overview
  • First agent
  • Tools and data
  • Concepts
    • How it works
    • Calls and runs

Configure

  • Behavior
    • Prompting
    • Conversation flow
  • Voice and models
    • LLM
    • Voice
    • Transcription
    • Fallbacks
    • Audio library
  • Tools
    • Tools
    • HTTP API
    • MCP
    • Credentials
    • Call transfer
    • End call
  • Knowledge base
  • Testing
  • Agent ID

Deploy

  • Publishing
  • Versions
  • Telephony
    • Introduction
    • Connect telephony
    • Inbound calls
    • Twilio
    • Telnyx
    • SIP

Monitor

  • Runs and usage
  • Reports
  • Troubleshooting

Workspace

  • Workspace
  • Members and permissions
  • Billing
  • Security
  • Privacy

Developer

  • Call data
Dashboard

Documentation / Calls & Runs

Calls & Runs

The lifecycle of a call and how runs capture its results

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.

stateDiagram-v2
    [*] --> Ringing: Number dialed
    Ringing --> Connected: Caller answers
    Ringing --> Ended: No answer
    Connected --> Ended: Conversation completes
    Connected --> Ended: Error or disconnect
    Ended --> [*]

For inbound calls, the flow starts when the caller dials in and the telephony provider routes the call to Tigy AI.

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:

FieldDescription
statusFinal run state
recording_urlDownload URL for the call audio
transcript_urlDownload URL for the conversation transcript
gathered_contextStructured data extracted by the agent during the call
initial_contextThe data available when the conversation starts
usage_infoDuration in seconds, token count
cost_infoCost in USD
← Back to documentation
© 2026 Tigy AItigyai.com ↗

On this page

  • Calls vs runs
  • Call lifecycle
  • Inbound calls
  • Web Calls
  • What a run contains