Delete a Contact deliberately and understand the history that remains

A Contact represents a person in the customer relationship. Deleting one can affect customer login and relationships as well as the active Contacts list. Historical cases and audit records remain available, so this action should not be described as complete privacy or data erasure. Identify the exact person and reason first; for a duplicate, review the separate merge workflow instead of deleting useful history by assumption.

Decide whether deletion is the right action  ·  Identify the exact Contact and inspect its context  ·  Delete one Contact from its record  ·  Delete explicitly selected Contacts from the list  ·  Understand what deletion changes  ·  Example: clean up a customer relationship without losing context  ·  Troubleshoot deletion safely

Decide whether deletion is the right action

State the purpose clearly. Removing a confirmed unwanted record, consolidating duplicate people and resolving a customer access issue are different tasks. Deletion should not be a quick experiment to see whether a login or relationship problem goes away.

This article does not prescribe an unverified Archive or restore control. Keep the record until the right action is understood if the purpose or impact is uncertain.

Identify the exact Contact and inspect its context

1. Open Customers → Contacts. Search using a specific name or identifying detail.
2. Compare the Company, exact email and other available identity information. People with similar names or shared mailboxes may be different records.
3. Open the Contact and inspect relevant cases, customer notes, portal/customer relationships, assets and other linked context available to your role.
4. Decide how any ongoing customer communication or case association should be handled. Complete necessary operational changes through their normal workflows.
5. Confirm that you have Delete contacts permission and the authority to delete this particular record. Editing permission alone is not deletion permission.

For a B2B customer with several offices and contacts, check the actual relationship before removing a record. A former employee’s historical case can still be relevant to a colleague’s current issue. Preserved history and current customer access should be considered separately.

Delete one Contact from its record

1. Open the verified Contact record.
2. Choose Delete.
3. Read the confirmation Delete this Contact? This action cannot be undone. Confirm the identity and purpose before accepting the deletion.
4. After success, the workspace returns to Contacts. Verify that the intended Contact is no longer available as an active record.
5. Check the relevant ongoing case/customer workflow separately; disappearance from the list alone does not verify every downstream consequence.

Delete explicitly selected Contacts from the list

1. Open Contacts and narrow the list to the intended records.
2. Select the specific rows you have reviewed. Do not rely on Select all matching; deletion is blocked for that selection mode.
3. Choose Delete.
4. In Delete Contacts, review the displayed count and the notice that historical cases and audit records remain available. Cancel if the selection is not exactly what you intended.
5. Choose Apply only for the approved, reviewed selection.
6. Review the resulting list and any reported outcome before making another request. If the result is unclear, inspect the records before retrying.

Bulk deletion magnifies an identity mistake. Review the actual selected people and Companies, not just the search term that produced the list. A broad search such as a Company name is not itself proof that every matching Contact should be deleted.

Understand what deletion changes

Core marks the Contact deleted and inactive. It removes selected customer-side links, credentials, discussions, synchronization/tag/social/email links and asset-relationship information, and removes the Contact’s knowledge-quality snapshots. The exact impact therefore extends beyond hiding a row.

Historical cases, notes, files, roles, custom values, watches and audit rows are preserved as queryable history by the current deletion lifecycle. Do not promise that case history has vanished, that all historical reporting loses its reference, or that the operation is a complete erasure of personal information.

A retained historical case and a current customer login are separate things. Review the intended portal and relationship consequences through the normal authorized process. The operation should never be used as a shortcut for granting another Contact access to the deleted person’s history.

Example: clean up a customer relationship without losing context

A customer administrator reports that a named contact has left their organization. The support team first checks which current cases and updates depend on that person, confirms the new authorized contact, and updates the ongoing work through the appropriate process. The team then follows its customer-record policy to decide whether deletion is appropriate.

If deletion is approved, the administrator verifies the exact Contact and performs the action. They check the active list and relevant customer workflow afterward, while recognizing that older cases and audit records remain. This avoids confusing a current-access change with removal of the organization’s support history.

Troubleshoot deletion safely

Continue learning

• Understand Companies, Contacts and support relationships
• Merge genuine duplicate records
• Review customer-portal access configuration
• Understand portal Division scope for customer cases