> 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/first-level-support.md).

# First-level support

The use case first-level support is suitable when incoming support requests should be reliably accepted, sorted in advance, and partially answered directly. The agent handles recurring issues, answers standard questions immediately, and forwards more complex cases in a structured way without queues.

### What exactly does the agent handle?

In first-level support, the agent takes calls and clarifies the issue. Common questions, such as about opening hours, prices, or availability, are answered immediately. For more complex topics, it records all relevant information and prioritizes the issue for forwarding. This way, urgent cases reach the right contact person faster. After each conversation, the content is automatically summarized and provided.

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

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

Create an agent and define in the **company profile** (configuration area) which topics your support covers (e.g. "We help with IT problems and billing questions"). *Tip:* Use the greeting to let callers know that they are speaking with a digital assistant (e.g. "I’ll take your ticket or answer quick questions").
{% endstep %}

{% step %}
**Create playbooks for tickets & escalation**

Under Playbooks, create guides for issues that a person must solve.

* **Playbook "Incident report":**
  * Condition: "Caller reports a technical problem"
  * Task: "Record error description"
  * Task: "Ask for customer number & urgency"
  * Closing action: Forward (to 2nd-level support in emergencies) or announce callback (standard ticket).
    {% endstep %}

{% step %}
**Store knowledge**

So that the agent can resolve standard questions ("How do I reset my password?") immediately without disturbing the team:

* **Knowledge base:** Upload manuals, FAQs or instructions as PDF.
* **Customer questions:** Store short answers for quick fixes (e.g. "Where can I find my customer number?").
* **Note:** Avoid redundant or contradictory content in the knowledge base and customer questions. This keeps the agent's response clear and consistent.
  {% endstep %}

{% step %}
**Ticket creation & notification**

Make sure the call becomes a ticket.

* **Email summary:** Enter under *Configuration* → *Recipient* the address of your ticket system (many systems automatically convert emails into tickets).
* **Webhooks (recommended):** Use webhooks to push the incident report directly and in a structured way into tools like Jira, Zendesk, or Freshdesk.
  {% endstep %}

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

To start, you will receive a phone number for 7 days, through which your agent will be immediately reachable. 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 actively under **phone numbers**.
{% endstep %}
{% endstepper %}

### Benefits at a glance

The agent ensures that calls are answered at all times and no request is lost. Support teams are relieved because routine inquiries are processed automatically and only relevant cases are forwarded. At the same time, conversations remain traceable, as all inquiries are documented and can be analyzed. Statistics and call logs make it possible to see which topics occur particularly frequently.


---

# 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/first-level-support.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.
