Configure custom contact and opportunity fields in 6am

Outcome and responsibility

A reviewed set of contact and opportunity fields, with the right object, stable key, type, choices and group. The operator needs permission to manage contacts in the selected 6am workspace.

A contact field belongs to a person. An opportunity field belongs to one deal. A person can have several deals with different budgets or interests: do not store deal-specific information on the contact.

Before you start

• Open 6am and confirm the workspace in the company selector.
• Prepare a field plan: object, key, display name, group, type, allowed choices and help text. Reuse native fields such as email, phone and opportunity title rather than creating duplicates.
• Confirm permission to store the proposed information. Avoid passwords, credentials and unnecessary sensitive data in CRM fields.
• Use clearly identified synthetic examples for validation. This procedure does not authorize contacting clients, importing data or starting automations.

01. Review existing definitions

Open Custom fields in the sidebar. Filter by Object, Group or Active and search by name or key. Archived definitions still reserve their keys. Check the existing type and choices before creating another field.

Groups organize fields within the selected object. Enter a consistent group name or reuse a suggested name; there is no separate folder setup screen. Renaming a group on one field moves only that field.

02. Create a contact or opportunity field

1. Click Create field.
2. Select Contact or Opportunity in Object. Choose the owner of the information before saving.
3. Enter a unique Field key for that object. Use lowercase letters, numbers and underscores, starting with a letter; maximum 50 characters. Example: preferred_channel for a contact or budget_range for a deal.
4. Choose Type, enter Field name, Group and optional Help text. Names and groups accept up to 80 characters; help text accepts 250.
5. For Single choice or Multiple choice, enter one option per line in Options. Use up to 30 distinct options, each up to 80 characters. Leave Options empty for other types.
6. Keep Active enabled and save. Check the new row's object, key, type, group and options.

The limit is 50 definitions per object, including archived fields. All values are optional. There is no mandatory-field enforcement on imports, transitions or contact creation in this version.

03. Fill and verify a synthetic record

Open Contacts or Sales opportunities and choose the record's Custom fields action. Fields appear under their groups and only for that record's object. Enter the approved test values and save. Reopen the action and check each value. Leaving an active field blank clears that value; archived values are read-only and remain stored.

For example, give a contact preferred_channel = Email and a deal budget_range = To confirm. Verify that the opportunity value does not appear on the contact or on another opportunity. Use zero, No and a date in the validation set when those types are present.

If another operator changes the values or definitions while your form is open, saving is rejected. Close and reopen it, compare the current data and reapply only the intended changes.

04. Maintain definitions without changing their meaning

Use Edit field to change its name, group, help text or Active state. Object, key, type and choices are immutable after creation. To change one of them, archive the old field and create a new definition with a new key. Do not claim that creating the replacement migrated existing values.

Deactivate Active to archive a field. Its values remain visible in the record action. Reactivate it to edit those values again. Definitions are not permanently deleted through this screen.

When unifying duplicate contacts, compatible custom values are retained. Conflicting values stop the merge before any record is changed. Reconcile both contacts, reactivating an archived field if necessary, then repeat the comparison and confirmation.

Acceptance criteria

• Correct workspace, object, key, label, type, group and choices match the field plan.
• Synthetic values persist after reopening; contact and deal values remain independent.
• Blank, zero and No behave as intended; invalid choices are rejected.
• Archiving preserves values and blocks editing until reactivation.
• Record the verification date, operator, field keys and any limitations before handoff.

Scope and next steps

These fields are stored in the CRM and edited through the record action. Active contact fields can be mapped during CSV import; follow SOPs 082 and 083 for formats, preview and a pilot. Blank CSV cells preserve values, unlike clearing a field in the record action. Opportunity fields are not imported through the contact CSV screen. Fields are not automatically available in smart-list filters, pipeline acceptance rules, AI scoring or email templates. Plan and validate those integrations separately before relying on them.

• SOP 003 — Configure a 6am workspace
• SOP 005 — Configure pipelines and stages
• SOP 082 — Prepare a contact import

Collect through a public form

Forms can explicitly select up to 10 active custom contact fields. Labels, help text and choices become public. Valid answers fill empty values only; existing values, including false and zero, are preserved. Field changes require reviewing and republishing dependent forms. Follow SOP 076 before enabling collection. Opportunity fields, automatic custom-field filtering and scoring are outside this integration.