A CRM-linked field is a field diio extracts from each conversation and that, when syncing, is automatically written into a property in your CRM.
It's how you get structured information from conversations straight into the contact, company, or deal record, without anyone having to copy it by hand.
Before you start
To link a diio field to the CRM, you need:
The CRM connected to your diio account, under diio settings → Integrations.
The CRM property you want to link to must already exist. diio doesn't create properties: if it doesn't exist, it has to be created first in HubSpot, Salesforce, Pipedrive, Zoho, or Odoo, and then selected from diio.
The Team Coordinator or Teams Administrator role in diio (on the Starter plan, Administrator).
Steps to link the field
Linking happens from the field itself, inside the playbook. There's nothing to configure separately.
Go to diio settings → Playbooks and open the playbook.
Move ahead to the editor's "Fields" step.
Turn on the field you want to link.
Under "Linked CRM properties", click Link property.
Search for your CRM property and select it. The search groups them by object: Contact, Company, Deal.
Save with Save progress, or move ahead to the last step and click Confirm and save.
The response type has to match
The field's response type in diio has to be compatible with the property type that exists in the CRM. If they don't match, the property doesn't appear as an option, or the value isn't written.
Text → text property.
Number → numeric property.
Single select → single-select property.
Multi select → property that accepts multiple values.
When the CRM property uses predefined options, the field's values must match those options exactly. If the stage in your CRM is called "Proposal sent" and the diio field returns "Proposal delivered", the value won't match and the property won't be updated. Field options are defined by diio and can't be edited from the playbook, so only link the field to properties whose options match exactly as written, including capitalization and accents.
Which CRM object gets updated
The object depends on what information the field extracts and how your CRM is structured:
Information about the person (job title, role in the decision) → Contact.
Information about the company (industry, size, technologies it uses) → Company, Account, or Organization, depending on the CRM.
Information about the process (stage, budget, estimated close date) → Deal, Opportunity, or Lead, depending on the CRM.
What happens when syncing
When the conversation is synced to the CRM, diio writes the extracted value into the linked property of the corresponding object.
Sync goes in one direction only: from diio to the CRM. If someone edits that value directly in the CRM, the change isn't reflected in diio, and a later sync could overwrite it.
Only link what someone is going to use
A field that travels to the CRM only has value if the team checks it to make decisions. If it's been sitting there for months and nobody looks at it, remove it from the playbook: it reduces noise and frees up quota for information that actually matters.
Remember that the number of fields per playbook depends on your plan: up to 5 on Starter, up to 10 on Business, and custom configuration on Enterprise.
If the value doesn't reach the CRM
Check that the field's response type is compatible with the property type.
If the property uses predefined options, check that the field's options are written exactly the same way.
Confirm that the conversation was actually synced to the CRM.
Check that the field's question can be answered by reading the conversation: if diio didn't find the data, there's no value to write.
