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

# Appointment management

The appointment management agent is suitable when appointments need to be scheduled, changed, or canceled by phone. Around the clock and without employees having to be permanently available. It captures appointment requests in a structured way and significantly reduces administrative effort.

### **What exactly does the agent handle?**

The agent answers calls and recognizes whether callers want to schedule a new appointment, change an existing one, or cancel it. Depending on the request, it asks targeted follow-up questions about the desired time slot, the type of appointment, or existing information. All relevant details are recorded in a structured way. Callers receive a clear confirmation of what happens next. After each conversation, the information is available in full, as a call log or by email.

### **Briefly explained: How to set up the use case**

{% stepper %}
{% step %}
**Create agent & refine profile**

Create an agent and enter your opening hours and rough availability in the company profile (Configuration section). This allows your agent to respond directly to unsuitable time suggestions (e.g. "Sunday at 3 a.m.").

**Note:** For direct appointment bookings, connect a cal.com calendar. Without calendar integration, use a playbook to collect appointment requests in a structured way.
{% endstep %}

{% step %}
**Create playbooks for appointment requests**

Only create a playbook for appointment requests if no calendar integration is connected. The agent will then record the appointment request, but will not check a live calendar.

* **Playbook "New Appointment":**
  * Condition: "Caller wants to schedule an appointment"
  * Task: "Ask for desired appointment time & alternative"
  * Task: "Note contact details (name, phone number) for confirmation"
  * Closing action: announce a callback
    {% endstep %}

{% step %}
**Enable notification**

* **Email summary:** Enter an email address under Configuration → "Summary recipients". After the call, you will receive all details and call the customer back for confirmation.
* **Webhooks (optional):** Send the data in a structured way to your CRM or a tool like Zapier to create tickets automatically.
  {% endstep %}

{% step %}
**Assign phone number**

To get started, you will receive a phone number for 7 days, through which your agent can be reached immediately. After that, you can port your existing phone number to sipgate or book a free phone number. The free phone number is not automatically available in your account; you actively book it under **Phone numbers**.
{% endstep %}
{% endstepper %}

**Benefits at a glance**

The agent ensures that every appointment request is accepted, regardless of time or workload. Teams are relieved and no longer have to juggle between phone and calendar. Statistics make it possible to see when particularly many appointment requests come in, which issues occur frequently, and where processes can be simplified further.


---

# 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.de/ai-agents/en/use-cases/terminmanagement.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.
