Contacts
A contact is a person — a named human you can attach to the organizations you work with. Contacts live in a shared pool: one contact can be linked to several records, and a record can have several contacts, each with a role.
The three parts
A contact is made of a person record plus two kinds of sub-record:
- Contact — the person: display name, first/last name, title, notes.
- Contact methods — ways to reach them. Each method is an email or a phone number, with an optional label ("Mobile", "Direct") and an optional primary flag.
- Entity links — which records this person belongs to. Each link points at a customer or a vendor, with an optional role ("Billing", "Procurement") and primary flag.
| Field | Meaning |
|---|---|
displayName | Name shown in lists |
firstName, lastName, title | Optional structured detail |
method methodType / value / label / isPrimary | An email or phone entry |
link entityType / entityId / role / isPrimary | An attachment to a customer or vendor |
isActive | Whether the contact is in use |
Relationships
- Linked to customers and vendors through entity links. (Links to locations are reserved for a future release.)
- Contacts are never required by an order — they're a convenience layer for keeping track of who to talk to.
Deleting a contact removes its methods and links along with it.
See also
Manage contacts through the REST API or the MCP server.