Contacts: Sync Attachments to Document Management Tab

Task-specific steps

Conversation attachments can be copied into a contact's Documents area so important files are available from the contact record rather than buried in a message thread.

1. 1Open Conversations, select the correct contact, and locate the message that contains the attachment.
2. 2Open the message's three-dot menu and choose Add to Documents. Confirm that you are saving the intended file to the intended contact.
3. 3When sending an attachment by SMS or email, enable Add to Documents before sending if the outgoing file should also be retained.
4. 4Open the contact record and select its Documents or Document Management tab.
5. 5Find the saved file, preview it when the file type supports preview, and confirm its name and contents are correct.
6. 6Rename or organize the document according to your team's records policy without removing information required for audit or service delivery.

Feature-specific checks

• The same message-menu process applies to supported email, SMS, Instagram, Facebook, and connected WhatsApp conversations.
• Preview availability can vary by file type and channel; download and validate the file when preview is unavailable.
• Do not copy sensitive attachments unless the contact record and staff permissions are appropriate for that information.

Before you begin

“Contacts: Sync Attachments to Document Management Tab” is part of the Contacts → All Contacts area in Adaptive AI. Create and manage complete contact records. Contact, opportunity, pipeline, field, tag, follower, and task changes should preserve clean ownership and reporting. Validate with a test record before applying the same behavior broadly. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Define the field, owner, pipeline stage, task, tag, or relationship being changed and how the team will use it afterward.
• Check for existing fields, tags, pipelines, duplicate records, and automations that may already represent the same information.
• Use a clearly labeled test contact or opportunity with enough sample data to exercise filters, assignments, and merge values.
• Confirm field type, allowed values, date format, ownership rules, and required permissions before importing or automating updates.
• Identify reports, smart lists, workflows, forms, and integrations that depend on the record property you are changing.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Make the change on the test record and confirm the saved value, owner, stage, follower, task, tag, or attachment is correct.
2. 2Refresh the record and verify the result appears in list, board, filter, search, and reporting views where expected.
3. 3Trigger any dependent workflow or notification and confirm it uses the updated value without creating duplicates.
4. 4Check permissions with a non-admin test user when the information should be visible or editable by a specific role.
5. 5Reverse or archive the test change and confirm the operational process handles that lifecycle cleanly.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm the record is in the correct business, pipeline, smart list, or object before assuming the update failed.
• Check field type, date format, required values, duplicate rules, and ownership permissions when a save is rejected.
• Review filters and board settings when a correct record exists but is hidden from the current view.
• Inspect workflow history and integration mappings if the value changes back or a duplicate record appears after saving.
• Test the smallest single-record change first before using bulk actions, imports, or automation across the database.

Best practices

• Give fields, pipelines, stages, tags, and tasks names that describe one clear business meaning.
• Avoid storing the same fact in multiple fields unless a documented integration requires it.
• Limit bulk edits and deletion permissions, export a backup before major imports, and document the intended rollback path.
• Use ownership and follower rules consistently so assignments remain useful for accountability and reporting.
• Audit stale tags, unused fields, duplicate records, overdue tasks, and stalled opportunities on a regular schedule.