> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/operate/contacts.md).

# Contacts

Contacts in Equipme Operate: people, groups and external persons, fields, figures, a contact's tickets and how employees become contacts.

**Path:** Equipme Operate → **"Contacts"** (administrators)

A **contact** is someone tickets are handled for – the requester of a ticket. The list shows "People you handle tickets for".

## Kinds of contacts

| Kind                  | Description                                                                             |
| --------------------- | --------------------------------------------------------------------------------------- |
| **Person**            | An employee of your company with equipme access.                                        |
| **Group**             | Every group is automatically also a contact and can be written to that way.             |
| **"External person"** | Someone without a user account, e.g. a service provider or someone who writes by email. |

## How employees become contacts

You don't have to create employees manually:

* On activation, the option **"Synchronize all employees"** creates a contact for all active employees (see [Equipme Operate at a glance](/dokumentation/operate.md#activating-equipme-operate)).
* Otherwise an employee gets their contact automatically as soon as they create a ticket for the first time or one is created for them.
* If you add an unknown email address as a recipient in a ticket, you can create it as a contact right away ("Add "*address*" as contact").

## The contact list

Fields: **"First name"**, **"Last name"**, **"Email"**, **"Phone"**, **"Mobile"** and **"Company"**. **"Show KPIs"** adds the columns "Open tickets", "Closed tickets" and "Total tickets".

Shortcuts:

* **Ctrl + click** on the email address writes an email.
* **Ctrl + click** on the phone number places a call.
* A row's menu offers **"View profile"**, **"Edit contact"**, **"Write email"**, **"Create new ticket"** and **"Delete contact"**.

Create new contacts with **"Add contact"**.

## Contact details

At the top are figures about the contact's tickets: **"New"**, **"Open"**, **"Closed"** and **"Total"**. Below, the **"Tickets"** area lists their tickets, either **"Open"** or **"All"**. With **"New ticket"** you create a ticket for this contact directly.

In the ticket itself, the contact also gets you further quickly: **"Open contact"**, **"Write to *****name*****"** or **"Call *****name*****"**.

## FAQ

**An employee is missing from the contact list. What should I do?**

They get their contact automatically with their first ticket. You can also create them with "Add contact" or create a ticket for them with "Open ticket for".

**Does an external person need an account?**

No. External persons communicate by email.


---

# 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://hub.equipme.io/dokumentation/operate/contacts.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.