> 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/cloud-telefonanlage/en/using-sipgate/ereignisliste/was-ist-die-ereignisliste-bei-sipgate.md).
# What is the event list in sipgate?
The sipgate event list clearly displays all calls, faxes, and voicemails – functions and usage at a glance.
{% tabs %}
{% tab title="Classic" %}
**The event list**
The event list is like an email inbox for all your telephony. You always have a complete overview of **incoming and outgoing calls, faxes and SMS**. In addition, you can **voicemail messages** be listened to directly, individual events be annotated with notes, and much more.
**Inbox and archive**
You can always find new events in the **Inbox**. From there, you can move events to the archive if you no longer need them at the moment but do not want to delete them yet. Conversely, events can be moved from the archive back into the inbox of your event list.
**Export events**
You can save your events at any time as **CSV file** by clicking the **Export list*****.***
**Read and unread events**
You can recognize new events by the fact that they are displayed with a **blue background** and **bold text** are displayed. As soon as you click an event and thus open its **detail information** it is marked as read. Read events are displayed with a light gray background and normal text.
**entries per page**
For better clarity, your events are organized across successive pages. Events in your list always appear **chronologically** — that means new events always appear at the very top of page 1. At the bottom of your event list, you can navigate between the different pages and set how many events per page you want to see.
**Mark events as favorite**
Next to each event there is a **star**. Click it to mark an event as a favorite so you can find it again more quickly later.
**Events in a group**
If you have created one or more groups, those groups also have their own event list. This is shared with all group members. Here you have the option to add notes to individual events, e.g. completed call-backs for missed calls, which are visible to all members of the group.
**The event list - saving call data**
For data protection reasons, all events that appear in your event list are, by default, **after 30 days** automatically deleted. This also applies to the events you have archived. However, you can set these events to be either **immediately** or **after 30 days** deleted, or **stored permanently** be.
You can find the options in the web app on the left under **Phone system ➔ Customization**.
**Select and edit multiple events at once**
Through the **checkboxes** on the right, you have the option to select multiple events, such as missed calls or faxes, to edit them. If you enable the checkbox\
**Select all** you select all events on the currently displayed page. As soon as you have selected one or more events, you receive a **selection of editing options**.
➔ **Archive**: Move all selected events from the inbox to the archive.
➔ **Unarchive**: Move all selected events from the archive to the inbox.
➔ **Delete**: Permanently delete all selected events.
**Filter events**
To find specific events again more quickly, you can filter your event list by various criteria. Simply click the corresponding button for the filter you want:
**➔ Marking***:* Filter your events by Read / Unread / Marked or Unmarked.
**➔ Direction:** Filter your events by Incoming / Outgoing.
**➔ Type:** Filter your events by Call / Fax / SMS / Voicemail.
**➔ Status:** Filter your events by Answered / Missed
**➔ Phone number**: Filter your events by specific phone numbers. Partial search (e.g. only the area code) is not possible. Recommendation: export the event list as CSV, then filter in the CSV
**➔ Extension**: Filter your events by lines / groups that your users have access to.
**➔ Labels**: Filter your events by labels you created yourself.
**➔ Time period**: Filter your events by a specific time period.
{% endtab %}
{% tab title="Neo PBX" %}
In the new sipgate Neo-PBX platform, transcription is part of the respective call event, so its retention period depends on the setting for event retention in your account. The admin of an account can choose between three options there: do not store at all, 30 days (default setting), or store permanently. The setting is made in the logged-in area under **Account management ➔ Customization ➔ Events.**
With the default setting, the transcription is automatically deleted after 30 days. Regardless of this, the audio tracks of the conversation are completely deleted immediately after the transcription is completed and are neither stored with the LLM provider used nor used for training purposes.
{% endtab %}
{% endtabs %}
---
# 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.de/cloud-telefonanlage/en/using-sipgate/ereignisliste/was-ist-die-ereignisliste-bei-sipgate.md?ask=&goal=
```
`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.