
A preview dialer shows the rep a contact's record first and dials only when the rep decides to call. Sometimes the rep clicks, sometimes a short countdown places the call. You trade speed for preparation, which pays off on high-value accounts and complex personas and costs you on volume lists.
The useful question is not whether to preview. It is what to preview, for how long, and who should do the previewing: the rep or the software.
The skip option is the point. A preview that always ends in a call is a delay, not a decision. If your reps never skip, the preview step is not doing anything.
Two settings decide whether preview helps or hurts. The first is a maximum preview time: if the countdown is 30 seconds, reps will use 30 seconds. We would start at 10 to 15. The second is the skip rate. Managers should look at it weekly, because a team that skips nothing is not previewing, and a team that skips everything has a list problem and not a dialer problem.
Preview is the right mode when one conversation is worth more than the time spent preparing it:
A fair test is to compare two groups on the same list: reps who preview and reps who do not, over two weeks, with the same hours. Compare conversations per hour and meetings per conversation separately. Preview usually costs you the first and has to earn it back in the second.
The cost is easy to compute. Our benchmark of 1,000,000 B2B cold calls in France shows an 11.3% average connect rate. Out of 100 dials, about 11 reach the person you wanted and about 89 do not.
Now take a 45-second preview before every dial. That is 75 minutes of preparation to reach about 11 people. Most of that preparation goes to calls that end in voicemail or a switchboard.
The preparation matters most on the calls that connect, and you do not know in advance which ones those are. That is the structural weakness of manual preview on cold lists, and why it belongs to small, valuable lists and not to a 400-contact call block.
If a preview takes longer than 10 seconds, nobody does it twice. Five things earn their place on the screen:
Our 60-second pre-call framework goes deeper for accounts that justify it.
Look at that list again. Every item is data that already exists somewhere: the CRM, the website, the call history, the calendar of a persona. The preview is a data-assembly problem, and a rep should not solve it by hand 60 times a day.
Reps use only about 20% of the signals already in their CRM, and 50% of Sonik's pipeline comes from signals that were already there. Two changes remove most of the manual work. First, signals decide the order of the list, so the contact with a reason to be called comes first. Second, AI call prep puts the five items above on one card, so the "preview" is a ten-second read while the line rings.
You keep what preview was good at, a rep who knows why they are calling, and lose what it was bad at, the minutes spent assembling context.
We treat preview as a property of the list, not of the tool. A list of 30 named accounts deserves a slow, careful pass. A list of 400 contacts with fresh signals deserves a fast one, with the prep card ready when a human picks up.
The aim of our dialer is 5x more conversations with the right contacts, so the context has to arrive with the call and not before it. If you want a preview step for your top accounts, keep it. Just keep it short and give it a skip.
Preview dialing is worth it when a call is worth more than the preparation. This week, pick your 10 best accounts, run the five-point preview in 10 seconds each, and compare their connect and meeting rates with your normal dials. If the gap is small, your preview is too slow. If it is large, automate it.