> For the complete documentation index, see [llms.txt](https://help.sipgate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.com/documentation/en/connections-and-integrations/outbound-agents.md).

# Outbound Agents

With an Outbound Agent, your sipgate AI Agent can actively call people and conduct conversations independently. The agent works on the basis of a defined conversation goal and documents the results after the call is completed.

### What is an Outbound Agent?

With an **Outbound Agent** your sipgate AI Agent can actively call people and conduct conversations independently. The agent works on the basis of a defined conversation goal and uses information provided to it before the call.

**Typical use cases are:**

* Appointment scheduling & reminders
* Service reminders
* Customer surveys

After the conversation, the agent documents the result. The data can then be analyzed or passed on to connected systems and workflows.

{% hint style="info" %}
**Note:** Please note the legal and data protection requirements for using Outbound Agents. If you have any questions, we'll be happy to help.
{% endhint %}

### How does the outbound process work?

An Outbound Agent is part of a larger process. In addition to the actual conversation, preparation and follow-up also need to be planned.

**The process consists of three phases:**

{% stepper %}
{% step %}

### Preparation

Before the call, it is defined who will be called, why the call is taking place, and what information the agent needs.

This data can come, for example, from a CRM system, a lead list, a spreadsheet, or another target system. It can be retrieved directly before the call or collected and prepared in advance.
{% endstep %}

{% step %}

### Conversation

The AI Assistant starts the call and conducts the conversation based on the prepared context. How the agent behaves during the conversation is defined by a [**playbook**](https://help.sipgate.com/documentation/en/behavior/playbooks.md) defined. The playbook consists of individual tasks that define which information the agent asks for or provides and in what order the steps are handled.

Live-call functions can be used during the conversation to provide support via an MCP server. This allows the agent, for example, to query available calendar slots or retrieve or change information from a connected system.
{% endstep %}

{% step %}

### Processing the results

After the conversation, result data can be transferred to a connected system via a webhook and processed there via custom workflows. In addition, summaries can be provided by email.
{% endstep %}
{% endstepper %}

### What information does the agent need?

A call order contains the information the agent needs for the call. This usually includes:

* **Outgoing caller ID**\
  The phone number displayed to the person being called. It also determines where possible callbacks go, for example to a team, a mailbox, or an Inbound Agent. Since the number can be set per call, callbacks can be controlled in a targeted way, for example for urgent matters, special cases, or different responsibilities.\
  Note: If the outgoing caller ID is listed in public directories (e.g. Google Maps), the company name will also be displayed on some devices.
* **Target phone number**\
  The phone number of the person to be called.
* **Additional information**\
  Provide the agent with all information that is important for the call. This includes, for example, name, address, age, last appointment, outstanding amount, booked product, desired appointment time, or previous communication.

In addition, a work instruction can be stored. It describes the goal of the call and what the agent should pay attention to during the conversation, for example whether it should be brief or give particular consideration to certain points.

### How is a call triggered?

A call can be triggered in different ways. Together with our Solution Consulting team, we plan a suitable interface for this, tailored to your use case and your existing systems.

**Possible triggers include, for example:**

* time-based calls, for example for reminders or follow-ups
* triggers via secure HTTP endpoints
* direct triggering from a CRM system

### What happens after the call?

Once a conversation has been completed, the results are available. Transcripts can be found in the settings of the respective agent. In addition, summaries or result data can be passed on by email, webhook, MCP server, or into a connected target system.

**Plan in advance how different conversation outcomes are handled:**

* Conversation successfully completed
* Mailbox reached
* Call answered, but use not desired
* Call declined, busy, or phone number unreachable
* Callback to the displayed phone number

Depending on the use case, a CRM status can then be updated, a follow-up task created, a summary sent, or a new call order prepared, for example.

{% hint style="info" %}
**Note:** The Outbound Agent handles the actual call and conducts the conversation based on the defined process. How mailboxes, unsuccessful calls, or retry attempts are handled is mapped in the connected workflow. Our Solution Consultants develop this workflow together with you in the first proof of concept and then hand it over for ongoing operation.
{% endhint %}

### Questions before setup

Before the Outbound Agent is set up, the following points should be defined:

* Which system does the data for the call come from?
* When and by what is a call triggered?
* What information does the agent need during the conversation?
* Which phone number is displayed?
* What happens in the event of a callback?
* How are the conversation results processed further?

### Setup

Outbound Agents are currently set up together with our AI Consultants. The conversation goal, conversation flow, required information, call initiation and follow-up are defined.

Our experts support you with conception, setup, and integration into your existing processes.

You can view the current configuration of your Outbound Agent at any time in the app web:

<figure><img src="https://1551117702-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXgAkjs11I2pdU4JZqXDl%2Fuploads%2F4864A2llsXSWLpMdEztV%2Fapp.sipgate.com_frontdesks_19813ae8-1923-4a5b-aad4-2b6bf88fb464_outbound.png?alt=media&amp;token=a8ad8e4a-1804-4bb8-89a7-9a4d62d3093d" alt=""><figcaption></figcaption></figure>

### Prices

The use of Outbound Agents is billed by the minute. In addition, outbound calls incur connection charges, which depend on the respective call destination. Further information can be found in the [**current price list.**](https://cdn.prod.website-files.com/678900e941dcd8f65b4519f8/690890314e9ffd30f11ad0c7_eb38f3194fb645a39308cfef5e1834ca_121124_sipgate_Preisliste_PSP.pdf)

### Interested in Outbound Agents?

Outbound Agents are currently set up together with our AI Consultants. Our experts support you with conception, setup, and integration into your existing processes. If you would like to use an Outbound Agent, please [**contact our team.**](https://help.sipgate.com/documentation/en/plans-and-pricing/enterprise-tarif-leistungen-und-einfuhrungsprozess.md)


---

# 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://help.sipgate.com/documentation/en/connections-and-integrations/outbound-agents.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.
