---
title: Signals in People
description: For each of your people, Venom reads your notes, interactions and deals and gives a call (engage, progress, hold or drop), strengths, weaknesses and a bar per indicator. It runs on a schedule with the gear you choose, and records "insufficient data" when too little is written.
section: cloud
order: 172
audience: [user, operator]
sources: ["services/nodejs-cloud/lib/people/signals/index.ts", "services/nodejs-cloud/lib/people/signals/model.ts", "services/nodejs-cloud/lib/people/tools-signals.ts", "services/nodejs-cloud/app/api/cron/people-signals/route.ts", "services/nodejs-cloud/components/people/SignalsCard.tsx", "services/nodejs-cloud/components/people/SignalsSettings.tsx", "services/nodejs-cloud/migrations/0364_people_signals.sql"]
features: [cloud.page-people, cloud.api-cron, cloud.migrations]
---

Signals answers one question about each person you know: is this worth more of your time? It reads what you wrote about
them and puts the answer on their page as a card: a call, the reasons, and eight bars.

It is a signal, not a verdict. It is made only from your own notes, so it is as one-sided as they are, and it scores
what a person did and said, never who they are.

## What the card shows

- **The call**: one of
  - **Engage**: worth starting or deepening contact.
  - **Progress**: something concrete is under way and the next step is clear.
  - **Hold**: wait for a named thing before spending more time.
  - **Drop**: stop investing.
  - **Insufficient data**: not enough is written to say.
- **Why**, in one or two sentences, with the next step or the thing to wait for.
- **Eight bars**, each from 0 to 100. 50 is neutral and higher is better for you. A bar is empty, with "No evidence",
  when your notes say nothing about it.

| Bar | What it measures |
|---|---|
| Responsiveness | how quickly and reliably they reply and turn up |
| Follow-through | whether they do what they said they would |
| Clarity | how concrete they are about the problem, scope and what they want |
| Authority | whether they can decide, or reach the person who does |
| Budget | evidence of money to spend and willingness to pay |
| Fit | how well what they need matches what you offer |
| Trust | whether what they say holds up against what others say and what happened |
| Momentum | whether things are moving forward lately, or stalling |

- **Strengths** and **weaknesses**, up to five each, each resting on something you wrote.
- **What was read** (how many interactions, how many characters of notes, how many deals), when, and with which model.
- **Assess now**, to run it for this person without waiting.

On a phone and in the installed app the card is one column.

## What it reads

For one person: your notes on them, how you met, your latest 15 interactions, and the deals they are on that you can
see. It does not read their handles, tags, photos or anything another member wrote about them.

## Insufficient data

A person needs at least two pieces of evidence (you can change the number). Each of these counts as one:

- an interaction that says what was discussed (a line such as "Connected on LinkedIn" does not count),
- notes of a paragraph or more,
- a deal the person is on.

A person below that is recorded as **Insufficient data**, with the counts, and no model is called. So a large import of
contacts you have never spoken to costs nothing. The model can also answer insufficient data itself, and a call with no
bar under it is always shown as insufficient data.

## When it runs

Nobody has to ask. Every 10 minutes Venom looks at the people who are due:

- people it has never looked at,
- people whose entry, interactions or deals changed since the last look,
- people whose result is older than 30 days (momentum goes stale),
- people whose last attempt failed, six hours later.

A change that alters nothing the model would read is not sent again. People on a deal go first.

## Settings

**People → Settings → Signals.** Owners and admins change them. Signals is off until one of them turns it on.

| Setting | What it does | Default |
|---|---|---|
| **Gear** | Which [gear](/docs/cloud/console-gears.md) answers: any of your organisation's gears, or one of venom's built-ins (such as `qwen` or `china`) unless your organisation allows only its own. A gear that cannot run now is shown greyed out with the reason (no provider key for its model, and which provider; its daemon is offline; its wildcard matches nothing served). The page shows the model the chosen gear (or **Org default**, named with the gear it is now) runs on. | the organisation's default gear |
| **Daily cap (USD)** | Signals' own spend a day. It also stops at People's daily AI cap. | $0.50 |
| **People per pass** | How many people one pass sends to the model. | 20 |
| **Assess again after (days)** | Re-run a person even when nothing changed. | 30 |
| **Minimum evidence** | Pieces of evidence a person needs. | 2 |

Every call goes through your organisation's own gear and is booked like any other request, so it shows on Requests
(task `people-signals`) and on the spend pages.

A built-in gear runs on the model your provider keys or daemons serve for it, the same one a quick chat would use. When the
chosen gear cannot run (its key was removed, its daemon went offline), the gear stays selected and the page and
`people_signalsetting_get` say why; passes wait with that reason instead of moving to another gear. `people_signalsetting_get`
returns every gear in `gears` with `available`, `model`, and `why` and `reason` for one that cannot run, and
`people_signalsetting_set` accepts exactly those names.

Turning Signals off stops the passes. What was already written stays on each person's page, marked as the last result.

## Who sees it

Only the member who knows the person, like the notes it is made from. A colleague who can see a shared person does not
see your signals for them.

## For agents

The workspace MCP server has `people_signal_get` (a person's signals), `people_signal_run` (assess one now),
`people_signalsetting_get` and `people_signalsetting_set`, with REST twins under `/api/v1/people/{person}/signals` and
`/api/v1/people/signals/setting`. See [People for agents](/docs/cloud/people-mcp).

## Self-hosted installs

Signals makes no outbound call of its own. It uses whatever model your gear routes to, which can be a local one.
