MSP calling playbook: call blocks, cadence and KPI ranges

The call block, in two shifts

MSP prospecting is a territory and vertical business. A rep calling fifty random businesses learns nothing repeatable. A rep calling fifty medical offices in the same county learns the backup stories, the practice-management systems and the compliance fears of one vertical, and every call makes the next one better.

Morning, discovery block. New SMBs grouped by vertical, then referrals from existing clients. Expect front desks, wrong contacts and voicemail. The deliverable is booked assessments and named contacts.

Afternoon, book block. Booked assessments, QBRs, incident follow-ups and referrals to place. This block is where revenue hides, and it dies first whenever the week gets busy. Treat it as an appointment.

List hygiene

Load SMB lists with company, industry, contact where available, phone and any stack notes. Deduplicate by phone and by address, because a single business appears on chamber lists, association rosters and purchased files at once. Tag the source on every row so you can later see which lists produce assessments and which produce only dials.

Screen the internal do-not-call list before the block. A stop request is absolute and goes into suppression the same day. Make sure suppression follows the account, not a rep’s personal spreadsheet, because MSP staff turn over and the record must outlive the seat.

Attempt cadence

Five touches over three weeks, then park for a quarter.

• Day 1 discovery: who handles IT, current support, downtime consequence, assessment offer.
• Day 3 contact confirmation: get the right name and a better time.
• Day 7 assessment offer: tied to the specific pain captured on day 1.
• Day 12 follow-up: confirm the offer arrived, answer the flat-fee question plainly.
• Day 21 close-out: “Want me to check back before the next fiscal quarter?”
• Then park for a quarter unless a stop request or a news event reopens it.

Quiet hours follow the contact’s local time. Keep the voicemail to a sentence: name, firm, the assessment offer, a callback number.

Dispositions in IT terms

• Assessment booked: day, window, pain to prep.
• QBR scheduled: for the client book.
• No IT person: contact name for a later pass.
• Has an MSP: long callback, renewal season noted.
• In-house IT: admin name, different pitch later.
• Callback requested: with the date.
• Not interested: with the reason, because the reason is data.
• Left voicemail and Do not call.

Working three lines on an SMB list

DialBreeze rings up to three numbers per rep and the rep takes the live answer, with a recorded voicemail dropping on the rest. SMB lists are front-desk heavy, so three lines buys conversations per hour rather than raw dials. Two owners occasionally answer at once; pick a line count the rep can serve without dropping a practice manager mid-sentence.

Recording feeds the AI summary, so calls you want summarized need to be recorded. Several states require every party to consent to recording, so keep a short disclosure. On the dialing side, business-to-business calls sit mostly outside the FTC Telemarketing Sales Rule under 16 CFR 310.6(b)(7), but the wireless rules under 47 CFR 64.1200 reach the cell phones owners actually answer, and 16 CFR 310.4(c) holds solicitation to 8 a.m. through 9 p.m. local time at the called party’s location. DialBreeze applies your internal lists, quiet hours and attempt caps; it does not decide whether a number may be called.

Where the AI summaries go

The summary should brief the engineer without a second discovery call. Stack in their words, user count, backup status, who handles IT today, who signs, the pain with a date, and the agreed next step. Before the engineer rolls, check the stack details against the recording, because an assessment that opens by misquoting the client’s own setup loses the room in the first five minutes.

Keep prospect and client records apart. A QBR call and a discovery call need different fields, and merging them makes both reports meaningless. DialBreeze is not an RMM or a PSA; it is the calling seat next to those tools, and the AI summary is a note, not a ticket.

KPI targets as ranges

Reference points measured in DialBreeze production use (last 90 days to 2026-09-26, three-line sessions, one operator per session): median of about 85 dials per active calling hour, about 600 dials per operator day, and a 17.8 percent person-connect rate. Aggregate measured values, not a promise.

For an MSP desk:

• Dials per rep day: measured median about 600 per day on three lines.
• Person-connect rate: expect a wide band on front-desk lists.
• Assessments booked per rep-week: track it weekly and set the target from your own first two weeks of data. While working a clean vertical list.
• Assessment show rate: track it weekly and set the target from your own first two weeks of data.; the lever is a confirmation call the day before.
• Close rate from assessment to agreement: track it weekly and set the target from your own first two weeks of data. When it sags, fix the assessment before adding dials.
• QBR completion per quarter: every client offered a slot, which is a service promise more than a sales metric.

Compliance, disclosure and the parts that belong to counsel

Keep suppression current, honor every stop request, use a recording disclosure, and hold solicitation calls inside the local calling window. Discovery calls touch patient and client data constantly; what you promise on a recorded call about handling that data must match your contracts, and anything involving a specific compliance regime goes to counsel before the script claims it. This playbook is an operating guide, not legal advice.