Your first question
Before you start#
- One source of customer signal you already have, such as call recordings, support tickets or CRM notes
- A question with a decision attached to it, not a curiosity
- Someone who knows the answer well enough to catch a wrong one
Start with the source that holds the most unstructured truth, usually calls or support tickets. One source is enough for a first answer; the reasoning gets stronger as more connect. See Connect your sources.
Poth models customers, accounts and segments before answering. This runs once on ingestion and continues in the background as new signal arrives.
"What is driving churn in mid-market" beats "summarize last month's feedback." The first has an owner and a next step; the second produces a summary nobody acts on. See Ask Poth a question.
Open the trail behind the top finding. Check the segment, the counts and which competing explanations were rejected. If the reasoning is wrong, this is where you will see it. See Read the evidence.
When evidence runs out, Poth proposes targeted questions to close the gap. Approving them is what turns a 60 percent answer into a validated one. See Adaptive surveys.
What a good first result looks like#
A ranked list of findings, each with counts, an affected segment and a recommended action. Something like: onboarding friction, 847 mentions, SMB under 50 seats, day-3 activation nudge.
If the top finding is something your team already knew, look at rank two and three. The value of a customer brain shows up in the patterns nobody had the full view to see.
Next#
- Act on an insight turns a validated finding into an owned decision.
- Who uses Poth shows the questions each team brings first.