Fields are the backbone of diio's analysis. They are the pieces of information that diio extracts from each conversation and delivers in a structured way so you can act on them —without taking notes, without manually copying data to the CRM.
Understanding the two types of fields in diio helps you know what comes ready from day one and what you can customize so the analysis reflects exactly what your process needs to record.
Default fields
Default fields are the ones diio brings ready according to the playbook Type you use. You don't need to configure them: they are available from the first analysis.
Most simply extract: they identify objections, detect the counterpart's mood, list the topics covered. But two default fields are special because they have adjustable variables your team can calibrate:
Performance: evaluates how the conversation was conducted according to the criteria the team defines. What does it mean for your company that a renewal call went well? That is configured here.
Success Prediction: estimates the probability that the conversation advances to the next step, based on the success indicators the team defined in the playbook.
These two fields are the ones that vary the most between companies. It's worth adjusting their variables with the team before you start using them as a basis for decisions.
Specific fields
Specific fields are the ones your team turns on in the playbook, from the diio catalog, to record particular information from its own process: something not covered by the default fields and important to capture in every conversation of that playbook.
Examples by use case:
Sales: Available budget · Number of users · Decision date · Is budget approved?
Recruiting: Salary expectation · Start availability · Interest level (1-5).
Post-sales: Contact reason · Would they renew? · Satisfaction level.
Available response types
Each specific field has a response type, defined by diio, that determines how diio extracts and presents the information:
Number: a quantity. Example: "Number of users" → 47.
List: a list of items. Example: "Topics covered" → [price, implementation, support].
From a list: a predefined option. Example: "Process stage" → [Prospect, Qualified, Proposal sent, Negotiation].
Yes or no: binary answer. Example: "Is budget approved?" → Yes.
Free text: open answer. Example: "Additional context" → unstructured text.
How specific fields connect to the CRM
Each specific field can be mapped to a property in your CRM. When diio syncs the conversation, the extracted value travels automatically to the corresponding field in HubSpot, Salesforce, Pipedrive, Zoho or Odoo.
This eliminates the manual step of opening the CRM and copying the information: diio does it for you every time a conversation from that playbook is analyzed.
Who can manage specific fields
Field definitions are created by diio: you can't create new fields or choose their response type. Team Coordinators and the Teams Administrator can turn on, rename or duplicate catalog fields in their playbooks and link them to CRM properties. This restriction exists to keep CRM data consistent: if every executive could manage their own fields, reports would lose comparability.