If the Account is a company, a Contact is the person you communicate with at that company. If the Account is an individual, a Contact can be any related person who communicates on behalf of the customer.

1. Example Business Scenarios

• For company Accounts, the Account is the organization (for example, “Beijing XX Technology Co., Ltd.”); Contacts are the organization’s personnel who facilitate sales communication or handle after-sales service, such as the Purchasing Manager or the Receiving Contact.
• For individual Accounts, the Account represents the primary person for the Opportunity; you can add related Contacts as secondary contacts for the Opportunity (for example, in a real estate transaction where the Account is “Mr. Li”, a Contact could be his spouse or child).

2. Detailed Description of Contacts

2.1 Contact Preset Views

• All: Records where the owner is the current user or the current user’s subordinate, or where a related team member includes the current user or the current user’s subordinate, or where a “data sharing” rule in Data Permission Management shares records owned by a record owner or the owner’s Dept. with the current user, the current user’s Dept., or the current user’s user group, or where the data belongs to “My Responsible Departments”.
• Owner is current user or current user’s subordinate.
• Or a related team includes the current user or the current user’s subordinate.
• Or the Data Permission Management “data sharing” rule for Contacts shares records owned by the record owner or the owner’s Dept. with the current user, the current user’s Dept., or the current user’s user group.
• Or data belongs to “My Responsible Departments”.
• My Responsibilities (Contacts): owner is the current user.
• Participated by Me (Contacts): related team includes the current user.
• Contacts without an associated Account: owner is the current user and the Account lookup is empty.
• My subordinates’ Contacts: owner is a subordinate of the current user.
• Contacts my subordinates participate in: related team includes the current user’s subordinates.
• Shared With Me: Data Permission Management is configured to share Contact records owned by a record owner or the owner’s Dept. with the current user, the current user’s Dept., or the current user’s user group.
• My Responsible Departments: the current user is the head of their primary Dept., and the primary Dept. of related team members in the record is that Dept. Note: Whether the responsible Dept. includes all subordinate data is controlled by CRM Management → Rules Settings → Basic Settings → “Upper-level Visible Data Range”.
• The current user is head of their primary Dept.
• The primary Dept. of related team members in the record is that Dept.
• Note: Whether the responsible Dept. includes all subordinate data is controlled by CRM Management → Rules Settings → Basic Settings → “Upper-level Visible Data Range”.

Note:

• CRM Administrators can view all data.
• Records whose status is “void” are visible only to CRM Administrators; other users cannot see them.

2.2 Contact Business Operations

2.2.1 Create a Contact

• Creation methods:
  • Manual creation from the Contacts list view.
  • From an Account detail page under Contacts.
  • From an Opportunity detail page under Contacts.
  • From a Visit (Activity) detail page under Contacts.
  • Scan business card on mobile to create an Account and Contact.
  • Convert a Lead into a Contact during Lead conversion. (Conversion entry: Leads list → Detail → More → Actions → Convert Lead)
  • Import. See: https://help.fxiaoke.com/2615/3eab/856c/5765#header-2
• Duplicate-check on Contact creation: The system validates duplicates to ensure data quality. Configure Contact duplicate rules in backend management. See: http://help.fxiaoke.com/2615/9ad7/82a7/89e6/3519
  • If all conditions in “New-record duplicate check” are set to Exact Match, creation fails when an existing Contact matches.
  • If all conditions are set to Fuzzy Match, the system lists similar Contacts for review but still allows completing the new Contact creation.
• Save and create Contact when creating an Account: When creating an Account, the “Save and Create Contact” option lets you quickly add a Contact to improve entry efficiency.

2.3 Common Contact Operations

• Common list view operations: http://help.fxiaoke.com/2615/3eab/856c/76b1
• Add Sales Activity (Sales Record): http://help.fxiaoke.com/2615/3eab/856c/4bc2
• Common business actions include: change owner, add related team members, print, import, export, edit, void, delete, etc. See: http://help.fxiaoke.com/2615/3eab/856c/863a
• Collaboration features include: forward, Calendar, reminders, make calls, send emails, etc. See: http://help.fxiaoke.com/2615/3eab/856c/863a

2.4 Email

• Purpose: Store email exchanges associated with the Contact to preserve communication history for the current employee.
• Entry point: “Email” on the Contact detail page.
• Email tracking: Sent emails can be tracked for read status. If the recipient has read the email, the email history will show a read icon; if unread, it will show an unread icon.
• Related actions:
  • Filter by Received by me, Sent by me, or All.
  • Send email.