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

# First-level support

The use case First-Level Support is suitable when incoming support requests should be reliably accepted, pre-sorted, and partially answered directly. The agent handles recurring issues, answers standard questions immediately, and forwards more complex cases in a structured way, without waiting on hold.

### What exactly does the agent handle?

In First-Level Support, the agent answers calls and clarifies the issue. He answers common questions, such as about opening hours, prices, or availability, immediately. For more complex topics, he records all relevant information and prioritizes the request for handoff. This way, urgent cases reach the right contact person faster. After each call, 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 section) which topics your support covers (e.g. "We help with IT problems and billing questions"). *Tip:* Use the greeting to let callers know they're speaking with a digital assistant (e.g. "I’ll take your ticket or answer quick questions").
{% endstep %}

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

Create guides under Playbooks for issues that a human needs to solve.

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

{% step %}
**Store knowledge**

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

* **Knowledge base:** Upload manuals, FAQs, or guides as PDFs.
* **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 answer clear and consistent.
  {% endstep %}

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

Make sure the call becomes a ticket.

* **Email summary:** Enter under *Configuration* → *Recipients* the address of your ticketing 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 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 ensures that calls are answered at any time and no request is lost. Support teams are relieved because routine inquiries are handled automatically and only relevant cases are forwarded. At the same time, conversations remain traceable, as all requests are documented and can be evaluated. Statistics and call logs make it possible to see which topics occur particularly often.


---

# 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/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.
