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 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 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 that a renewal call went well for your company? 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 vary the most between companies. It is worth adjusting their variables with the team before starting to use them as a basis for decisions.

Specific fields are the ones your team creates to record specific information from your 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.

Each specific field is configured with a response type that defines how diio extracts and presents the information:

Number:

List:

From a list:

Yes or no:

Free text:

Each specific field can be mapped to a CRM property. 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.

Only Team Coordinators and the Team Administrator can create, edit, and delete specific fields at account level. This restriction exists to maintain consistency in CRM data: if every executive could define their own fields, reports would lose comparability.