A custom field linked to the CRM is a field diio extracts from each conversation and that, when syncing, is written automatically into a property in your CRM.
It is 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 Settings → Integrations.
The CRM property you want to link to must already exist. diio does not create properties: if it does not exist, it has to be created first in HubSpot, Salesforce, Pipedrive, Zoho, or Odoo, and then selected from diio.
The Team Coordinator or Settings Admin role in diio.
Steps to link the field
Linking happens from the field itself, inside the playbook. There is nothing to configure separately.
Go to Settings → Playbooks and open the playbook.
Go to the "Fields" section.
Enable the field you want to link and expand its configuration.
Under "CRM properties", click + Link property.
Search for your CRM property and select it. The search groups them by object: Contact, Company, Deal.
Save.
The response type has to match
The response type you configure in diio has to be compatible with the property type that exists in the CRM. If they do not match, the property does not appear as an option, or the value is not 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 has to respect those options exactly. If the stage in your CRM is called "Proposal sent" and you configure "Proposal delivered" in diio, the value will not match and the property will stay empty. Copy the options exactly as they are written in the CRM, 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, tools they use) → 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 syncs to the CRM, diio writes the extracted value into the linked property of the corresponding object.
The sync runs one way only: from diio to the CRM. If someone edits that value directly in the CRM, the change is not reflected in diio, and a later sync could overwrite it.
Only link what someone will actually use
A field that travels to the CRM is only worth something if the team consults it to make decisions. If it has been sitting there for months and nobody looks at it, remove it from the playbook: it cuts noise and frees up quota for information that does matter.
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 is not reaching the CRM
Check that the field's response type is compatible with the property type.
If the property uses predefined options, verify the field's options are written exactly the same way.
Confirm the conversation actually synced to the CRM.
Check that the field's question can be answered by reading the conversation: if diio did not find the data, there is no value to write.