The conversation type (shown in the app as Playbook Type) is the second level of how playbooks are organized. It identifies the nature of the conversation within a use case.
It's what you choose after the use case and before configuring the playbook.
The type doesn't identify the team
It identifies what kind of conversation it is, not who has it. A Discovery is still a Discovery whether the Sales team or the Prospecting team runs it, in Chile or in Mexico.
Choose the option that best represents the conversation you want diio to analyze, not the one that best describes the area running it.
Sales conversation types
Discovery. A conversation aimed at understanding the potential customer's context, needs or problems.
Sales Presentation. A conversation aimed at presenting a solution and connecting it to the customer's needs.
Sales Follow-up. A later conversation whose purpose is to pick up open items and create progress.
Negotiation. A conversation aimed at resolving terms or objections that are blocking progress toward the close.
Each use case has its own conversation types. In diio settings → Playbooks, opening a use case shows the available Playbook types and how many playbooks each one contains.
What the conversation type determines
The type you choose influences the suggested fields diio proposes, the predefined evaluation criteria and the vocabulary diio uses to interpret the conversation. It's not just a filter for sorting the list.
Several playbooks within the same type
You can have several playbooks within the same type, as long as each one analyzes that conversation differently.
For example, within Discovery you might have "Discovery Inbound" and "Discovery Enterprise" if they have different objectives, success criteria or relevant information. If only the country, the office or the executive changes, use the same playbook: fewer well-configured playbooks analyze better than many that look alike.
Don't confuse it with the channel
The conversation type describes the nature of the conversation (Discovery, Negotiation). The channel describes how it happened: Meeting, Call or Message (and Emails, depending on your company's configuration).
They are two separate settings. The same conversation type can happen across several channels, and the channel is defined inside the playbook, in the context stage, with the Channel selector. If you leave the playbook on "Any", it competes across all channels.
