The people object stores individual contacts. It is extensible but cannot be deleted.
| Field | Type | Behavior |
|---|---|---|
Name | string | Read-only title composed from First Name and Last Name. |
First Name | string | Editable component of Name. |
Last Name | string | Editable component of Name. |
Email | string (email) | Unique and the primary deduplication key. |
Phone Number | string (phone_number) | Secondary deduplication key. |
Address | string (text) | Postal address. |
Role | string | Job title or role. |
Website | string (url) | Contact website. |
Linkedin | string (url) | LinkedIn profile. |
Location | string | Contact location. |
Language | string | Preferred language. |
Relationship Type | select | Lead, Customer, Churned, Vendor, Partner, Investor, or Other. |
Users | prismaRelation | Assigned Frontline account users. |
Last Interaction | date | Read-only timestamp maintained from recent interactions. |
Company | relation | Single relation to a record in companies. |
Use frontline object schema people to inspect the current account schema, including custom fields and select options.
People are deduplicated by email first and phone number second. Uniqueness applies across the entire object, including all record types.
People created from channels may initially be anonymous. Normal People list and search operations return identified contacts only. A contact is identified when sufficient information such as a name, email, or phone number is available.
When a Person is created or updated with an email on a non-generic business domain, Frontline can:
- Find an existing Company whose
Domainmatches the email domain. - Link the Person to that Company.
- Create and enrich the Company when no match exists.
Generic email domains such as Gmail or Outlook are not auto-linked. Contacts without an email also require a manual Company relation when one is needed.
People can be created automatically from email, WhatsApp, Instagram, Messenger, and agent conversations according to the account's contact creation settings.
Communication activity is attached to the Person timeline. Frontline also maintains profile context such as summaries, memories, relationship insights, and Last Interaction; do not duplicate these with custom fields or parallel activity tables.
frontline object record create people --data '{
"First Name": "Jane",
"Last Name": "Doe",
"Email": "jane@example.com"
}'See Companies for Company-side linking and activity behavior.