> 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/use-cases/zahlung-and-abrechnung.md).

# Payment & billing

The Payment & Billing Agent is suitable when appointments need to be scheduled, changed, or canceled by phone. Around the clock and without staff needing 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 the issue is an invoice, a payment status, or general payment terms. It answers common questions about payment terms, payment methods, or formal details directly. For individual concerns, it records all relevant information and prepares the handoff to the responsible team. Callers receive clear feedback on how their request will be handled next. After each conversation, the content is documented in a traceable way.

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

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

Create an agent and, in the Configuration section under Company Profile, enter the key data (e.g., IBAN, billing address) in the description so that the agent has it ready when needed.
{% endstep %}

{% step %}
**Create playbook**

Under Playbooks, create separate guides for different concerns. For example, questions about invoices could be handled as follows:

* **Playbook "Question about invoice":**
  * Condition: "Caller asks a question about an invoice"
  * Task: ask for invoice number
  * Task: ask about the concern
  * Closing action: announce a callback
    {% endstep %}

{% step %}
**Store knowledge**

* **Knowledge base:** Upload your terms and conditions, payment terms, or price lists here as a PDF.
* **Customer questions:** Store targeted answers here for outlier questions such as "Can I pay by PayPal?" or "Where should I send the receipt?".
  {% endstep %}

{% step %}
**Enable notifications**

* **Email summary:** Enter an email address under Configuration → "Summary recipients". You will receive all details after the call 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, via which your agent can be reached immediately. After that, port your existing phone number to sipgate or book a free phone number. The free phone number is not automatically in your account; you book it manually under **Phone numbers**.
{% endstep %}
{% endstepper %}

**Benefits at a glance**

The agent handles every payment question and relieves your team of standard inquiries. This leaves more time for complex cases that require real advice. Especially during periods of high inquiry volume (start of month, after invoices are sent, during closings), the service remains reliable. Documentation and analysis make it visible which topics keep coming up and where processes or explanations can be improved before they become recurring pain points.


---

# 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/use-cases/zahlung-and-abrechnung.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.
