> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Place an outbound call

> Call a phone you control from an assistant, then use the right automation path.

Use an assistant's **Outbound call** control to test a call before adding the assistant to an automated workflow.

## Before you begin

You need permission to manage the assistant, an active assistant in the selected account, and an available outgoing number. The form uses the assistant's assigned number when available; otherwise, choose a number for this call. If you use an imported number, complete the carrier's outgoing route first. Use a destination you control for the test.

## Place a test call

1. Open the assistant.
2. Select **Outbound call**.
3. Enter the destination phone number, including its country code.
4. Review the available calling options and selected source number.
5. Select **Call now**.
6. Answer the destination phone.
7. Confirm the assistant, caller ID, greeting, and one task you expect it to perform.
8. End the call and inspect its call record.

A submitted request can succeed before the phone rings. Confirm the destination actually receives the call and that the conversation works.

## Calling form options

| Field or control | Behavior |
| - | - |
| From | Shows **Assistant default** when the assigned number is available. Otherwise choose an available number from the account for this call; the choice does not change the assistant's saved settings. |
| To | Enter a full number with country code. When contact search is available, search by name, email, or phone (at least two characters; input allows up to 200), then select a matching contact. The contact must have a valid phone number. |
| Call now | Requests a call immediately. The recipient must differ from the source number. |
| Call requested | Confirms the request was accepted and displays To, From when available, and Assistant. Use **View call logs** for connection/outcome or **New call** for a separate request. |

## Choose an automation path

| Your starting point | Use |
| - | - |
| A GoHighLevel contact or workflow | The installed Assistable **Make AI Call** action. Select the assistant and map the destination/contact fields offered by that action version. |
| A custom application | The v3 Calls API. Supply the assistant, destination, and supported source-number or variable fields from the current API reference. |
| A Zapier workflow | The [Zapier guide](/v3/zapier). |
| An assistant responding to a request in chat | [Start a call from chat](/v3/guides/chat/start-requested-call). |

Test the chosen automation with one controlled contact before adding more recipients. Inspect the action's returned result and then confirm the call at the destination. A contact active tag is not a universal requirement for outgoing calls; the direct request selects the assistant explicitly.

## Diagnose a call that does not start

| Result or symptom | Next step |
| - | - |
| Permission or account-access error | Check that you can manage the assistant and that the assistant and source number belong to the selected account. |
| Missing or unavailable source number | Check the assistant's assigned number and its setup status. |
| Funding or billing error | Follow the specific returned error and review the applicable account balance and [billing guide](/v3/billing-guide). |
| DNC or calling DND failure in Make AI Call | Pause retries and investigate [calling screening](/v3/guides/troubleshooting/blocked-calls). |
| Request accepted but no conversation | Check the call record and provider result for the destination. An accepted request is not an answered call. |
| SIP import calls fail | Review the carrier's termination route and authorization separately from the incoming route. |

For API failures, use the [v3 errors reference](/v3/errors). For GHL actions, read the returned error message instead of assuming a legacy error tag is always created.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.