Leads

The Leads tab is the top of the funnel. Leads are added in bulk, then worked one at a time.

Search by name, handle, or email to find one fast.

Every lead records the channel it came from: Instagram, LinkedIn, Facebook, X, TikTok, YouTube, a community, a referral, an event, inbound, or other. What the app asks for changes with the channel, because a handle identifies someone on some of them, a profile link on others, and neither on the ones that happen offline.

It also asks where the lead was found, and that answer is the most useful thing the list records: it is how a workspace learns which targets, groups or events actually produce booked calls.

The setter sends the message themselves. The app does not send it for you.

Two independent labels track a lead.

• Is it worth working? Unreviewed, Qualified, or Not a fit.
• Where has the conversation got to? Not sent, Sent, No reply, Follow up, Interested, Not interested, Booked, Needs rebooking, or Abandoned.

When a lead turns into a real conversation it is promoted into a contact, either linked to a record you already have in GoHighLevel or created fresh.

From there it lives on the Contacts side, and the setter who sourced it is kept as a follower.

A lead added one at a time is assigned to whoever added it, since typing somebody's details in is how you say you are working them. A pasted or imported list is the opposite and stays unassigned, so it lands in the pool for anyone to claim.

A prospect who books and then never joins is the setter's work to redo, but the closer is the one who finds out. So the closer can send it straight back.

The control is on the contact, not on the lead. A contact that came from a lead carries a Setter handoff card naming who sourced them and when the meeting is set for, and while it is still booked that card offers Send back.

Pick what happened, and add a note if there is more to say:

• No-show. They never joined the call.
• Cancelled. They called it off ahead of time.
• Not the right fit. They turned up, but they should not have been booked.

The lead reopens as Needs rebooking and comes due in the setter's queue today, dated by their timezone rather than the closer's, so it never sits invisible until tomorrow arrives for them. It loses its meeting date and counts as live pipeline again.

Everybody except a setter can send a lead back, which is wider than most controls here on purpose: whoever was in the room, or was not, is the person who knows. A setter is excluded because the lead is already theirs to work, so they would only be handing it to themselves.

Every member can see the whole lead list. Claiming a lead does not hide it. Claiming only restricts who may reassign it.

Owner, admin and manager can reassign a lead and change the outbound settings: the daily target, the backlog threshold that pauses sourcing, the targeting, and the tone of the message.

Those live under Settings › Sales.