Manage your leads

The Leads page is the contact-by-contact view of your dialer: every person a CRM workflow ever pushed into GodSetter, how many times they were called, how the last call ended — and, when a call did not go out, why. It is the page that answers "what happened to this person", where the dispatch article answers "what happens to leads in general".

Times are shown in the Europe/Rome time zone, except the next-retry time, which is shown in the time zone of the calling window that governs it.

The list

Leads are ordered by most recently updated, 25 per page. The columns are:

Filters and pagination

Five pills filter the list: All, Blocked, Booked, Callback, No answer. Blocked filters on the Do-Not-Call flag; the other three match the lead's last outcome, not any call in their history. Each pill carries a real count over all your leads.

Pagination works like everywhere else — 1–25 of 340, with Previous page and Next page — and both the filter and the page live in the URL.

The "Skipped" badge

When the last thing that happened to a lead was a skip rather than a call, the Last outcome cell shows an amber Skipped: … badge with the exact reason instead of a stale outcome. There are ten reasons:

The badge is cleared the moment the lead is actually dispatched, so what you see is always the last thing that happened — a skip from yesterday never shadows a call placed this morning. The same reason, with its timestamp, appears as Last skip on the lead's own page.

Inside a lead

The lead page opens with the name, the phone number (with Copy number), the last outcome and a Blocked or Active badge.

The Profile card lists the record as GodSetter holds it: Name, Phone, Email, GHL contact ID, Client, Timezone, Created, Retries and Last skip. The GHL contact ID is the link back to the contact in your CRM. The Timezone is the contact's own zone — the one an agent whose calling window runs in contact mode dials on, so it is also the answer to "why was this lead called at that hour?".

Retries: where the lead sits in the plan

The Retries row reads either attempt 2 of 6 · next 12 Sep 2026, 10:30 or plan exhausted (6 of 6). It is computed from the retry plan of the agent that made the last outbound call, and the time is expressed in the time zone of the window that governs that agent.

A dash means no retry will ever be scheduled for this lead as things stand. The page applies exactly the eligibility the dialer applies at the end of a call: retries switched on for that agent, the agent active, the client active, the lead not blocked, and the last outcome among the ones the agent retries. If you expected a redial and see a dash, one of those five is the reason — see Retry cadence, callbacks and transfer.

Call history and last call summary

Call history lists every call for this lead — Date, Dir., Outcome, Duration — with a button that opens the full call detail. A lead that has never been called reads No calls for this lead yet.

When the last call produced a summary, a Last call summary card shows it. That is the same text the agent carries into the next conversation, so it is worth reading before you judge a redial.

Consent and Do Not Call

The Consent card shows the proof on file — Form ID and Submitted at — or No consent proof on file. In strict mode a lead without valid proof is never called; see Consent, strict mode and proof.

The Do Not Call card shows the state and a single button: Block lead or Unblock lead. Blocking is permanent until you undo it — the dialer will never call a blocked lead, and the block is re-checked right before dialing. Unblocking is there for the mistakes: a lead auto-blocked from a misread call can be brought back. Both actions are written to the audit log. The full rules are in Do Not Call: blocking and unblocking.

Next

• Read the call log
• How outbound dispatch works
• Calls are not firing — full checklist