How do I diagnose why a metric dropped with iDBQuery?

When a key metric falls, the urgent question is why, and the answer usually hides in a slice of the data. iDBQuery's Analyst agent runs that investigation for you: - Ask 'Why did revenue fall 12% last month?' - The agent decomposes the drop by region, product, segment, channel and new-versus-returning, running a series of queries and using each result to decide the next. - It returns a cited narrative that names the specific segments responsible, not just a chart.

A worked example: after a dip, a founder asks 'What caused the drop in signups?' The agent finds that one acquisition channel collapsed while others held, checks whether it was volume or conversion, and reports the cited cause with the rows behind it.

The differentiator is that this is a genuine investigation, not a single query. The agent forms and tests hypotheses the way an analyst would, then shows its work, so every figure traces to source rows and you can trust the conclusion before you act on it. Because iDBQuery spans sources, the investigation can cross systems, for example linking a revenue drop to a shipping delay in operations data. You can start with the agent for the 'why,' then keep drilling in conversation to pressure-test what it found.