Skip to main content
Reference — comprehensive feature documentation.

​
What is Suggested Field Updates from Notes?

Suggested Field Updates from Notes is an AI-powered Labs feature that analyzes your meeting notes and automatically suggests CRM field updates—funding stage, revenue, team size, location, and more. Instead of manually reading through notes and updating fields one by one, you can trigger AI analysis and review a curated list of suggested updates, then accept them all in one click or selectively apply only what looks right. The workflow: Write your note → Click Analyze → Review suggested field updates → Select which to accept → Click Apply What it eliminates: Manual data entry after meetings. The AI reads your notes, extracts structured data, and suggests field updates with before/after comparison for each change. Who it’s for: Investment professionals who take detailed meeting notes and want to keep CRM fields current without manual copy-paste work. Where to access: Notes tab on profiles, Notes Center, list Notes sidebar, or single note pages—anywhere notes live in Affinity. Feature status: Active Labs experiment (launched April 2026)

​
How to Use Suggested Field Updates

​
Option 1: While Adding or Editing a Note

  1. Write your note as usual (capture meeting details, metrics, updates)
  2. Before publishing, click the Analyze button
  3. AI analyzes the note and surfaces suggested field updates
  4. Review the suggestions modal:
    • See before/after comparison for each field
    • Each suggestion shows which part of your note it came from
    • Select/unselect individual suggestions
  5. Click Apply to update selected fields
  6. Note publishes with fields updated
Use this when: You want field updates to happen as part of your note-taking workflow—write the note, extract the data, publish, and you’re done.

​
Option 2: From an Existing Note

  1. Find any note you can view (Notes tab, Notes Center, list sidebar, single note page)
  2. Open the three-dot menu on the note
  3. Select Suggest Field Updates
  4. Review and apply suggestions same as above
Use this when: You’ve already published a note and realize it contains field-relevant data, or you’re reviewing old notes and want to update fields retroactively.

​
Understanding the Suggestions Modal

What you’ll see: Before/After Comparison:
  • Current field value (what’s in the CRM now)
  • AI-suggested value (what the note indicates)
  • Clear visual diff showing what will change
Source Attribution:
  • Each suggestion highlights the relevant text from your note
  • See exactly what the AI read to generate the suggestion
  • Builds trust through transparency
Controls:
  • Select all: Apply every suggestion with one click
  • Uncheck individual: Remove suggestions that look wrong
  • Regenerate: Re-run analysis (helpful if you edited the note)
  • Thumbs up/down: Give feedback on suggestion quality
  • Written feedback: Submit detailed comments about the feature
No inline editing: If a suggested value is wrong, uncheck it and update the field manually after closing the modal.

​
What Fields Can Receive Suggestions?

​
Supported Field Types

The AI can suggest updates for these field types:
  • Text (plain text, short phrases)
  • Multiline text (longer text, paragraphs)
  • Number/Float (revenue, funding amounts, metrics, percentages)
  • Date (explicit dates like “February 2023” or relative dates like “last year” are both supported)
  • Location (city, state, country)
Not supported:
  • Dropdown fields
  • Multi-value fields
  • Person/Company/Opportunity relationship fields
  • Boolean, URL, formula, and other specialized types
Note: Relative dates (“last quarter”, “six months ago”) are calculated relative to the note creation date.

​
Field Eligibility by Entity Type

​
For Company and Person entities:

Suggestions are generated for global fields only (not list-specific fields)—including Affinity Data enriched fields and custom global fields. Critical requirement: The field must be configured to display on the profile by an admin via Settings > Profile Field Customization. Even if a field is the right type, it won’t receive suggestions unless it’s enabled in Profile Settings. Why this matters: Admins control which fields are eligible for AI suggestions. If a supported field isn’t surfacing suggestions, check Profile Settings first.

​
For Opportunity entities:

Suggestions are generated for list-specific fields. The Profile Settings requirement does not apply—all supported field types on the opportunity can receive suggestions.

​
For all entity types:

Fields must be manually editable, and identity fields (name, primary domain, email address) are excluded from suggestions.

​
Permissions

Your existing permissions are always respected—you can only generate field suggestions from notes you have permission to view.

​
Current Limitations

Multi-entity notes not supported: Suggest Field Updates only works for notes associated with exactly one entity (one company, one person, or one opportunity). If a note is associated with multiple entities, the feature is disabled for that note. Meeting participant associations don’t count: A meeting note with multiple attendees but no explicit entity association won’t have Suggest Field Updates available. Limited Notetaker support: Notetaker notes don’t typically have an explicit entity association (they appear on profiles via participant associations), so Suggest Field Updates won’t be available for most Notetaker notes in v1. Workaround: Edit the Notetaker note and manually associate it with a specific company, person, or opportunity to unlock the feature. Future improvement: Enabling Notetaker notes without manual association is a planned enhancement. No bulk processing: This applies to individual notes only. There’s no way to run field extraction across historical notes at once—you must analyze notes one at a time. No inline editing: You can’t edit suggested values in the modal. If a suggestion is wrong, uncheck it and update the field manually. List-specific fields for Company/Person: Not supported in v1. Only global fields receive suggestions. List-specific field support is a planned enhancement based on customer feedback.

​
Troubleshooting

​
”Suggest Field Updates” option isn’t showing

Check:
  1. Feature is enabled in Settings > Labs
  2. Note is associated with exactly one entity (not multiple or none)
  3. You have permission to view the note
Solution: Enable Labs feature if off. For multi-entity notes, the feature isn’t available by design.

​
No suggestions appear after running analysis

Possible causes:
  1. AI couldn’t find field-relevant information in the note
  2. All relevant fields are already up to date
  3. Note doesn’t contain structured data (dates, numbers, locations, etc.)
  4. Fields in question aren’t configured to display on profile (Company/Person only)
  5. Field types aren’t supported
Solution:
  1. Confirm note contains relevant data (funding stage, revenue, location, dates)
  2. Check that field values aren’t already current
  3. For Company/Person profiles: Verify fields are enabled in Settings > Profile Field Customization (admin required)
  4. Confirm fields are supported types (text, multiline text, number, date, location)

​
Suggested value looks wrong

What to do:
  1. Uncheck that suggestion (don’t apply it)
  2. Update the field manually with correct value
  3. Give thumbs down feedback in the modal
  4. Submit written feedback explaining what was wrong
Your feedback helps improve the AI.

​
Feature not available on Notetaker notes

Why: Notetaker notes don’t have explicit entity associations (they appear via participant associations). Workaround:
  1. Edit the Notetaker note
  2. Manually associate it with a company, person, or opportunity
  3. Save
  4. Now Suggest Field Updates will be available
Note: Improving Notetaker support is a planned enhancement.

​
Best Practices

Write notes with field-relevant data: The AI can only suggest updates if your notes contain structured information. Include details like:
  • Funding stage and amounts (“Raised Series B, $15M”)
  • Revenue and metrics (“$5M ARR, 40% YoY growth”)
  • Team size (“25 employees, hiring 10 more”)
  • Location (“Headquartered in San Francisco, expanding to NYC”)
  • Dates (“Founded in 2019”, “Planning Series C for Q3 2024”)
Review suggestions before applying: AI suggestions are highly accurate but not perfect. Always review the before/after comparison to catch:
  • Incorrect extractions (AI misread the note)
  • Outdated information (note is old, field already updated)
  • Ambiguous values (“$5M” could be revenue or funding—AI guessed)
Use Analyze after significant meetings: If a meeting covered financial updates, strategic changes, or company milestones, run Analyze to catch field updates you might have missed. Provide feedback: Thumbs up/down and written feedback directly improve the AI. Share:
  • Which field types work well vs. struggle
  • Common extraction errors
  • Fields you wish were supportedRelated Features