Contacts
Overview
Contacts are the people behind the customers — the individuals you actually talk to. A contact belongs to exactly one customer.
The separation matters: the customer carries what concerns the company — billing address, VAT identification number, payment terms. The contact carries what concerns the person — salutation, position, direct line, language. Looking for those fields on the wrong object is a search that never ends.
Core tasks
Create and maintain contacts. New contact creates a contact person. The detail page holds salutation, email, phone, mobile, position, department, language, the owning customer, role and status.
Search the list. Columns show name with position, customer, email, phone, role and status; filtering is by role and status.
Register additional email addresses. A contact can hold several addresses. This is not a convenience field but the reason incoming mail is still filed correctly when someone writes from a private or an old company address.
Review the history. The Communication tab shows the message history with this person.
Set the language. The Language field governs which language this person is written to in by the software — it belongs to the contact, not to your own interface setting.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Creating and editing a contact
| Field | Required | Values / format | What it does |
|---|---|---|---|
First name firstName | yes | text, max. 255 characters | Part of the name. First and last name together form the display in selection, document and salutation. |
Last name lastName | yes | text, max. 255 characters | The second required part. |
Customer customerUlid | no | an existing customer | Which company the contact belongs to. Without a customer they stand alone — findable, but in no customer record. |
Salutation salutation | no | text, max. 20 characters | Used as the form of address in mails and documents. |
Email email | no | email address, max. 255 characters | The main address. Documents and mails go there, and incoming post is attributed to this person by it. |
Further addresses aliasEmails | no | list of email addresses | Secondary addresses of the same person. Post from them lands in the same record instead of creating a second contact. |
Phone phone | no | text, max. 50 characters | Landline number. |
Mobile mobile | no | text, max. 50 characters | Mobile number; the target for SMS and WhatsApp where set up. |
Position position | no | text, max. 255 characters | The function in the company, e.g. "Head of purchasing". |
Department department | no | text, max. 255 characters | The unit the person belongs to. |
Role role | no | master data "contact roles" | What the person is responsible for on your side (invoicing, technical, purchasing …). Document dispatch picks the right recipient by it. |
Primary contact isPrimary | no | yes/no | Who is proposed when only "the customer" is meant. There is exactly one per customer; the mark moves rather than duplicating. |
Channels channels | no | list of channels | Which ways this person can be reached on. Governs what the history and the dispatch offer. |
Language locale | no | one of the configured languages | Language of address. Empty means the customer's language, otherwise the system language. |
Status statusId | no | master data "contact statuses" | Life state of the contact, e.g. left the company. A departed contact stays on old documents but is no longer proposed. |
Tags tags | no | several terms | Free grouping across role and customer; filterable and usable as an entry into marketing journeys. |
Notes notes | no | multi-line text | Free text on the person. |
Watchers watcherIds | no | list of users | Who may read the contact. A contact has no owner of its own — this permission comes on top of the customer's and replaces no permission. Saving replaces the whole list. |
Brand brandId | no | one of your brands | Assigns the contact to a brand. Empty means assigned to no brand. |
Settings & permissions
- Permission
contact.read. Without it neither the list nor a detail page is reachable; a deep
link redirects back to the dashboard.
contact.createto create,contact.deleteto delete.- Role and status are master data and can be adjusted in the administration area.
- Portal access is separate. A contact is at first only a record. Access to the customer portal
arises solely from an explicit invitation — a distinct action with its own permission, so that nobody is granted access by accident.
FAQ & troubleshooting
I cannot find a contact. Check the role and status filters. If the owning customer belongs to a brand you hold no permission for, the contact will not appear either.
A contact cannot see the customer portal. The record alone is not enough — the person has to have been invited.
Mail from this person is filed under the wrong customer. Then the sender address used is missing from the additional email addresses, or a domain rule on the customer takes precedence.
Position and phone cannot be changed on the customer. Correct — those fields belong to the contact and are maintained here.