lead:reply
lead family
Sends a new lead the first reply from the caller's own workspace, at once: one transactional email through message:send, with the workspace's booking link when it has a bookable service, and records the seconds from the capture to the reply on the lead (meta.lead.firstReply) for the monthly report. One reply per address per workspace in 14 days (the reservation row rides agent_events_warm's 14-day purge); at most 100 first replies a UTC day per workspace and 3 a UTC day per address across every workspace — every bound keys on the inbox (lower-cased, +tag dropped, gmail dots folded); the email says a stranger can ignore it and carries an unsubscribe link signed for the inbox, so following it blocks every spelling; a canary lead, a suppressed or a declined address gets nothing and nothing is recorded
- Effect
- ask
- Awaits an outcome — the call returns the response below.
- Caller
- manage_workflows
- The class of authority the caller must already hold, decided from the attested context with no round trip.
- Cost
- free
- What one call costs, so you can budget before acting.
- Reversible
- no
- This cannot be undone. Dry-run it first where the contract allows.
- Idempotent
- yes
- Safe to retry as-is.
- Version
- 1.0.0
- Pin this to keep a contract stable; additive bumps never break callers.