A lifecycle row written per successfully assigned lead, stamped with the receiving rep and dated at the moment of assignment. This makes engine-distributed leads visible to the per-rep conversion and speed denominators that overflow ranking depends on.
Also called: rep performance · conversion by rep · speed to lead by rep · self optimizing routing
- 1Imported leads emit their creation record with no owner, because they were unassigned at import
- 2The engine appends an owner-stamped creation row per winning assignment
- 3The event time is the assignment time, so a rep's speed clock starts when they got the lead, not when it was imported
- 4The row id is derived from the lead so there is at most one engine row per lead ever
The rep score that decides who gets the next lead could not see the leads it had routed, because engine assignments were not written as events it read — the system optimising distribution was blind to its own output. Every routed lead now writes an owner-stamped record. The kind of record matters and was chosen carefully: it is the only one that feeds a rep's lead count without faking speed-to-lead, since any move out of New Lead is otherwise treated as first contact having happened.
- Distributed leads invisible to rep performance measurement
- Speed to lead measured from import date rather than assignment
- Routing decisions made on incomplete performance data
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →