Signals
Review scored revenue evidence, confidence, account context, and delivery history used by Funnels and operators.
Signals are account-level revenue moments derived from events, billing context, mappings, account facts, and intelligence. They explain why Prevenue believes an account may be ready to Grow, need a Save path, be likely to Convert, or require Watch-only review.
Signals is an always-visible Data & Intelligence surface. It supports Funnels and account investigation; it does not own the customer journey.
Signal motions
| Motion | Meaning |
|---|---|
| Grow | Expansion, top-up, annual conversion, team expansion, premium feature, or capacity evidence. |
| Save | Churn, downgrade, cancellation, support friction, contraction, or payment-risk evidence. |
| Convert | Signup, trial, checkout, free-to-paid, activation, subscription, lead, or opt-in evidence. |
| Watch | Monitor-only, low-confidence, or incomplete evidence that should not control customer treatment. |
Queue workflow
- Search by account, signal, Funnel, route, or summary.
- Add filters for motion, state, account, route, confidence, created date, owner, or saved list.
- Add columns for evidence count, delivery history, source, account identity, or intelligence context when needed.
- Open a signal in its drawer to inspect the evidence.
- Decide whether it should inform Funnel eligibility, account prioritization, delivery, suppression, or Watch-only investigation.
Signal detail
A signal can include:
- Motion, type, priority, confidence, and state.
- Estimated movement or MRR context.
- Deterministic reason and recommended handling.
- Account intelligence and prediction-readiness caveats.
- Evidence rows, rollups, and timeline.
- The Funnels and Opportunities that consumed it.
- Routing and delivery history.
- A safe payload preview for downstream delivery.
Confidence is evidence strength, not the probability that the customer will expand, churn, convert, or remain retained.
Using Signals in Funnels
A Funnel can use an explicit signal condition as an entry or eligibility input. Preserve the Signal ID, version, confidence, freshness, and evidence reference used by the decision.
Low-confidence, stale, or missing Signals should fall back to deterministic eligibility or no render. Save evidence should suppress or soften conflicting Grow/Convert treatment according to the published Funnel policy.
Delivery
Route a Signal or Funnel follow-up only when the receiving team or system has enough context to act. Provider configuration and delivery diagnostics live in Settings > Integrations and Integration Activity.