Contacts on a lead — Hauptkontakt and Teilnehmer

A lead is a request — “Mika wants a trial class for his daughter”. The people on it are contacts: records that exist once per organisation and are shared by every request they appear on. Mika enquiring again next year is a second request on the same contact, not a second Mika.

Names, phone numbers and email addresses live on the contact. They are no longer pool fields.

The Kontakte card

Every lead shows a Kontakte card in the Anfrage tab listing the people on the request. Each row can show:

Label	Meaning
Hauptkontakt	The one person the lead displays and addresses. Calls, emails and automations go to them. Exactly one per lead.
Gebucht	This person has a live booking for this lead.

Whether someone is a Teilnehmer — the person the request is about, who would actually train — is set per row but not badged: a parent enquiring for a child is the Hauptkontakt and not a Teilnehmer; the child is a Teilnehmer. An adult enquiring for themselves is both.

Row actions (the ”…” menu):

• Kontakt bearbeiten — name parts, and any number of phone numbers and email addresses (Kontaktweg hinzufügen). One of each kind is marked Als primär markieren — that’s where messages go.
• Zum Hauptkontakt machen
• Als Teilnehmer markieren / Nicht mehr als Teilnehmer
• Mit anderem Kontakt zusammenführen — see Duplicates and merging.
• Von dieser Anfrage entfernen — takes the person off this lead only. The contact itself is never deleted and stays on their other requests.

Kontakt hinzufügen oder verknüpfen adds someone: search for an existing contact first, and only create a new one if they aren’t there.

Editing a contact changes it everywhere

Contacts belong to the organisation. Correcting a phone number on one lead corrects it on every lead that person is on — that’s the point, but it means “fixing” a contact on the wrong lead fixes it everywhere.

Repeat enquiries are recognised

When a form, webhook or integration sends in a person, RocketLead first looks for someone the org already has:

• If an existing contact has the same name and already holds every phone number and email that came in, the new request is attached to that contact.
• If anything new came in — a different email, say — a new contact is created instead. A submission can never add an address to an existing person. Likely pairs show up for review as possible duplicates.
• A child (usually sent without channels) is recognised among the children already on the same parent’s other requests.

The lead header then shows Weitere Anfragen von diesem Kontakt, linking the person’s other requests. Each request stays its own lead with its own lead state.

Where this shows up

• Lead pool: requests of the same person are grouped into one row.
• Calendar, dashboard, print, search: show the lead’s name according to the display setting.
• Booking: the booking assistant asks who the appointment is for.
• Automations: $contact.* is the Hauptkontakt, $subjects.* the Teilnehmer — see Variable placeholders.
• Forms: fields must be mapped to people — see Contact mapping.

Deleting a lead does not delete its contacts.