track_prospect
Log a signal from a prospect and update their temperature.
`signal` examples: booked_demo, asked_pricing, viewed_content, replied,
not_interested, too_expensive, no_time, competitor, ghosted_3_days,
ghosted_7_days, opted_out (they asked not to be contacted: ends the
relationship). Creates the prospect if new.
When you have the prospect's actual reply text, use `record_reply`
instead: it reads the reply and updates temperature, mode, objections and
do-not-contact for you.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"handle": "<handle>",
"channel": "<channel>",
"signal": "<signal>"
},
"name": "track_prospect"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | The prospect's handle or address on that channel, such as a Reddit username or an email address. | |
| signal | Yes | What happened: booked_demo, asked_pricing, viewed_content, clicked_link, replied, not_interested, too_expensive, no_time, competitor, not_decision_maker, bad_timing, ghosted_3_days, ghosted_7_days or opted_out. | |
| channel | Yes | Where you talk to them, such as "reddit", "twitter" or "email". The handle and channel together identify the prospect. | |
| mission_id | No | Optional. The mission they came from, from get_missions. | |
| product_id | No | Optional. The product they are a prospect for, from get_products. |