Every shipped change to the LeadGrade inbound lead agent.
Point anything that can POST JSON at your endpoint — Webflow, Framer, Typeform, HubSpot forms, your own site.
A payload with no readable email comes back 422 naming the keys it did see, instead of dropping a lead quietly. A lead lost at the door is the worst failure this product can have.
Approved writes are deferred, and the dispatcher selects on the send-after column — so a row inside its window is not picked up at all rather than picked up and filtered.
After it goes, the value it replaced is stored, so putting it back is one tap and the same window again.
A CRM field that already holds a value is never written. The refusal is recorded with the value it protected and shown in the queue, rather than being a silent no-op nobody can audit.
There is no setting that turns it off. Adding one would be adding the --force this product's own landing page promises does not exist.
The queue no longer renders a bare number. Each lead carries the rules that produced its score — the value each one read and what that value was worth — so a ranking can be checked, argued with, and changed.
A score with an empty reason list is not a state the scoring module can produce: the no-signal case has its own rule and its own line.
WHEN A RULE CHANGES
LeadGrade scores every inbound lead overnight and ranks the queue highest first. The scoring rules and the rails it will write back to both change. Leave an address and LeadGrade writes when one does.
