Conversation Completeness
The conversation completeness metric is a conversational metric that determines whether your LLM chatbot is able to complete an end-to-end conversation by satisfying user needs throughout a conversation.
Required Arguments
To use the ConversationCompletenessMetric, you'll have to provide the following arguments when creating a ConversationalTestCase:
turns
You must provide the role and content for evaluation to happen. Read the How Is It Calculated section below to learn more.
Usage
The ConversationCompletenessMetric() can be used for end-to-end multi-turn evaluation:
from deepeval.test_case import Turn, ConversationalTestCase
from deepeval.metrics import ConversationCompletenessMetric
from deepeval import evaluate
convo_test_case = ConversationalTestCase(
turns=[Turn(role="...", content="..."), Turn(role="...", content="...")]
)
metric = ConversationCompletenessMetric(threshold=0.5)
# To run metric as a standalone
# metric.measure(convo_test_case)
# print(metric.score, metric.reason)
evaluate(test_cases=[convo_test_case], metrics=[metric])There are SEVEN optional parameters when creating a ConversationCompletenessMetric:
- [Optional]
threshold: a number representing the minimum passing threshold. Can also be set toNoneto run the metric in score-only mode. Defaulted to0.5. - [Optional]
model: a string specifying which of OpenAI's GPT models to use, OR any custom LLM model of typeDeepEvalBaseLLM. Defaulted togpt-5.4. - [Optional]
include_reason: a boolean which when set toTrue, will include a reason for its evaluation score. Defaulted toTrue. - [Optional]
strict_mode: a boolean which when set toTrue, enforces a binary metric score: 1 for perfection, 0 otherwise. It also overrides the current threshold and sets it to 1. Defaulted toFalse. -
[Optional]
async_mode: a boolean which when set toTrue, enables concurrent execution within themeasure()method. Defaulted toTrue. - [Optional]
verbose_mode: a boolean which when set toTrue, prints the intermediate steps used to calculate said metric to the console, as outlined in the How Is It Calculated section. Defaulted toFalse. - [Optional]
flaky: a boolean which when set toTrue, marks the metric as flaky. Defaulted toFalse.
As a standalone
You can also run the ConversationCompletenessMetric on a single test case as a standalone, one-off execution.
...
metric.measure(convo_test_case)
print(metric.score, metric.reason)How Is It Calculated?
The ConversationCompletenessMetric score is calculated according to the following equation:
The ConversationCompletenessMetric assumes that a conversion is only complete if user intentions, such as asking for help to an LLM chatbot, are met by the LLM chatbot.
Hence, the ConversationCompletenessMetric first uses an LLM to extract a list of high level user intentions found in turns (in "user" roles), before using the same LLM to determine whether each intention was met and/or satisfied throughout the conversation by the "assistant".
FAQs
How is Conversation Completeness different from Goal Accuracy?
What does an incomplete conversation look like?
How does the metric decide what the user wanted?
"user" turns, then checks each against the "assistant" turns. The score is satisfied intentions over total intentions.Can I use this as a user-satisfaction proxy?
ConversationCompletenessMetric works well as a proxy for overall satisfaction in chatbot use cases.