Phone Connection

​

What is a Phone Connection?

A Phone Connection tells Galtea how to reach your AI agent over the phone. Instead of calling an HTTP API, Galtea dials your agent’s phone number and runs the conversation as a real voice call — this is Direct Inference over the phone. You configure the phone number once (and, optionally, the voice and language), and Galtea uses it to drive voice evaluations against your telephony agent automatically.

​

Use Cases

• Evaluate voice agents — Galtea calls your agent’s phone number directly for each test case, exercising the full telephony stack
• Multi-turn conversation evaluation — For Behavior test cases, Galtea drives a full scripted conversation using the test case’s persona, goal, and scenario, with the conversation simulator generating each user turn.
• Standardize call configuration — Define a reusable phone number, voice, and language for repeatable voice evaluations
• Manage multiple agents — Create separate phone connections for different agents or environments

​

Creating a Phone Connection

To create a Phone Connection:

1. Navigate to your product in the Galtea Dashboard
2. Go to the “Phone Connections” section
3. Click “New Phone Connection”
4. Configure the connection properties as described below

​

Phone Connection Properties

​

Relation to Versions

A Phone Connection becomes the conversation target of a Version: when a version references a phone connection, Galtea dials that number to run each evaluation. A version’s conversation target is mutually exclusive — a version connects to your AI product either through an Endpoint Connection or through a Phone Connection, never both. Choose an endpoint connection when Galtea should call your HTTP API, or a phone connection when Galtea should place a voice call.

​

Relation to Voice Evaluation

Phone Connections power voice evaluation: because Galtea drives a real phone call, the conversation, transcription, and resulting inferences reflect how your agent behaves over the telephony channel. This makes phone connections the entry point for evaluating voice agents end-to-end. Phone connections currently run Behavior test cases (multi-turn: the conversation simulator drives each user turn from the test case’s persona, goal, and scenario) — no additional configuration is required beyond attaching the phone connection to the version. Single-turn Accuracy/Security phone runs (speaking a scripted input line into the call) are planned but not yet available; a version whose phone connection would run non-Behavior tests is rejected. The API automatically transcribes the agent’s audio responses using speech-to-text, so no manual transcript preparation is required. Each recorded agent turn is transcribed before evaluation runs, and the written transcript is what metrics score — your agent’s voice output is evaluated as accurately as any text-based agent. Both sides of every turn are recorded and stored on the InferenceResult for that turn:

• Agent audio (what your agent said): stored as a content-parts envelope on actualOutput; access the envelope via the SDK’s .actual_output_data field and the scored transcript via .actual_output.
• Simulated user audio (what the synthetic caller said): stored as a content-parts envelope on input; access the envelope via the SDK’s .input_data field and the spoken transcript via .input.

This means the full phone conversation — both the synthetic user side and the agent side — can be played back turn by turn in the dashboard’s audio player and read programmatically via the SDK. See InferenceResult for the envelope shapes.

​

Best Practices

​

Related