The morning ritual ends when the last row in the queue is hung up and filed. What happens between “dial the queue” and “last row hung up” is what this post is about — specifically, how to work through a list one call at a time without losing the row you just called, and without breaking the rhythm that keeps you on the phone for two hours without thinking about it.

The dialer in Leadline is not a separate piece of software you log into. It is a tab in the same workspace where your list lives. The list and the dialer are the same surface, so the row you see on screen when the phone rings is the row you were looking at a second ago.

What the queue shows

Open a filtered list — say, every plumber in the 94110 zip code with stage “New” — and click Dial queue. The list is now a queue: lead on top, queue below.

The lead on top is who you are about to call. The queue below is who you will call next. They are the same rows in the same table; the dialer just gives them a different visual weight.

You can re-order the queue by dragging the rows. You can pin one lead to the top. You can remove a lead from the queue without removing them from the list. The dialer does not own the list — the list owns the dialer.

What happens when you call

Click the phone icon next to the lead’s number. The dialer places the call in your browser over WebRTC — your browser is the phone. You hear ringing. The lead’s name and number are on the screen. A timer starts the moment the call connects.

If the lead picks up, you talk. If they don’t, the dialer files the outcome as “no answer” and advances to the next lead. If you get voicemail, same thing. There is no setup — the dialer knows what to do with each outcome.

The recording indicator is on by default. Recordings are kept with the lead, not in a separate audio library. The row and the call are bound. If you ever come back to that lead, the call is there.

How to file an outcome

When the call ends — they hung up, you hung up, the dialer hung up for you — the outcome form appears on screen. It is a small panel, not a popup, so it does not break the rhythm. Three fields, fast to fill:

Outcome. What happened: connected, voicemail, no answer, wrong number, do-not-call, sale, follow-up. These are the same outcomes the workspace ships with; you can rename them in settings.
Notes. Whatever you learned on the call. The notes are saved against the lead, not against the call — they show up on the lead’s detail view and in any saved view that includes the Notes column.
Next step. Optional. A date and a label for what you or someone else should do next (“call back Tuesday”, “send proposal”, “qualify for partner program”). This creates a follow-up task that surfaces in the queue on the date you set.

Hit save. The lead moves to the next stage you assigned to that outcome, the next lead rises to the top of the queue, and the dialer is ready for the next call. The whole sequence is two seconds if the outcome is “no answer”, ten seconds if you wrote a paragraph of notes.

Why this matters

The thing the dialer is actually solving is not “place calls faster”. Plausible faster: you could open ten tabs and dial them in parallel and feel busy. The thing it is solving is the row stays attached to the call. When you come back to that plumber tomorrow, or next week, or when the partner program manager asks what happened with them, the call is right there. The notes are right there. The next-step task is right there.

This is what the workflow does not do that spreadsheets and a separate dialer do: it does not let the call and the row drift apart. They live in the same place from the moment the row is saved to the moment the outcome is filed. There is no copy-paste, no second login, no CSV export to a CRM, no “let me check my notes”.

What this is not

A few honest things:

The dialer is not a predictive dialer. It does not call multiple lines at once and patch in the agent who connects. One call at a time. You can skip a row, but you can’t dial five rows in parallel.
The dialer is not a spam engine. There is no list-blast mode, no ringless voicemail, no auto-dial-and-hang-up. The phone rings, you or the lead picks up, you talk. If you want a system that pretends a real human is calling, this is not it.
The dialer is not magic at compliance. Your carrier handles DNC suppression at the network level if you turn it on. Scrubbing the list against state DNC lists is on you. We do not pretend otherwise.

When to skip a row

Sometimes the right move is to not call. The dialer knows this:

Do-not-call. If a lead asks not to be called again, mark them DNC and the dialer will never put them back in a queue. This applies across the workspace, not just your queue. One person adds it; everyone respects it.
Wrong number. Sometimes the number is disconnected or belongs to someone else. Mark it wrong number and the lead moves to a holding stage. Someone else can fix the number and put them back in the rotation.
Not a fit. If the lead is a restaurant and you sell plumbing software, the conversation is short. Mark “not a fit” with a one-line note explaining what they actually do, so the next person who looks at the lead understands why.

The dialer advances past these as fast as you can click. The point is to spend your time on the leads that are a fit, not to grind through every row in the list.

Where to go next

If you have a list and a calling credit, open the list, click Dial queue, start at the top. The dialer does not need configuration — it picks up where the list leaves off.

If you want to read more first:

Saved views — turn the list you’re dialing into a URL a colleague can open to see the same filtered rows.
Harvest a neighbourhood — if you don’t have a list yet, this is where to start.
Solo vs Team — if you’re calling solo and wondering whether to bring a partner in, this is the decision guide.

That’s the dialer. Call, file, next. Repeat until the queue is empty, then sweep another region and refill it.