System Fields & Custom Fields
Quantixone provides two types of fields on Contact and Company records: System Fields (built-in platform fields) and Custom Fields (fields you create for your business). Understanding the difference helps you organize data effectively.
System Fields
What Are System Fields?
System Fields are built-in fields provided by Quantixone. They can't be renamed or deleted, and they form the foundation of every contact and company record.
You can browse them under Contacts > Settings, on the System Fields toggle — this view is read-only (searchable, but no add/edit/delete).
Contact System Fields Include
- Identity — First Name, Last Name, Full Name, Middle Name, Suffix, Salutation, Pronouns, Gender
- Communication — Email, Phone, WhatsApp Number, Preferred Language, Preferred Contact Method
- Location — Address, City, State, Postal Code, Country, Timezone
- Professional — Title, Headline, Seniority, Departments, Sub-departments, Functions, Skills, Years of Experience, Education, Certifications
- Social — LinkedIn (URL, Followers, Summary), Twitter/X, Instagram, GitHub, YouTube, TikTok, Skype, Website, Photo URL
- Sales & Lifecycle — Source, Lead Score, Lead Score Category, Lead Status, Lead Quality, Lifecycle Stage, Buying Stage, Budget Range, Deal Size Range, Decision Timeline, Annual Income
- Status — DND Status, DND Date, Email Status, Enrichment Status, Enriched At, Valid Email Date
- Record Metadata — Created At/By, Updated At/By, Last Activity, Last Contacted At, Next Follow-up At, Auto Tag Last Run, Imported File Name
Company System Fields Include
Company Name, Description, Email, Phone, Address, City, State, Country, Postal Code, Website, LinkedIn, Twitter/X, Facebook, Instagram, YouTube, plus Created/Updated At/By.
System Field Characteristics
| Aspect | Details |
|---|---|
| Modification | Cannot be renamed or deleted |
| Scope | Same set for every organization |
| Access | Available to all users in your organization |
| Data Type | Predetermined per field |
Custom Fields
What Are Custom Fields?
Custom Fields are additional fields you create to capture information unique to your business — for Contacts, Companies, or Calendar records.
When to Create a Custom Field
Create a custom field when you need to capture information that:
- Is specific to your industry or process (GST number, account tier, competitor flag)
- Isn't already covered by a system field
- You want to make required, filterable, or shown on the create form
Field Types Available
| Type | Best for |
|---|---|
| Single Line | Short text — with a Text Format sub-type: Text, Number, Percentage, Currency, Email, URL, or Phone |
| Multi Line | Longer free text (notes, bios) — same Text Format sub-types |
| Text Box List | A list of short entries |
| Dropdown (Single) | One choice from a list |
| Dropdown (Multi) | Multiple choices from a list |
| Radio Buttons | One choice, shown as radio buttons |
| Checkbox | Yes/No, or pick-any-of-several in Multiple mode |
| Date Picker | A date, optionally with time |
See Settings & Custom Fields for the full configuration options per type, and the step-by-step walkthrough for creating one.
Using Custom Fields
In Contact/Company Creation: Custom fields with Show in ... Form enabled appear on the create/edit form.
In Bulk Import: Custom fields are matched against your CSV/Excel column headers during the AI-assisted mapping step — you can also create a brand-new custom field on the fly if a column doesn't match anything existing. See Importing Contacts.
In Filtering: Filter contacts or companies by any custom field's value in the filter builder — see Search & Filters.
System Fields vs Custom Fields: Quick Comparison
| Factor | System Fields | Custom Fields |
|---|---|---|
| Who creates it? | Quantixone | Your organization |
| Can it be modified? | No | Yes |
| Can it be deleted? | No | Yes |
| Available to all orgs? | Yes | No — specific to your org |
| Naming | Predefined | You decide |
| Purpose | Core contact/company data | Business-specific data |
Best Practices
- Name Clearly — Use descriptive, self-explanatory field names.
- Use Dropdowns for Fixed Options — Prevents inconsistent free-text values.
- Keep It Lean — Don't create fields you won't actually use.
- Check for System Field Conflicts — The field-name check will warn you if a name conflicts with an existing system field.
- Regular Review — Remove unused custom fields; deleting one removes its data from every record permanently.