Skip to main content
The Phone entity represents phone numbers in the Well system. It can be associated with people, companies, and workspaces, and includes verification status, primary designation, and contextual labels.

Table structure

Table name: phones

Main fields

NameTypeRequiredConstraintsAllowed ValuesDescriptionExample
idstring, UUID, πŸ”’ systemβ€”Unique identifier (read-only)β€”Unique ID”phone-uuid-123”
numberstringβœ… YesE.164 formatted numberE.164 format (+33123456789)Phone number”+33123456789”
is_primarybooleanβšͺ Nodefault: true, only valid when in relationship with a Person or Companytrue, falseMarks preferred phonetrue
is_verifiedbooleanβšͺ Nodefault: false, only valid when in relationship with a Person or Companytrue, falseVerification flag for 2FA setuptrue
labelstring (50 char)βšͺ Nomax 50 chars, only valid when in relationship with a Person or Companywork, mobile, home, otherTag for extra context when having multiple phones”mobile”
created_atstring (ISO 8601) πŸ”’ systemβ€”auto timestampβ€”Creation timestamp”2023-01-01T12:00:00Z”
updated_atstring (ISO 8601) πŸ”’ systemβ€”auto timestampβ€”Last update timestamp”2023-01-01T12:00:00Z”
deleted_atstring | null πŸ”’ systemβ€”nullable ISO 8601β€”Deletion timestamp (soft delete)β€œ2024-01-01T12:00:00Z”

Relations

Many-to-Many relations

  • People: Can be associated with multiple people
  • Companies: Can be associated with multiple companies
  • Workspaces: Can be associated with multiple workspaces

Relationship schema

Phone (N) ←→ (N) People
Phone (N) ←→ (N) Companies
Phone (N) ←→ (N) Workspaces

# Direct relationship without intermediate tables
# Each phone can belong to multiple people/companies/workspaces
# Each person/company/workspace can have multiple phones
⌘I