Lesson 56 · Settings and admin
Teach BuildBetter your own signals
Define a signal, check the cost, preview it, read the runs.
You’ll be able to
- Define a signal in your own words
- See what it will cost before it runs
- Preview it and read every run
Read the docs
Synced from docs.buildbetter.aiThe help pages for this lesson, kept up to date. Read them here without leaving the lesson.
Transcript
Custom signals teach BuildBetter to catch something specific to your team, in every call.
Open Settings, then AI Labeling. Under Labeling tools, open Signal Types. Your custom signals sit above the defaults.
Click New signal. Give it a title, and describe exactly what counts.
Add signal knowledge for extra context. Then pick the sources and the boundary, like calls with external people only.
The estimate shows how many runs a day to expect. Each completed run uses eight credits.
Leave Active on to run it after every new extraction, then click Create.
To test a signal on one call first, click Preview, pick a recent call, and run the preview.
From the menu, View runs lists every run. Open one to read what it found, how confident it is, and the quotes behind it.
Next up, Knowledge Gaps.
