# Registration contact

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FksgY5neuOoH3enRqwowc%2Fimage.png?alt=media&#x26;token=838b1f80-ba4e-4e11-a262-2f04ab513f86" alt="Fig. 1: Add Registration contact in backend"><figcaption><p>Fig. 1: Add Registration contact in backend</p></figcaption></figure>

A contact must be defined for registration, as this information is used in many important places, e.g. on **documents** and in **mail footers**, but also as the **sender name** and **address** for system mails.

{% hint style="info" %}
A separate contact can be defined for registration if the contact person differs from the general contact. If it is the same contact person, this contact can be added here again (Fig. 1).
{% endhint %}

* Select the person icon to add a dataset from the person browser as a *registration contact* (Fig. 1).
* If the desired person dataset was found via the search, it can be applied using the blue arrow at the beginning of the line (Fig. 2).

{% hint style="info" %}
If no suitable dataset is available, a new personal dataset can be created using the *Add person* button (Fig. 2) and adopted directly by saving using the *Select* checkbox (Fig. 3).

***

It is also advisable to mark the personal dataset as *not synchronizable* (Fig. 3) so that it is not used for duplicate matching and thus unintentionally changed.
{% endhint %}

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FtGjZrZ9aAsl9uK76czXm%2Fimage.png?alt=media&#x26;token=7d5a0d04-840b-4e05-b03c-7a57734af6a3" alt="Fig. 2:  Add person"><figcaption><p>Fig. 2:  Add person</p></figcaption></figure>

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FfohjK1b3xmcfEnprBRe8%2Fimage.png?alt=media&#x26;token=baca6328-e386-419c-82a9-9ee2add17505" alt="Fig. 3: Properties of the contact dataset"><figcaption><p>Fig. 3: Properties of the contact dataset</p></figcaption></figure>

## Places where the registration contact is used

The *Registration contact* is output wherever the associated replacements (Fig. 4) are used in texts. In Converia standard, this occurs in the following places:

* Booking confirmation and booking confirmation email
* Invoice and invoice mail
* Mail templates for the manual dispatch of info mails from the attendee registration

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FUVuylwghFj7rcpK3rHSQ%2Fimage.png?alt=media&#x26;token=1c7572b8-53c6-47db-a7a6-0cec058a2dba" alt="Fig. 4: Replacements of the registration contact"><figcaption><p>Fig. 4: Replacements of the registration contact</p></figcaption></figure>

## Mail address of the registration contact as sender address for mails from Converia

The email address used in the personal dataset of the *Registration Contact* has several other functions in Converia:

1. The email address is the **sender address** for **all emails from the registration** and **attendee registration management** (note: not to be confused with the sender name. This is usually the [abbreviation of the conference](https://manual.converia.de/en/general/a-new-event-in-converia/central-settings-and-individualization/conference-name-location-and-date)).
2. **A copy** of **all emails sent from Converia as part of the participant registration process** is sent to this address. This means that when new participants register and receive a booking confirmation and invoice via email, the information about these new registrations is also sent to the *registration contact*.

{% hint style="info" %}
The location displayed in the PDF templates refers to the location of the corresponding contact (e.g. Invoice -> Registration contact).
{% endhint %}
