> 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

### **What is an Outbound Agent?**

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

Typical use cases are

* Appointment scheduling
* Service reminders
* Customer surveys

{% hint style="info" %}
**Note:** Please note the legal and data protection requirements for the use of Outbound Agents.
{% endhint %}

### How an Outbound Agent works

{% stepper %}
{% step %}
Together with the sipgate Solution Consulting team, you set up the agent for your use case: the conversation goal, conversation flow and the required information are defined.
{% endstep %}

{% step %}
After setup, you gain access to the API. Through it, you pass individual call jobs to the agent and can use it to start calls to any phone numbers.
{% endstep %}

{% step %}
The agent calls the target person and conducts the conversation based on the stored specifications.
{% endstep %}
{% endstepper %}

### Create call job

The following information is passed for each call job:

* **Extension:** The ID of the VoIP phone used for billing.
* **Outgoing caller ID:** The number displayed to the other party.
* **Target phone number:** The phone number of the person to be called.
* **Additional information:** Context data that the agent uses in the conversation. For example, name, outstanding amount, or booked product.

### Evaluate results

After a conversation has been completed, the results are available. Transcripts can be found in the settings of the respective agent. In addition, you will receive a summary by email.

{% hint style="info" %}
**Note:** Retry attempts are not carried out automatically. Contacts that are not reached are recorded accordingly and provided to the trigger system. For another call attempt, a new job must be created via the API.
{% endhint %}

### Prices

The use of Outbound Agents is billed by the minute. In addition, connection costs are charged for outgoing calls, 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 in planning, setup and integration into your existing processes. If you would like to use an Outbound Agent, [**please contact our team.**](/documentation/en/plans-and-costs/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sipgate.com/documentation/en/connections-and-integrations/outbound-agents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.