> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getenso.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact Groups

> Understand how contact information is managed and resolved for invoices and other communications.

## Overview

A **contact group** is a reusable contact record — a label, an email address (plus CC/BCC), and a phone number — that can be attached to a **customer**, **entity**, **contract**, or **invoice**. It replaces entering contact details directly on an entity: contact information now lives in its own record, so the same contact can be reused across multiple records, and each record can have a different contact depending on what the communication is for.

***

## Contact Group Fields

* **Label:** A display name for the contact, e.g. "Billing team" or "Accounts payable".
* **Purpose:** Which kind of document this contact is used for — **Invoice**, **Credit note**, **Dunning**, or **All** (a generic contact used for anything that doesn't have a more specific match).
* **Email / CC / BCC:** The address(es) this contact is reached at.
* **Phone number:** A contact phone number.

***

## Attaching a Contact Group

A contact group can be attached to any one of:

* A **customer**
* An **entity** (including your own organisation's entities)
* A **contract**
* An **invoice**

Only one contact group is allowed per record + purpose combination — for example, a contract can have one "Invoice" contact and a separate "Credit note" contact, but not two different "Invoice" contacts at once.

***

## How a Contact Resolves

When Enso needs a contact for a document — for example, deciding who an invoice email should go to — it looks for the most specific match first, then falls back up the hierarchy:

1. **Invoice** — is there a contact attached directly to this invoice, for this document type?
2. **Contract** — if not, is there one attached to the invoice's contract?
3. **Entity** — if not, is there one attached to the purchasing entity?
4. **Customer** — if not, is there one attached to the customer?

At each level, an exact match for the document type (Invoice / Credit note / Dunning) is tried first; if there isn't one, a generic **All** contact at that same level is used instead. The walk stops at the first match found anywhere in the chain.

Organisation (Seller) entities work a little differently: since there's no invoice/contract hierarchy above your own entity, they only ever use a single **All** contact.

***

## Managing Contact Groups

* **Settings > Contacts** lists every contact group across your organisation, regardless of what it's attached to.
* A **Contact groups** section on a customer, entity, or contract's own page shows just that record's contacts, with options to add, edit, duplicate, or link an existing contact.