Lesson 09 · Understand your customers

What are signals?

What BuildBetter pulls out of your data, and how to tune it.

1 min 13 s5 stepsLesson 3 of 8 in Understand your customers

You’ll be able to

  • Spot the signals on any call
  • Choose what BuildBetter looks for
  • Sort signals by product area

Read the docs

Synced from docs.buildbetter.ai

The help pages for this lesson, kept up to date. Read them here without leaving the lesson.

Understanding Signals
Automatically extract and analyze insights from all your customer interactions
Automatic Signal Extraction
How BuildBetter automatically identifies and extracts signals from your conversations and data
Settings Comprehensive Guide
Complete guide to configuring BuildBetter for your organization
Taxonomy Overview
Organize and categorize your signals with AI-powered product taxonomy

Transcript

A signal is one specific thing a customer said, or your team decided.

A feature request. A bug. A complaint. A decision with an owner.

BuildBetter pulls them out of every call, ticket and Slack thread. Each one links to the moment it happened, so anyone can check it.

You choose what it looks for. Open Settings, then AI Labeling, then Signal Types.

Under Default signals, turn types on or off for Product, Meetings and Company.

Or add your own. Click New signal and describe it, like mentions a competitor by name.

Then give signals a structure. Back in AI Labeling, click Generate from Prompt, then Use Custom Context.

Click Generate, and BuildBetter builds a product taxonomy. Every signal gets sorted into the product area it's about.

Next up, find insights with Signals.