Opportunities - FAQs

General Questions

Q: How to export opportunities from Adaptive AI?

Q: How do I share a specific opportunity with my team? To share a specific opportunity:

The shared link will take them directly to the specific opportunity and its details, improving collaboration and saving time.

Q: How to track all activities in my opportunity and find the Opportunity ID?

Q: How does the feature of Multiple Contacts per Opportunity currently work?

Q: How do I find the names and details of contacts on lost opportunities?

Custom Fields Questions

Q: How can I see my custom fields in an Opportunity? When you go to 'Opportunities' and select or create an opportunity, you'll see your custom fields listed. When you edit an opportunity, these fields are available for input. If you've organized your fields into folders, these will appear one after the other.

Q: What does the 'hide empty fields' feature do? When enabled, the 'hide empty fields' feature hides all fields with no value. This allows you to focus only on fields that are relevant or required for you, providing a cleaner, more streamlined view of your opportunity data.

Q: How can I edit the values in "lost reason" field under Opportunities

Step 1: Go to Settings > Custom Fields Step 2: Select Lost Reason and click on Bulk Actions > Edit

Step 3: Make changes to your lost reason values in the modal and save for them to reflect.

If the name of the lost reason is changed for any of these instances, all the places where the lost reason was being invoked will start showing the new name for the same.

Before you begin

“Opportunities - FAQs” is part of the Opportunities → Board View area in Adaptive AI. Manage opportunities on a visual pipeline board. 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.