Outbound Audit: 12 Questions to Evaluate Your Prospecting

Outbound Audit: 12 Questions to Evaluate Your Prospecting

An outbound audit is an afternoon with the data and twelve questions, in four layers: the list, the session, the conversation and the system. Each question has a number you can pull from the dialer or the CRM and a benchmark to compare it with, from our analysis of 1,000,000 B2B cold calls in France. Teams that run it quarterly find their leak in the first layer most of the time, and it is rarely where the sales deck says.

Layer 1: the list

1. What share of your numbers are verified mobiles?

Pull last month's dials and split by number type. Mobiles pick up; switchboards screen. If less than 60% of dials went to a mobile verified in the last 90 days, the list is the problem and nothing downstream will fix it. Enrichment waterfalls and verification are the lever; we described them in waterfall enrichment for mobile coverage in Europe.

2. What share of the list came from a signal?

Contacts with a trigger (job change, website visit, closed-lost past renewal, dormant lead with activity) versus contacts from a filter export. 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. If under a third of your dials carry a signal, the CRM is holding pipeline you are not calling.

3. How many contacts were dialed more than three times without an answer?

Most connects happen within the first three attempts in our experience. A list with many contacts at attempt six is a list that needs resting and re-enriching, and it is burning your caller ID.

Layer 2: the session

4. What is your connect rate, by slot?

The benchmark is 11.3% average, 15.8% at 4pm, 14% at 10am, 9.8% at 8am. If your 4pm is below your 10am, something is wrong with the list or the personas in that block. If every slot is under 8%, see question 1.

5. How many conversations per rep per day?

Our north star is 20. Most teams without a dialer sit at 4 to 8, and a parallel dialer gives around 5x more in our experience. Count conversations, not dials: dials are an input and they hide the list quality.

6. What share of the good slots is actually spent calling?

Open the calendars. If 10am and 4pm are full of internal meetings, the team is calling at 9.8%-connect-rate hours by design. This is the cheapest fix in the audit.

Layer 3: the conversation

7. How do reps open?

Listen to ten calls per rep. In our benchmark 65% of reps open by explaining what they sell; trigger-based openers reach a 7 to 10% meeting rate against 2 to 3% for pitch-first. If most openers are pitches, the meeting rate ceiling is 3% whatever the volume.

8. What happens on the first objection?

Same ten calls. Does the rep answer, or ask "What do you mean?" first? The question lifts conversion by 197% in our data. Count how many reps do it. Usually it is one, and that rep has the best numbers.

9. What is the meeting rate per conversation?

Meetings booked divided by conversations. Benchmark: 7 to 10% with trigger openers, 2 to 3% without. This number, times the conversations from question 5, is your pipeline. If it is low with good openers, look at the endings: calls that finish without a date or a reason. We covered them in how to end a cold call.

Layer 4: the system

10. What share of calls are logged in the CRM, with a disposition?

Compare the dialer's call count with the CRM's. A gap above 10% means callbacks, opt-outs and not-nows are being lost. Free-text notes do not count; a disposition the dialer can act on does.

11. How many dated callbacks happened on their date?

Pull every "call me in [month]" from the last two quarters and check whether the call happened. In our experience most teams are under half. Those callbacks are the warmest list you own: a known contact reaches around 10% success against 1.5% for a cold open.

12. What does the Monday review look at?

If it looks at dials, the team will produce dials. If it looks at conversations per day, meeting rate per conversation, and the two conversation habits from questions 7 and 8, the team will produce meetings. The review is the system; everything else follows it.

How to score it

Do not build a weighted index. Mark each question green, amber or red against the benchmark, and fix the reds in layer order: list before session, session before conversation, conversation before system. A perfect opener on a switchboard list at 9am books nothing. The quarterly audit takes an afternoon the first time and an hour after that, because the dialer report answers nine of the twelve questions on its own.

The European note

Add a thirteenth question for France and the EU: are opposition lists, do-not-call flags and data sources documented per country? It does not change the meeting rate, but it is the question a prospect's legal team will ask you first, and a team that cannot answer it has a different kind of leak. We are not lawyers; we just know the question gets asked.

How Sonik approaches the audit

Most of these twelve numbers are on the Sonik dashboard by default: connect rate by slot and persona, conversations and meetings per rep per day, meeting rate per conversation, share of dials with a signal, attempts per contact, callbacks due and callbacks done. The live coach scores questions 7 and 8 on every call, so the ten-call listening session becomes a column.

Sonik AI dialer: the call list with live call statuses and meetings booked
The Sonik dialer during a session: parallel calls, statuses and the running count of meetings booked.

The session itself enforces the fixes: lists built from the CRM with signals first, protected slots, parallel dialing for the volume, one-click dispositions that write the CRM. The audit then stops being a quarterly event and becomes the Monday review, which is where question 12 says it belongs.

Conclusion

Twelve questions, four layers, one afternoon. This week, answer the three list questions first: mobile share, signal share, attempts per contact. In our experience that is where most teams find the leak, and it is fixed before anyone touches a script.