When the ambiguity is mostly interpretive
Start with reporting explanation when the real question is about understanding the definition, scope, or posture of a report or export without assuming broken behavior.
This is different from assuming the product is malfunctioning or assuming a thin reporting surface quietly promises stronger analytics maturity than has been claimed.
When the ambiguity belongs somewhere else
Use support when the question is blocked or consequence-heavy, known-limits interpretation when the real issue is a present product boundary, and product-gap routing when the confusion points to a missing capability or suspected broken behavior.
The safest first route is the one that preserves the real reporting signal without forcing more certainty than you actually have.