Understand why Fin behaved a certain way in a conversation, and how to fix it. Fin Operator reads full transcripts — including Fin's thoughts, traces, and the content sources it used — then diagnoses what happened and helps you resolve the root cause.
What you can investigate
Why a specific answer was given — which content sources were used, how Fin reasoned about them, and whether the right information was available.
Why Fin behaved a certain way — trace the decision path that led to a specific response, escalation, or resolution — including which content, guidance rules, and procedures influenced the outcome.
Why a procedure step executed a certain way — see exactly which steps ran, in what order, with what data, and why a step was skipped or took an unexpected branch.
Example prompts
"Why did Fin give the wrong answer in this conversation?" (paste the conversation link or ID)
"This conversation was escalated — why?"
"Why did step 3 get skipped in this procedure?"
How Fin Operator investigates — and fixes
Fin Operator pulls the data it needs, cross-references your Fin configuration, and proposes fixes — all in one flow:
Fetches the full conversation — including Fin's reasoning traces, the content sources it referenced, and any tool calls it made.
Looks up your Fin configuration — checks the relevant content, guidance rules, and procedure definitions to understand what Fin was working with.
Identifies the root cause — pinpoints whether the issue is in your content, guidance, procedures, or a combination.
Proposes a fix — depending on the root cause, suggests changes to your knowledge base, procedures, or guidance rules. You review and approve in the same conversation.
For procedure issues, Fin Operator fetches the execution trace showing exactly which steps ran, in what order, and with what data — then cross-references against the procedure definition to pinpoint the root cause.
Tips
Share specific conversation links or IDs for targeted debugging. The more specific you are, the faster Fin Operator can diagnose the issue.
Describe the symptom, not the investigation for pattern analysis. "Customers asking about returns are getting escalated" is better than "Look at escalation triggers for return-related conversations." Let Fin Operator determine the right investigation path.
Start with a single conversation if you're unsure what's going wrong. Once Fin Operator identifies a pattern, you can ask it to check whether the same issue appears across more conversations.
Fin Operator verifies claims against actual data. If you say "step 3 was skipped," it checks whether that actually happened before building an explanation.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts