> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/build/workflows/steps/call-phone.md).

# Call Phone Step

Have a Voice agent call a lead's phone number.

The **Call Phone** step initiates an outgoing call to a lead's phone number using one of your Voice agents.

<figure><img src="https://4072969777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FreCGkFdsmuPJzGP9ZgGA%2Fuploads%2Fgit-blob-88e9e6077517a19561bd1ab9fd083e28ce2339cb%2FWorkflow%20Call%20Phone%20Step.png?alt=media" alt=""><figcaption><p>The Call Phone step configuration panel.</p></figcaption></figure>

## Configuration

Choose the outgoing number on the workflow's **Settings** tab, under **Voice Agent**. Each option is one of your phone numbers with the Voice agent published on it. The lead sees this number on their caller ID, and the Voice agent published on it places the call.

The agent's persona, instructions, and tools are managed on the Voice agent itself, not here. A summary of the agent is shown in the step panel for reference.

If more than one Voice agent is published on the number, they are an A/B test, and the number's traffic split decides which agent calls each lead. The split applies to incoming calls and outgoing workflow calls alike, so an agent set to 0% never places a call. See [A/B Testing](https://docs.spara.com/build/channels/configuring/a-b-testing.md) to adjust the split.

## Tips

{% hint style="info" %}
**Best practice: pair with a Wait step.** Place a **Wait** step before **Call Phone** to give the lead time to complete an action before calling. For example: wait 30 minutes after a form submission before calling.
{% endhint %}

{% hint style="warning" %}
**Missing phone number.** If a lead has no phone number on record, this step is skipped and the workflow continues to the next step.
{% endhint %}

{% hint style="warning" %}
**Do Not Call.** If the lead has opted out of calls, this step is skipped and the workflow continues to the next step. See [Phone](https://docs.spara.com/build/channels/phone.md#do-not-call).
{% endhint %}

{% hint style="warning" %}
**Outgoing calls only.** Workflows initiate outgoing calls. Incoming call handling is configured directly on the Voice agent, not in workflows.
{% endhint %}

{% hint style="info" %}
**Outgoing time windows.** Calls only fire inside your outgoing call window (Settings > Phone Numbers > Outgoing Times), which by default is read in the lead's own local time. Leads that reach this step outside the window are held — not dropped — and the step retries automatically once the window reopens. To use a different window for this step alone, choose **Send during custom times for this step** under Outgoing times in the step panel.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spara.com/build/workflows/steps/call-phone.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
