Signals

Understand what signals are and how ProductBet captures them from your connected tools.

What are signals?

Signals are individual pieces of product intelligence captured from your connected tools. Every support conversation, feature request, deal outcome, cancellation reason, or Slack message becomes a signal in ProductBet.

You never create signals manually. They flow in automatically from your integrations.

Where signals come from

Signals are captured from every tool you connect:

  • Intercom - customer support conversations
  • Slack - messages from monitored channels
  • Productboard - customer feedback notes and feature requests
  • Salesforce - won/lost deal reasons from closed opportunities
  • Stripe - subscription cancellation reasons and payment signals

The more integrations you connect, the richer your signal data becomes.

What a signal captures

Each signal extracts the intention behind customer feedback, not just the raw text. This means ProductBet understands what the customer is asking for, even when they describe it differently across channels.

Every signal includes:

  • Source - which integration it came from, with a link back to the original conversation
  • Intent - what the customer is trying to accomplish
  • Friction - what's blocking them
  • Expected outcome - what success looks like from the customer's perspective
  • Label - the type of feedback (bug, missing capability, UX friction, etc.)

How signals connect to opportunities

When the same need appears across multiple signals from different sources, ProductBet groups them together. For example, if three Intercom conversations, two Slack messages, and a Productboard note all point to the same product gap, they strengthen the evidence for a single opportunity.

This cross-source pattern matching is what makes ProductBet powerful. A single feature request is easy to ignore. The same request from five different customers across three different channels is hard to dismiss.

Signal labels

Each signal is automatically categorized:

LabelWhat it means
BugSomething is broken or not working as expected
UX frictionThe feature exists but is hard or confusing to use
Missing capabilityCustomers want something that doesn't exist yet
IntegrationRequests for connecting with other tools
Strategic expansionIdeas for entering new markets or product areas

Tips

  • You don't need to tag, label, or organize signals. ProductBet handles this automatically
  • Signals from different sources that point to the same need are grouped together
  • Each signal links back to its original source, so you can always read the full context
  • The strength of an opportunity depends on how many signals support it, especially from diverse sources