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

# Outbound Calls

> Have your AI agents place calls — appointment confirmations, follow-ups, and notifications

Your Telzino agents don't just answer calls — they can make them. An outbound call uses the agent's full configuration (voice, personality, tools, integrations), plus optional per-call context that tells it exactly who it's calling and why.

## Common uses

* **Appointment confirmations and reminders** — "You're calling John to confirm his 2pm appointment tomorrow"
* **Follow-ups** — post-service check-ins, quote follow-ups, review requests
* **Notifications** — order ready, prescription ready, schedule changes

## Placing a call from the dashboard

1. Go to **Reports → Outbound Calls** in the dashboard.
2. Click **Place call**.
3. Choose the agent, enter the phone number (e.g. `+18135551234`), and optionally add a greeting (the exact opening line) and call context — instructions for this one call, like *"You're calling Sarah to let her know her order is ready for pickup."*
4. Click **Place call**. The call appears in the table and updates live as it rings, connects, and completes — with duration and a transcript link when it's done.

## How the greeting works

When the callee answers, the agent speaks the first of these that's set:

1. **Per-call greeting** — the greeting entered in the dialog (or the `greeting` API field), spoken word for word.
2. **The agent's Outbound Greeting** — set once in the agent's settings, used for all its outbound calls.
3. **Auto-generated opener** — if you provided call context, the agent composes a natural introduction from it: *"Hi, this is Ava from Acme calling to confirm your appointment tomorrow at 2pm."*
4. The agent's regular (inbound) greeting, as a last resort.

For most calls, providing good call context and letting the agent generate the opener works best — it always matches the reason for the call.

## Placing calls via the API

For automated workflows (CRMs, schedulers, campaign tools), trigger calls with one API request and receive results on your webhook:

```bash theme={null}
curl -X POST "https://api.telzino.com/v1/agents/{agentId}/outbound-calls" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "to_number": "+18135551234",
    "call_context": "You are calling John to confirm his appointment tomorrow at 2pm.",
    "metadata": { "crm_id": "123" },
    "greeting": "Hi, this is Ava calling from Acme Corp about your appointment.",
    "callback_url": "https://your-system.com/telzino/call-result"
  }'
```

When the call ends, your `callback_url` receives the outcome — status, duration, an AI-generated summary, and your `metadata` echoed back so you can match it to your records. See the [Outbound Calls API](/api-reference/outbound-calls/overview) for the full reference, lifecycle, and webhook payload.

## Tips for great outbound agents

<Tip>
  **Set an Outbound Greeting on agents that make calls.** It guarantees a consistent, on-brand opener like *"Hi, this is Ava calling from Acme Corp."* even for calls placed without context — and the per-call greeting or auto-generated opener still takes over when you provide one.
</Tip>

<Tip>
  **Put the purpose in `call_context`, not the agent prompt.** One well-configured agent can handle confirmations, reminders, and follow-ups — the per-call context tells it which job this particular call is.
</Tip>

<Tip>
  **Plan for voicemail.** If voicemail picks up, the call counts as answered and the agent will speak to the recording. Keep greetings self-contained ("…calling to confirm your appointment tomorrow at 2pm — call us back at…") so even a voicemail drop delivers the message.
</Tip>

## What happens after the call

Outbound calls get the same post-call treatment as inbound: the transcript and AI summary are saved to your call logs, after-call webhooks run, and recordings are kept if enabled on the agent. The outbound call record additionally tracks the dial outcome (`completed`, `no_answer`, `busy`, `failed`) and delivers it to your result webhook.