What is a customer signal?
A customer signal is a single observable indication of what a customer needs, feels, or intends.
Examples: one survey response, one support ticket, one remark on a call, one usage pattern.
Signals are the raw input to customer intelligence. Individually they are weak: ambiguous, often contradictory, and heavily influenced by whatever happened to the customer that morning. Their value shows up in aggregate and in context.
Why it matters
Teams overreact to single signals, particularly loud ones from large accounts. The fix is to hold a signal until it either repeats across unrelated people or fails to. A signal that never repeats was noise.
Example
One enterprise customer asks for a Gantt view on a Thursday call. That is a signal. Whether it becomes a roadmap item depends on whether four other customers, in different segments, have asked for something that solves the same underlying problem, which may not be a Gantt view at all.
In UpSight
UpSight extracts each signal as an evidence row with its source intact, then groups the rows into themes. A theme shows its evidence count and its count of distinct people, and lists who they are, so you can tell five people from one person five times.
Related terms
FAQ
- What's the difference between a signal and evidence?
- A signal is the raw observation. It becomes evidence when it is captured verbatim, attributed to a person, and dated so it can be checked later.
- How many signals make a pattern?
- There is no fixed number, but the useful test is independence: five signals from five unrelated customers mean far more than fifteen from one account.
- Where do customer signals come from?
- Sales calls, support tickets, surveys, interviews, reviews, community posts, churn reasons, and product usage.