> 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/guides/get-started/voice-agent-onboarding.md).

# Voice agent onboarding

This page walks you through getting a Spara Voice agent live — from phone number registration to your first test call. The process is self-service and takes about 15–30 minutes.

For a refresher on how Voice agents work, see [Agents](https://docs.spara.com/build/agents.md) and [Phone](https://docs.spara.com/build/channels/phone.md).

## Overview

A live Voice agent needs three things:

1. **A phone number** — Registered in your organization's settings.
2. **Agent instructions and abilities** — What the agent says and what it can do (book meetings, transfer calls, etc.).
3. **A published version** — Draft changes don't affect live calls until you publish.

{% hint style="info" %}
Unlike Text agents, Voice agents do not require a Twilio A2P registration or carrier approval process. You can go live as soon as your phone number is registered and your agent is configured.
{% endhint %}

## Step 1: Register a phone number

Navigate to **Settings > Voice > Configuration**. This is where your organization manages all phone numbers used by Voice agents, Text agents, and Workflows.

Click **Add phone number** to register a new number. Once registered, the number is available across your account — you'll assign it to a specific agent in a later step.

{% hint style="info" %}
If you plan to run multiple Voice agents (e.g., one for sales and one for support), register a separate phone number for each. Each number can only be assigned to one published Voice agent at a time.
{% endhint %}

{% hint style="warning" %}
**Planning to use this agent for outgoing calls?** Ask your Spara representative to kick off **branded calling onboarding** as soon as you start setting up the agent. Branded calling registers your account with the telephony network so outgoing calls show your business — not "Spam Likely" — on the recipient's phone. It typically takes several days to complete, so start early. See [Phone](https://docs.spara.com/build/channels/phone.md#branded-caller-id-for-outgoing-calls) for details.
{% endhint %}

## Step 2: Create a Voice agent

Navigate to **Voice** in the left sidebar and click **New voice agent**. Give it a name that reflects its purpose — e.g., "Inbound Sales Qualifier" or "Demo Follow-Up."

## Step 3: Write instructions

The **Instructions** tab defines how the agent behaves on calls. Write in natural language, the same way you'd brief a new sales rep.

A good starting prompt covers:

* **Greeting and identification** — How the agent introduces itself and confirms it's speaking with the right person.
* **Qualification questions** — What the agent asks to determine if the lead is a fit.
* **Handling common questions** — How to respond to pricing, product, and competitor questions.
* **Next steps** — What the agent does with qualified leads (book a meeting, transfer to a rep) vs. unqualified leads (thank them, end politely).
* **Boundaries** — What the agent should never do (make up pricing, promise features, etc.).

**Example:**

```
You are a sales assistant for Acme Corp. Your goal is to qualify inbound 
leads and schedule demos with Account Executives.

- Introduce yourself: "Hi, this is Alex from Acme Corp. Thanks for calling!"
- Confirm you're speaking with the right person.
- Ask what prompted their interest and what problem they're trying to solve.
- If they're a good fit (B2B company, 50+ employees, looking for a solution 
  in the next 3 months), offer to schedule a demo using the calendar tool.
- If they're not a fit, thank them politely and end the call.
- Never make up pricing or feature details. Say "I'll make sure our team 
  follows up with that information" if you don't know.
```

See [Writing Effective Agent Prompts](https://docs.spara.com/guides/best-practices/writing-effective-agent-prompts.md) for more best practices.

## Step 4: Add abilities

On the **Abilities** tab, add the tools your agent needs:

* **Calendar** — Let the agent check availability and book meetings by conversation. The agent reads open slots aloud and books when the lead confirms a time. A Calendly integration is automatically created for new voice agents — you can change the provider or customize it here.
* **Transfer** — Route calls to reps or teams. Configure named destinations (e.g., "Sales", "Support", a specific rep) using the dropdown in the transfer tool settings. The agent picks the right destination based on the conversation.
* **API Request** — Call an external API during the conversation — for example, to look up an order or check account status. Configure the URL and parameters ahead of time.

You can add multiple abilities. Most voice agents start with Calendar and Transfer.

## Step 5: Configure voice and call settings

On the **Configuration** tab:

1. **Choose a voice provider and voice.** Spara supports ElevenLabs and Deepgram. Each offers a range of voices — pick one that matches your brand. You can adjust speed, stability, and similarity to fine-tune how it sounds.
2. **Set up a privacy warning** (recommended). Configure a custom call recording disclosure that plays at the start of each call. You can customize the message text and select a specific voice for the disclosure, independent of the agent's main voice. This is important for compliance with call recording consent laws in your jurisdiction.
3. **Configure additional settings:**
   * **Voicemail** — Enable the agent to leave a scripted voicemail when a lead doesn't answer an outgoing call.
   * **Interruption handling** — Control whether the lead can interrupt the agent mid-sentence and how sensitive the detection is.
   * **Re-engagement** — The agent speaks again if the lead goes silent, keeping the conversation moving.
   * **Max call duration** — Set a time limit for calls (defaults to 10 minutes).

## Step 6: Assign a phone number

On the **Configuration** tab, assign one of your registered phone numbers to this agent. This is the number the agent answers incoming calls on and uses as the caller ID for outgoing calls.

All outgoing numbers automatically accept callbacks — if a lead misses your call and dials back, the same agent picks up with the lead's full context.

## Step 7: Test your agent

Spara offers two ways to test before going live:

**Browser test call.** Click **Test** in the agent editor to start a live conversation with your agent directly in the browser. This is the fastest way to iterate on your instructions.

**Outbound test call.** From the voice testing dashboard, send a real outbound call to a phone number you specify. This lets you hear the full experience as a lead would — including caller ID, privacy warning, voicemail, and callback behavior.

Both test modes use the **draft** version of your agent, so you can make changes and re-test without affecting anything live.

**What to listen for:**

* Does the greeting sound natural?
* Does the privacy warning play correctly?
* Does the agent ask the right questions in the right order?
* Can the agent handle pushback or unexpected answers?
* Do abilities work (calendar booking returns real slots, transfers connect)?
* Does the voice sound right at the configured speed and stability?

Test calls are recorded and appear in the agent's call history for review.

## Step 8: Publish

When you're satisfied with testing, click **Publish**. Only the published version handles real incoming and outgoing calls.

Each publish creates a new entry in the agent's **version history**, so you can track what changed and when. If something goes wrong, you can review prior versions to understand what shifted.

## After going live

Once your agent is published and a phone number is assigned, it's live. Here's what to do next:

* **Set up workflows for outgoing calls.** Use the [Call Phone Step](https://docs.spara.com/build/workflows/steps/call-phone.md) step in [Workflows](https://docs.spara.com/build/workflows.md) to have the agent proactively call leads — for example, immediately after a form submission or 30 minutes before a scheduled demo.
* **Monitor call outcomes.** Call results appear on each lead's timeline in [Leads](https://docs.spara.com/pipeline/leads.md) — including whether the call was answered, transferred, or resulted in a booked meeting.
* **Use Ask Spara to debug.** **Ask Spara** opens beside the agent editor and lets you chat with an AI about why your agent behaved a certain way on a specific call. This is the fastest way to diagnose issues.
* **Review recordings.** Listen to real calls to identify where the agent needs prompt improvements. All calls are recorded and transcribed.
* **Iterate on your prompt.** Edit the Instructions tab, re-test, and publish a new version. Version history tracks every change.

## FAQ

**How long does it take to go live?**\
15–30 minutes. There is no carrier registration or approval process for Voice agents — once your phone number is registered and your agent is published, it's live.

**Can I have multiple voice agents on different phone numbers?**\
Yes. Register a separate phone number for each agent in **Settings > Voice > Configuration**, then assign each number to its agent on the Configuration tab.

**What happens if a lead calls back an outgoing number?**\
The same Voice agent that placed the outgoing call automatically answers. The agent has the lead's full context from the original call attempt.

**Do I need to set up a calendar integration manually?**\
Not for Calendly — a Calendly integration is automatically created when you create a new voice agent. If you want to use Cal.com or another provider, you can change it on the Abilities tab.

**Are calls recorded?**\
Yes. All voice calls are recorded and transcribed. Recordings and transcripts are available on the lead's timeline in [Leads](https://docs.spara.com/pipeline/leads.md).

**How do I handle compliance for call recording?**\
Configure a privacy warning on the Configuration tab. This plays a custom disclosure at the start of each call. Consult your legal team for the specific language required in your jurisdiction.


---

# 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/guides/get-started/voice-agent-onboarding.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.
