# Send a Single Call

Place a single call with a chosen pathway, voice, and delivery behavior to verify real-world performance. Read the Send Call guide in Hello Alex documentation.

Canonical HTML: https://docs.helloalex.ai/article/send-a-single-call

Path: [Documentation](/) / [Send Call](/send-call)

## Overview

Send Call is designed for controlled validation first, because a single live call reveals delivery and conversation behavior before you spend credits at scale. By choosing one recipient, one caller ID, and one pathway configuration, you can confirm the experience under real phone conditions and then reuse what works in batch workflows.

## How it works

- The form separates recipient identity, call goal, and runtime settings so each decision is visible before launch. That separation reduces configuration mistakes, because you can validate contact targeting independently from pathway logic.
- Launch Summary acts as a final gate, and that final checkpoint catches mismatches in caller ID, voice, or timing before the call is placed. As a result, Send Call becomes a low-risk preflight step for larger outbound sends.

## Tips

- Good to know: a suppressed destination in Do Not Call is blocked immediately with a clear error, so failed sends often indicate compliance rules rather than telephony outages.

## Recipient

Recipient setup comes first because accurate destination and caller identity determine whether the call can be delivered and trusted.

Confirm destination and caller ID, then move to Call Goal to define conversation behavior.

- You define who receives the call and which outbound number is presented, so carrier routing and recipient recognition are set before conversation logic runs. When caller identity is correct, answer rates and trust generally improve.
- **Destination Number:** The phone number you are calling.
- **Caller ID:** Outbound number shown to the recipient.
- Good to know: if a number exists in Do Not Call, Send Call blocks the attempt to prevent accidental policy violations.

## Call Goal

Call Goal defines intent before execution, so the pathway and voice you choose directly shape what the recipient hears and how Alex responds.

Set core conversation inputs, then open Call Settings for delivery constraints.

- Selecting a pathway or task sets the decision flow, while voice and opening message tune delivery tone. Because this layer controls conversation behavior, validating it here prevents misaligned messaging once calls are live.
- **Pathway / Task:** Defines conversation goal and flow.
- **Opening line:** Optional first line when the callee answers.
- Good to know: testing the same pathway in Chat & Test first helps isolate script issues before telephony variables are introduced.

## Call Settings

Call Settings controls runtime boundaries, which matters because timing, voicemail handling, and delivery hooks affect cost and post-call workflows.

Review your delivery constraints, then continue to Launch Summary for a final check.

- These settings apply operational guardrails such as maximum duration and voicemail behavior before dialing starts. Clear guardrails reduce billing surprises and make downstream automations more predictable.
- **Max Duration:** Cap on call length in minutes.
- **Voicemail:** Detection and message when unanswered.
- Good to know: shorter duration limits are useful during smoke tests so you can validate flow logic without long call exposure.

## Launch Summary

Launch Summary exists to prevent expensive misfires, so it consolidates the effective configuration before the final send action.

Launch the call, inspect the result, and document any adjustments before scaling.

- The summary aggregates recipient, pathway, voice, and timing decisions into one final verification view. Because this is the last pre-dial checkpoint, it is where most preventable mismatches are caught.
- **Launch Time:** Send now for immediate outbound dial.
- Good to know: when this single-call setup performs well, you can reuse the same structure in Batch Call with fewer surprises.

## Next step

Run one internal test call, review the outcome, then promote the same configuration to Batch Call if results are correct.

## Related documentation

- [More Send Call guides](/send-call)