On every New Lead card, a Call button that opens the phone with the lead's number staged and dials it. The stage advances to Contacted when the call connects, stamped by the telephony webhook. Where a builder has no in-app phone — a shop that texts through GoHighLevel — the manual Log Contact button remains, because nothing on our side can ever observe their call. Log Contact stamps the first-contact time on a first-contact-wins basis.
Also called: log contact button · speed to lead · did the rep actually call · click to call from the board
- 1The Call button appears only when the builder has the phone module and the lead has a dialable number
- 2It uses the same call path as the card modal, so one lead is dialled one way wherever you start
- 3Log Contact routes through the shared stage-move path: checklist reset, entry time, next action cleared, audit row
- 4The first-contact time is only stamped when it is still empty, so a later Log Contact cannot reset the clock the follow-up engine measures against
The New Lead card's main button moved the deal to Contacted and did nothing else — a button that asserted a phone call had happened without one happening, which meant speed-to-lead numbers were measuring clicks. It now opens the phone with the lead's number staged and dials, and the stage moves when the call actually connects. Accounts that route their calls through a different phone system keep their own path, since there is no connection event to listen for.
- A button that asserts work instead of doing it
- Speed-to-lead metrics built on self-reported clicks
- A later click resetting the first-contact clock
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 →