---
schema_version: "1"
id: 470a7066125828c3117b1c5a913ffaf0b38da77b1e7d38d9f9755854d8307bc8
title: Contact
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/object_reference/sforce_api_objects_contact.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contact.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: acef1cb9643dc21b7340b4246158a9710e4843f3820ebb0bbc56aa348b8cde40
description: Represents a contact, which is a person associated with an account.
---
# Contact

Represents a contact, which is a person associated with an account.

![Important](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note_important.png)

#### Important

Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.

## Supported Calls

create(), delete(), describeLayout(), describeSObjects(), getDeleted(), getUpdated(), merge(), query(), retrieve(), search(), undelete(), update(), upsert()

## Special Access Rules

Customer Portal users can access only portal-enabled contacts.

## Fields

<table class="featureTable sort_table" summary="">


          <thead class="thead sorted" align="left">
            <tr>
              <th class="featureTableHeader  " id="d438570e120">Field</th>

              <th class="featureTableHeader  " id="d438570e123">Details</th>

            </tr>

          </thead>

          <tbody class="tbody">
            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">AccountId</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">ID of the account that’s the parent of this contact.
                    <p class="p"><span class="ph" id="TransferPortalAccounts"><a name="TransferPortalAccounts"><!-- --></a>We recommend
                        that you update up to 50 contacts simultaneously
                        when changing the accounts on contacts enabled for
                        a Customer Portal or partner portal. We also
                        recommend that you make this update after business
                        hours.</span></p>
                  </dd>

                  <dd class="dd">This is a relationship field.</dd>



                  <dt class="dt dlterm">Relationship Name</dt>

                  <dd class="dd">Account</dd>



                  <dt class="dt dlterm">Relationship Type</dt>

                  <dd class="dd">Lookup</dd>



                  <dt class="dt dlterm">Refers To</dt>

                  <dd class="dd">Account</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ActionCadenceAssigneeId</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The ID of the sales rep designated to work the lead
                    through their assigned cadence. This field is available
                    in API version 48.0 and later when the Sales Engagement
                    license is enabled. To see this field, the user also
                    needs the Sales Engagement User or Sales Engagement
                    Quick Cadence Creator user permission set.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ActionCadenceId</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The ID of the lead’s assigned cadence. This field is
                    available in API version 48.0 and later when the Sales
                    Engagement license is enabled. To see this field, the
                    user also needs the Sales Engagement User or Sales
                    Engagement Quick Cadence Creator user permission
                    set.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ActionCadenceState</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Restricted picklist, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The state of the current action cadence tracker. This
                    field is available in API version 50.0 and later when
                    the Sales Engagement license is enabled. To see this
                    field, the user also needs the Sales Engagement User or
                    Sales Engagement Quick Cadence Creator user permission
                    set.</dd>

                  <dd class="dd">Possible values are: <ul class="ul bulletList">
                      <li class="li"><samp class="codeph nolang">Complete</samp></li>

                      <li class="li"><samp class="codeph nolang">Error</samp></li>

                      <li class="li"><samp class="codeph nolang">Initializing</samp></li>

                      <li class="li"><samp class="codeph nolang">Paused</samp></li>

                      <li class="li"><samp class="codeph nolang">Processing</samp></li>

                      <li class="li"><samp class="codeph nolang">Running</samp></li>

                    </ul>

                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ActiveTrackerCount</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">int</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The number of cadences that are actively running on this
                    contact. This field is available in API version 57.0 and
                    later when the Sales Engagement license is enabled. To
                    see this field, the user also needs the Sales Engagement
                    User or Sales Engagement Quick Cadence Creator user
                    permission set.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ActivityMetricId</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">When Einstein Activity Capture with Activity Metrics is
                    enabled, the ID of the related activity metric.</dd>

                  <dd class="dd">This field is a relationship field.</dd>

                  <dd class="dd">This field is available in API version 41.0 and
                    later.</dd>



                  <dt class="dt dlterm">Relationship Name</dt>

                  <dd class="dd">ActivityMetric</dd>



                  <dt class="dt dlterm">Refers To</dt>

                  <dd class="dd">ActivityMetric</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ActivityMetricRollupId</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <a name="dl_z15_wyp_tcc"><!-- --></a>
                <dl class="dl detailList" id="dl_z15_wyp_tcc">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">When Einstein Activity Capture with Activity Metrics is
                    enabled, the ID of the related activity metric
                    rollup.</dd>

                  <dd class="dd">This field is a relationship field.</dd>

                  <dd class="dd">This field is available in API version 41.0 and
                    later.</dd>



                  <dt class="dt dlterm">Relationship Name</dt>

                  <dd class="dd">ActivityMetricRollup</dd>



                  <dt class="dt dlterm">Refers To</dt>

                  <dd class="dd">ActivityMetricRollup</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">AssistantName</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd"> Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The assistant’s name.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">AssistantPhone</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">phone</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The assistant’s phone number. Label is <strong class="ph b">Asst.
                      Phone</strong>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname" id="field_Birthdate"><a name="field_Birthdate"><!-- --></a>Birthdate</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">date</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s birthdate.<div class="p">Filter criteria for report
                      filters, list view filters, and SOQL queries ignore
                      the year portion of the
                      <span class="keyword parmname">Birthdate</span> field. For example,
                      this SOQL query returns contacts with birthdays
                      later in the year than
                      today:<div class="codeSection soql">
                        <pre class="codeblock soql">SELECT Name, Birthdate
FROM Contact
WHERE Birthdate &gt; TODAY</pre>
                      </div>
                    </div>
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">BuyerAttributes</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">multipicklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Nillable, Restricted picklist,
                    Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">If Automatic Contact Enhancements or Buyer Relationship
                    Map is enabled, this field contains the role of the
                    contact in the opportunity or account. Possible values
                    are: <ul class="ul bulletList">
                      <li class="li">
                        <samp class="codeph nolang">BusinessUser</samp>—For example, an end
                        user. Key value.
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">Buyer</samp>—Key value
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">Champion</samp>—Key value
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">DecisionMaker</samp>—Shown in green on a
                        contact in the buyer relationship map UI. Key
                        value.
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">Detractor</samp>—Shown in red on a
                        contact in the buyer relationship map UI. Key
                        value.
                      </li>

                      <li class="li"><samp class="codeph nolang">Evaluator</samp></li>

                      <li class="li">
                        <samp class="codeph nolang">ExecutiveSponsor</samp>—Key value
                      </li>

                      <li class="li"><samp class="codeph nolang">TechnicalExpert</samp></li>

                    </ul>
                    Key values represent key contacts on an opportunity
                    or account. If a buyer relationship map doesn’t have
                    contacts with key values, then Salesforce prompts you to
                    add them. Having all key values represented on the map
                    provides a full view of the deal or account, increasing
                    sales success.<div class="box message warn">
                      <div class="inner">
                        <div class="bd">
                          <div class="media">
                            <img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note_warning.png" alt="Warning">
                            <div class="mediaBd">
                              <h4 class="mbs">Warning</h4>
                              <p>To ensure that the
                                buyer relationship map feature works as expected,
                                don't modify field values. For example, if you
                                change <samp class="codeph nolang">Detractor</samp> to <samp class="codeph nolang">Detract</samp>, the value isn’t shown in red in
                                a buyer relationship map.</p>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                    This field is
                    available with all profiles except custom and
                    minimum-access. To provide access, use field-level
                    security in Object Manager.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">CanAllowPortalSelfReg</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">boolean</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Defaulted on create, Filter, Group, Sort,
                    Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Indicates whether this contact can self-register for
                    your Customer Portal (<samp class="codeph java">true</samp>) or not (<samp class="codeph java">false</samp>).</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname" id="DataDotComCleanStatus"><a name="DataDotComCleanStatus"><!-- --></a>CleanStatus</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Restricted picklist,
                    Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">
                    <span class="ph" id="DDCCleanDef"><a name="DDCCleanDef"><!-- --></a>Indicates the record’s clean
                      status as compared with Data.com. Values include:
                      <samp class="ph systemoutput">Matched</samp>,
                      <samp class="ph systemoutput">Different</samp>,
                      <samp class="ph systemoutput">Acknowledged</samp>,
                      <samp class="ph systemoutput">NotFound</samp>,
                      <samp class="ph systemoutput">Inactive</samp>,
                      <samp class="ph systemoutput">Pending</samp>,<samp class="ph systemoutput">
                        SelectMatch</samp>, or
                      <samp class="ph systemoutput">Skipped</samp></span>.<p class="p">Several
                      values for <span class="keyword parmname">CleanStatus</span> appear
                      with different labels on the contact record.</p>
                    <ul class="ul bulletList">
                      <li class="li">
                        <samp class="ph systemoutput">Matched</samp> appears as
                        <samp class="ph systemoutput">In Sync</samp>
                      </li>

                      <li class="li">
                        <samp class="ph systemoutput">Acknowledged</samp>
                        appears as
                        <samp class="ph systemoutput">Reviewed</samp>
                      </li>

                      <li class="li">
                        <samp class="ph systemoutput">Pending</samp> appears as
                        <samp class="ph systemoutput">Not Compared</samp>
                      </li>

                    </ul>
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">CommerceCustomerReference</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The external Commerce ID of the individual. To update or
                    create field values, you need the Manage Shopper Profile
                    Sync System Fields user permission. Available in API
                    version 67.0 and later.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">CommerceGroupReference</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The external name of the Commerce customer group. To
                    update or create field values, you need the Manage
                    Shopper Profile Sync System Fields user permission.
                    Available in API version 67.0 and later.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">CommerceOrganizationReference</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The external organization ID of the Commerce instance.
                    To update or create field values, you need the Manage
                    Shopper Profile Sync System Fields user permission.
                    Available in API version 67.0 and later.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ConnectionReceivedId</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">ID of the PartnerNetworkConnection that shared this
                    record with your organization. This field is available
                    if you enabled Salesforce to Salesforce.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ConnectionSentId</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">ID of the PartnerNetworkConnection that you shared this
                    record with. This field is available if you enabled
                    Salesforce to Salesforce. This field is supported using
                    API versions earlier than 15.0. In all other API
                    versions, this field’s value is null. You can use the
                    new PartnerNetworkRecordConnection object to forward
                    records to connections.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ContactSource</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Restricted picklist,
                    Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">If Automatic Contact Creation is enabled, this field indicates whether the contact was
                    created automatically and identifies the source.
                    Possible values are: <ul class="ul bulletList">
                      <li class="li"><samp class="codeph nolang">Auto
                          Create</samp></li>

                      <li class="li"><samp class="codeph nolang">Email
                          Message</samp></li>

                      <li class="li"><samp class="codeph nolang">Meeting
                          Digest</samp></li>

                      <li class="li"><samp class="codeph nolang">Seller
                          Home</samp></li>

                    </ul>
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Department</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s department. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">DepartmentGroup</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Restricted picklist,
                    Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">If Automatic Contact Enhancements or Buyer Relationship
                    Map is enabled, this field contains the business unit,
                    function, or department that the contact belongs to in
                    the organization. Possible values are: <ul class="ul bulletList">
                      <li class="li">
                        <samp class="codeph nolang">chiefExecutive</samp>—Key value
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">customerSuccess</samp>—For example,
                        wealth management, consumer banking, subject
                        matter experts, or healthcare research
                        experts.
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">finance</samp>—Includes pricing and
                        procurement. Key value.
                      </li>

                      <li class="li"><samp class="codeph nolang">humanResources</samp></li>

                      <li class="li">
                        <samp class="codeph nolang">legal</samp>—Key value
                      </li>

                      <li class="li"><samp class="codeph nolang">marketing</samp></li>

                      <li class="li"><samp class="codeph nolang">other</samp></li>

                      <li class="li"><samp class="codeph nolang">sales</samp></li>

                      <li class="li">
                        <samp class="codeph nolang">support</samp>—For example, tech support
                        or customer support.
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">tech</samp>—For example, IT or
                        engineering. Key value.
                      </li>

                    </ul>
                    Key values represent key contacts on an opportunity
                    or account. If a buyer relationship map doesn’t have
                    contacts with key values, then Salesforce prompts you to
                    add them. Having all key values represented on the map
                    provides a full view of the deal or account, increasing
                    sales success. This field is available with all profiles
                    except custom and minimum-access. To provide access, use
                    field-level security in Object Manager.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Description</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">textarea</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Nillable, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">A description of the contact. Label is <strong class="ph b">Contact
                      Description</strong> up to 32 KB. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">DoNotCall</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">boolean</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Defaulted on create, Filter, Group, Sort,
                    Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Indicates that the contact doesn’t want to receive
                    calls.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Email</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">email</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, idLookup, Nillable, Sort,
                    Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s email address. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">EmailBouncedDate</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">dateTime</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">If bounce management is activated and an email sent to
                    the contact results in a hard bounce, the date and time
                    of the bounce.</dd>


                </dl>

                <div class="box message info">
                  <div class="inner">
                    <div class="bd">
                      <div class="media">
                        <img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png" alt="Note">
                        <div class="mediaBd">
                          <h4 class="mbs">Note</h4>
                          <p>Email bounce functionality isn't triggered by record updates,
                            including updates to this field. </p>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">EmailBouncedReason</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">If bounce management is activated and an email sent to
                    the contact results in a hard bounce, the reason for the
                    bounce.</dd>


                </dl>

                <div class="box message info">
                  <div class="inner">
                    <div class="bd">
                      <div class="media">
                        <img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png" alt="Note">
                        <div class="mediaBd">
                          <h4 class="mbs">Note</h4>
                          <p>Email bounce functionality isn't triggered by record updates,
                            including updates to this field. </p>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Fax</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">phone</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s fax number. Label is <strong class="ph b">Business Fax</strong>.
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">FirstCallDateTime</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">dateTime</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The date and time of the first call placed to the
                    contact. This field is available in API version 48.0 and
                    later when the Sales Engagement license is enabled. To
                    see this field, the user also needs the Sales Engagement
                    User or Sales Engagement Quick Cadence Creator user
                    permission set.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">FirstEmailDateTime</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">dateTime</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The date and time of the first email sent to the
                    contact. This field is available in API version 48.0 and
                    later when the Sales Engagement license is enabled. To
                    see this field, the user also needs the Sales Engagement
                    User or Sales Engagement Quick Cadence Creator user
                    permission set.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname" id="i1446709"><a name="i1446709"><!-- --></a>FirstName</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s first name up to 40 characters. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">GenderIdentity</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd"> Create, Filter, Group, Nillable, Restricted picklist,
                    Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s internal experience of their gender, which
                    may or may not correspond to their designated sex at
                    birth.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">HasOptedOutOfEmail</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">boolean</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Defaulted on create, Filter, Group, Sort,
                    Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Indicates whether the contact doesn’t want to receive
                    email from Salesforce (<samp class="codeph nolang">true</samp>) or does (<samp class="codeph nolang">false</samp>). Label is <strong class="ph b">Email Opt
                      Out</strong>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">HasOptedOutOfFax</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">boolean</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Defaulted on create, Filter, Group, Sort,
                    Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Indicates whether the contact prohibits receiving
                    faxes.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">HomePhone</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">phone</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s home phone number. Label is <strong class="ph b">Home
                      Phone</strong>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">IndividualId</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">ID of the data privacy record associated with this
                    contact. This field is available if Data Protection and
                    Privacy is enabled.</dd>

                  <dd class="dd">This is a relationship field.</dd>



                  <dt class="dt dlterm">Relationship Name</dt>

                  <dd class="dd">Individual</dd>



                  <dt class="dt dlterm">Relationship Type</dt>

                  <dd class="dd">Lookup</dd>



                  <dt class="dt dlterm">Refers To</dt>

                  <dd class="dd">Individual</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">IsDeleted</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">boolean</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Defaulted on create, Filter</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Indicates whether the object has been moved to the
                    Recycle Bin (<samp class="codeph nolang">true</samp>)
                    or not (<samp class="codeph nolang">false</samp>).
                    Label is <strong class="ph b">Deleted</strong>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">IsEmailBounced</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">boolean</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Defaulted on create, Filter, Group, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">If bounce management is activated and an email is sent
                    to a contact, indicates whether the email results in a
                    soft or hard bounce (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>).</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname" id="i1446796"><a name="i1446796"><!-- --></a>IsPersonAccount</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">boolean</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Defaulted on create, Filter, Group, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Read only. Indicates whether this account has a record
                    type of Person Account (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). Label is <strong class="ph uicontrol">Is Person
                      Account</strong>. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">IsPriorityRecord</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <a name="dl_pml_q3h_5bc"><!-- --></a>
                <dl class="dl detailList" id="dl_pml_q3h_5bc">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">boolean</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Defaulted on create, Group</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Shows whether the user has marked the contact as
                    important (<kbd class="ph userinput">True</kbd>) or not
                    (<kbd class="ph userinput">False</kbd>). The default value is
                    <samp class="codeph nolang">false</samp>.
                    Available in API version 59.0 and later.
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname" id="JigsawField"><a name="JigsawField"><!-- --></a>Jigsaw</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">References the company’s ID in Data.com. If an account
                    has a value in this field, it means that the account was
                    imported from Data.com. If the field value is <samp class="codeph nolang">null</samp>, the account
                    wasn’t imported from Data.com. Maximum size is 20
                    characters. Available in API version 22.0 and later.
                    Label is <strong class="ph b">Data.com Key</strong>.<div class="box message confirm">
                      <div class="inner">
                        <div class="bd">
                          <div class="media">
                            <img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note_important.png" alt="Important">
                            <div class="mediaBd">
                              <h4 class="mbs">Important</h4>
                              <p><span class="ph" id="JigsawFieldImpNote"><a name="JigsawFieldImpNote"><!-- --></a>The
                                  <span class="keyword parmname">Jigsaw</span> field is exposed in
                                  the API to support troubleshooting for import
                                  errors and reimporting of corrected data. Do not
                                  modify this value.</span></p>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">JigsawContactId</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <a name="dl_ift_tqc_tcc"><!-- --></a>
                <dl class="dl detailList" id="dl_ift_tqc_tcc">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The ID of the contact in reference to
                    <span class="keyword parmname">Jigsaw</span>.<div class="box message confirm">
                      <div class="inner">
                        <div class="bd">
                          <div class="media">
                            <img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note_important.png" alt="Important">
                            <div class="mediaBd">
                              <h4 class="mbs">Important</h4>
                              <p>The <span class="keyword parmname">Jigsaw</span> field is
                                exposed in the API to support troubleshooting for
                                import errors and reimporting of corrected data.
                                Don’t modify the value in the
                                <span class="keyword parmname">Jigsaw</span>
                                field.
                              </p>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">LastActivityDate</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">date</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Value is the most recent of either: <ul class="ul bulletList">
                      <li class="li">Due date of the most recent event logged against
                        the record. </li>

                      <li class="li">Due date of the most recently closed task
                        associated with the record.</li>

                    </ul>

                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname" id="i1446872"><a name="i1446872"><!-- --></a>LastName</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Required. Last name of the contact up to 80 characters.
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">LastReferencedDate</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">dateTime</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The timestamp when the current user last accessed this
                    record, a record related to this record, or a list view.
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">LastViewedDate</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">dateTime</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The timestamp when the current user last viewed this
                    record or list view. If this value is null, the user
                    might have only accessed this record or list view
                    (<span class="keyword parmname">LastReferencedDate</span>) but not
                    viewed it.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">LeadSource</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The source of the lead that was converted to this
                    contact. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">MailingAddress</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">address</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Nillable</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The compound form of the mailing address. Read-only. For
                    details on compound address fields, see <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_address.htm" title="Standard addresses—addresses built into standard objects in Salesforce—are accessible in the SOAP API and REST API as an Address, a structured compound data type, as well as individual address elements. If you enabled Custom Address Fields, you can also add custom fields that mimic the standard address field behavior.">Address Compound Fields</a>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">MailingCity</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Mailing address details. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">MailingCountry</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Mailing address details. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">MailingCountryCode</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The ISO codes for the mailing address’s state and
                    country.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">MailingGeocodeAccuracy</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Restricted picklist,
                    Sort, Update, Query, Restricted picklist, Nillable</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Accuracy level of the geocode for the mailing address.
                    For details on geolocation compound field, see <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_limitations.htm#compound_fields_limitations" title="Address and geolocation compound fields are convenient and result in more concise, clear code. Here are some things to consider when using them in your apps.">Compound Field Considerations and Limitations</a>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="ph" id="maillat"><a name="maillat"><!-- --></a><span class="keyword parmname">MailingLatitude</span></span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">double</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd"><span class="ph" id="maillat_def"><a name="maillat_def"><!-- --></a>Used with
                      <span class="keyword parmname">MailingLongitude</span> to specify
                      the precise geolocation of a mailing address.
                      Acceptable values are numbers between –90 and
                      90 up to 15 decimal places. For details on
                      geolocation compound fields, see <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_limitations.htm#compound_fields_limitations" title="Address and geolocation compound fields are convenient and result in more concise, clear code. Here are some things to consider when using them in your apps.">Compound Field Considerations and Limitations</a>.</span></dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="ph" id="maillong"><a name="maillong"><!-- --></a><span class="keyword parmname">MailingLongitude</span></span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">double</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd"><span class="ph" id="maillongdef"><a name="maillongdef"><!-- --></a>Used with
                      <span class="keyword parmname">MailingLatitude</span> to specify
                      the precise geolocation of a mailing address.
                      Acceptable values are numbers between –180
                      and 180 up to 15 decimal places. For details on
                      geolocation compound fields, see <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_limitations.htm#compound_fields_limitations" title="Address and geolocation compound fields are convenient and result in more concise, clear code. Here are some things to consider when using them in your apps.">Compound Field Considerations and Limitations</a>.</span></dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">MailingPostalCode</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Mailing address details. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">MailingState</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Mailing address details. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">MailingStateCode</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The ISO codes for the mailing address’s state and
                    country.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">MailingStreet</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">textarea</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Street address for mailing address. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">MasterRecordId</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">If this record was deleted as the result of a merge,
                    this field contains the ID of the record that remains.
                    If this record was deleted for any other reason, or
                    hasn’t been deleted, the value is <samp class="codeph nolang">null</samp>. </dd>

                  <dd class="dd">This is a relationship field.</dd>



                  <dt class="dt dlterm">Relationship Name</dt>

                  <dd class="dd">MasterRecord</dd>



                  <dt class="dt dlterm">Relationship Type</dt>

                  <dd class="dd">Lookup</dd>



                  <dt class="dt dlterm">Refers To</dt>

                  <dd class="dd">Contact</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">MiddleName</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s middle name. Maximum size is 40
                    characters.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">MobilePhone</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">phone</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Contact’s mobile phone number. Label is <strong class="ph b">Mobile
                      Phone</strong>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Name</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Concatenation of <span class="keyword parmname">FirstName</span>,
                    <span class="keyword parmname">MiddleName</span>,
                    <span class="keyword parmname">LastName</span>, and
                    <span class="keyword parmname">Suffix</span> up to 203 characters,
                    including whitespaces.
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">OtherAddress</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">address</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Nillable</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The compound form of the other address. Read-only. For
                    details on compound address fields, see <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_address.htm" title="Standard addresses—addresses built into standard objects in Salesforce—are accessible in the SOAP API and REST API as an Address, a structured compound data type, as well as individual address elements. If you enabled Custom Address Fields, you can also add custom fields that mimic the standard address field behavior.">Address Compound Fields</a>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">OtherCity</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Alternate address details. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">OtherCountry</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Alternate address details. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">OtherCountryCode</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The ISO codes for the alternate address’s state
                    and country.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">OtherGeocodeAccuracy</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Restricted picklist,
                    Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Accuracy level of the geocode for the other address. For
                    details on geolocation compound fields, see <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_limitations.htm#compound_fields_limitations" title="Address and geolocation compound fields are convenient and result in more concise, clear code. Here are some things to consider when using them in your apps.">Compound Field Considerations and Limitations</a>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="ph" id="otherlat"><a name="otherlat"><!-- --></a><span class="keyword parmname">OtherLatitude</span></span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">double</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd"><span class="ph" id="otherlat_def"><a name="otherlat_def"><!-- --></a>Used with
                      <span class="keyword parmname">OtherLongitude</span> to specify the
                      precise geolocation of an alternate address.
                      Acceptable values are numbers between –90 and
                      90 up to 15 decimal places. For details on
                      geolocation compound fields, see <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_limitations.htm#compound_fields_limitations" title="Address and geolocation compound fields are convenient and result in more concise, clear code. Here are some things to consider when using them in your apps.">Compound Field Considerations and Limitations</a>.</span></dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="ph" id="otherlong"><a name="otherlong"><!-- --></a><span class="keyword parmname">OtherLongitude</span></span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">double</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd"><span class="ph" id="otherlongdef"><a name="otherlongdef"><!-- --></a>Used with
                      <span class="keyword parmname">OtherLatitude</span> to specify the
                      precise geolocation of an alternate address.
                      Acceptable values are numbers between –180
                      and 180 up to 15 decimal places. For details on
                      geolocation compound fields, see <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/compound_fields_limitations.htm#compound_fields_limitations" title="Address and geolocation compound fields are convenient and result in more concise, clear code. Here are some things to consider when using them in your apps.">Compound Field Considerations and Limitations</a>.</span></dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">OtherPhone</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">phone</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Phone for alternate address. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">OtherPostalCode</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Alternate address details. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">OtherState</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Alternate address details. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">OtherStateCode</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The ISO codes for the alternate address’s state
                    and country.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">OtherStreet</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">textarea</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Street for alternate address. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">OwnerId</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Defaulted on create, Filter, Group, Sort,
                    Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The ID of the owner of the account associated with this
                    contact. </dd>

                  <dd class="dd">This is a relationship field.</dd>



                  <dt class="dt dlterm">Relationship Name</dt>

                  <dd class="dd">Owner</dd>



                  <dt class="dt dlterm">Relationship Type</dt>

                  <dd class="dd">Lookup</dd>



                  <dt class="dt dlterm">Refers To</dt>

                  <dd class="dd">User</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Phone</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">phone</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Phone number for the contact. Label is <strong class="ph b">Business
                      Phone</strong>.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">PhotoUrl</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">url</dd>


                </dl>

                <dl class="dl detailList">

                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Group, Nillable, Sort</dd>


                </dl>

                <dl class="dl detailList">

                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">
                    <p class="p">Path to be combined with the URL of a Salesforce
                      instance (<em class="ph i">Example:</em>
                      https://<var class="keyword varname">yourInstance</var>.salesforce.com/)
                      to generate a URL to request the social network
                      profile image associated with the contact. Generated
                      URL returns an HTTP redirect (code 302) to the
                      social network profile image for the contact.</p>

                    <p class="p">Empty if Social Accounts and Contacts isn't enabled
                      or if Social Accounts and Contacts is disabled for
                      the requesting user.</p>

                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Pronouns</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd"> Create, Filter, Group, Nillable, Restricted picklist,
                    Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The contact’s personal pronouns, reflecting their gender
                    identity. Others can use these pronouns to refer to the
                    contact in the third person. The entry is selected from
                    a picklist of available values, which the administrator
                    sets. Maximum 40 characters.</dd>

                  <dd class="dd">Possible values are: <a name="contact_pronouns"><!-- --></a>
                    <ul class="ul bulletList" id="contact_pronouns">
                      <li class="li"><samp class="codeph nolang">He/Him</samp></li>

                      <li class="li"><samp class="codeph nolang">He/They</samp></li>

                      <li class="li"><samp class="codeph nolang">Not
                          Listed</samp></li>

                      <li class="li"><samp class="codeph nolang">She/Her</samp></li>

                      <li class="li"><samp class="codeph nolang">She/They</samp></li>

                      <li class="li"><samp class="codeph nolang">They/Them</samp></li>

                    </ul>
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname" id="i1438294"><a name="i1438294"><!-- --></a>RecordTypeId</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Nillable, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">ID of the record type assigned to this object. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname" id="i1447142"><a name="i1447142"><!-- --></a>ReportsToId</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">reference</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">ID of the contact that this contact reports to.</dd>

                  <dd class="dd">This is a relationship field.</dd>



                  <dt class="dt dlterm">Relationship Name</dt>

                  <dd class="dd">ReportsTo</dd>



                  <dt class="dt dlterm">Relationship Type</dt>

                  <dd class="dd">Lookup</dd>



                  <dt class="dt dlterm">Refers To</dt>

                  <dd class="dd">Contact</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Salutation</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Honorific abbreviation, word, or phrase to be used in
                    front of name in greetings, such as Dr. or Mrs. </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">ScheduledResumeDateTime</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">dateTime</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Filter, Nillable, Sort</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">The date and time when the action cadence tracker is
                    going to resume after it’s paused or on a wait step.
                    This field is available in API version 54.0 and later
                    when the Sales Engagement license is enabled. To see
                    this field, the user also needs the Sales Engagement
                    User or Sales Engagement Quick Cadence Creator user
                    permission set.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">Suffix</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Name suffix of the contact. Maximum size is 40
                    characters.</dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field">
                <span class="keyword parmname">Title</span>
              </td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">string</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">Title of the contact, such as CEO or Vice President.
                  </dd>


                </dl>

              </td>

            </tr>

            <tr>
              <td class="entry" headers="d438570e120" data-title="Field"><span class="keyword parmname">TitleType</span></td>

              <td class="entry" headers="d438570e123" data-title="Details">
                <dl class="dl detailList">

                  <dt class="dt dlterm">Type</dt>

                  <dd class="dd">picklist</dd>



                  <dt class="dt dlterm">Properties</dt>

                  <dd class="dd">Create, Filter, Group, Nillable, Restricted picklist,
                    Sort, Update</dd>



                  <dt class="dt dlterm">Description</dt>

                  <dd class="dd">If Automatic Contact Enhancements or Buyer Relationship
                    Map is enabled, this field contains the hierarchical
                    position that the contact holds in the organization. In
                    the UI, this field is shown as Seniority Level. Possible
                    values are: <ul class="ul bulletList">
                      <li class="li">
                        <samp class="codeph nolang">ceo</samp>—Key value
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">directorOrManager</samp>—Key value
                      </li>

                      <li class="li">
                        <samp class="codeph nolang">executive</samp>—Key value
                      </li>

                      <li class="li"><samp class="codeph nolang">individualContributor</samp></li>

                      <li class="li">
                        <samp class="codeph nolang">vp</samp>—VP or Head of Department. Key
                        value.
                      </li>

                    </ul>
                    Key values represent key contacts on an opportunity
                    or account. If a buyer relationship map doesn’t show
                    contacts with key values, then Salesforce prompts you to
                    add them. Having all key values represented on the map
                    provides a complete picture of the deal or account,
                    increasing sales success. This field is available with
                    all profiles except custom and minimum-access. To
                    provide access, use field-level security in Object
                    Manager.</dd>


                </dl>

              </td>

            </tr>

          </tbody>

        </table>

![Note](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png)

#### Note

When importing contact data, users need the Set Audit Fields upon Record Creation permission to assign values to audit fields such as CreatedDate. Audit fields are automatically updated during API operations unless you set these fields yourself.

## Usage

Use this object to manage individual people who are associated with an account. You can create, query, delete, or update any attachment associated with a contact.

Create or update contacts by converting a lead with the convertLead() call.

## Associated Objects

This object has these associated objects. If the API version isn’t specified, they’re available in the same API versions as this object. Otherwise, they’re available in the specified API version and later.

[AccountChangeEvent](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_associated_objects_change_event.htm "A ChangeEvent object is available for each object that supports Change Data Capture. You can subscribe to a stream of change events using Change Data Capture to receive data tied to record changes in Salesforce. Changes include record creation, updates to an existing record, deletion of a record, and undeletion of a record. A change event isn’t a Salesforce object—it doesn’t support CRUD operations or queries. It’s included in the object reference so you can discover which Salesforce objects support change events.") (API version 44.0)

Change events are available for the object.

[ContactFeed](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_associated_objects_feed.htm "StandardObjectNameFeed is the model for all feed objects associated with standard objects. These objects represent the posts and feed-tracked changes of a standard object.") (API version 18.0)

Feed tracking is available for the object.

[ContactHistory](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_associated_objects_history.htm "StandardObjectNameHistory is the model for all history objects associated with standard objects. These objects represent the history of changes to the values in the fields of a standard object.") (API version 11.0)

History is available for tracked fields of the object.

[ContactOwnerSharingRule](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contactownersharingrule.htm "Represents the rules for sharing a contact with a User other than the owner.")

Sharing rules are available for the object.

[ContactShare](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contactshare.htm "Represents a list of access levels to a Contact along with an explanation of the access level. For example, if you have access to a record because you own it, the ContactAccessLevel is All and RowCause is Owner.")

Sharing is available for the object.

#### See Also

- [Overview of Salesforce Objects and Fields](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_concepts.htm "Salesforce objects and fields are analogous to database tables and the table columns. Objects and fields structure data. For example, the central object in the Salesforce data model represents accounts—companies and organizations involved with your business, such as customers, partners, and competitors.")