Two lists, one calling habit
An MSP’s phone work splits into two lists that behave differently. The first is the book: clients you already manage, who owe you quarterly conversations and renewals, and who trust you enough to mention the server that has been rebooting since spring. The second is the local prospect list: SMBs in your service area with no IT person, an aging something in the closet, and an owner who signs. Both lists are worked in focused blocks with three lines per rep, and the dispositions keep them from bleeding into each other in the reporting.
The book comes first, and not just because it converts. QBR calls surface the expansion work (the second location, the compliance question, the new hire onboarding that keeps breaking), and they catch the quiet cancellation risk before the renewal date, not after.
Discovery with an engineer’s briefing attached
SMB discovery calls live or die on the first specific question. “Who handles your computer issues today?” produces the answer that matters: nobody, the office manager, the owner’s nephew, or an MSP they are quietly unhappy with. The AI summary writes the briefing the engineer needs: the stack in the prospect’s own words, the pain with a date (“rebooting weekly for a month”), the decision maker, and the fixed-monthly-cost question that most SMB owners actually care about.
The booked assessment is the product of the discovery call, and it ships with the summary attached. The engineer arrives knowing the server is eight years old and the backups are untested, which turns the assessment from an audit into a conversation the office manager already started on the phone.
The incident window: facts only, fast
When a ransomware story hits a local industry, the phone is the fastest way to reach the businesses that read the headline and changed nothing. The incident block works that vertical with facts only: what happened publicly, what a security assessment covers, and what it costs. No scare inflation, no “your neighbors were breached” unless it is true, and no promises about preventing breaches (nobody can promise that; the honest line is detection, response and recovery).
The summary captures who is exposed and how they described it (“we still fax, is that a problem?”), and the dispositions show how many assessments the window produced. Done honestly, this is the highest-converting list an MSP runs; done badly, it burns the local reputation that a local business lives on.
QBRs and the renewal conversation
The QBR block runs on data the MSP already has: ticket volume, utilization, unresolved projects. The call is a relationship maintenance pattern: what changed in the business, what the current agreement covers, what it should cover next year. The AI summary records the commitments (a documentation cleanup by March, a revised asset list) and the risk signals (a new CFO who asks what the contract includes, a second location opening in Q3).
The recording settles the disputes that renewals generate: what was promised about response times, what was said about a project’s scope, and who agreed to move the renewal date. On a book of fifty clients, that memory is worth more than any single sale.
SMB lists are B2B with consumer edges
Most of this calling is business-to-business, and the FTC rule’s B2B exemption covers much of it. The edge cases are the whole point of an SMB list: a three-person shop answers on the owner’s personal cell, the same number appears on the national DNC list, and the TCPA’s rules on prerecorded and autodialed calls to wireless numbers apply regardless of the exemption’s reach. So the posture is human-dialed, three lines, a recorded disclosure for the all-party-consent states, and stop requests honored the moment they land. Attempt caps keep the dentist who said no in March from hearing from you again in April.
The first 30 days: onboarding calls that keep clients
The calls right after a signature are the cheapest retention an MSP never schedules. Day two: the migration went as described and the office manager’s question from the sales call got answered. Day ten: the backup test ran, and the ticket response time was what the contract said. Day thirty: what has surprised the client so far. Each call is two minutes, the AI summary files what was said, and the dispositions build a health record that the QBR block inherits.
The alternative is silence between the welcome email and the renewal, which is how the competitor’s coffee meeting in month five becomes a cancellation in month eleven. The onboarding block also surfaces scope creep early: the client quietly treating a managed machine as unmanaged, or the second location appearing on the network. Caught in week one it is a contract conversation; caught at renewal it is a dispute.
Working a vertical instead of a map
MSP prospecting converts better by vertical than by radius: ten dental offices called with HIPAA-shaped questions beat fifty random SMBs called with “who handles your IT”. The vertical list gets its own talk track (the audit calendar, the imaging software, the compliance paperwork the owner dreads), its own dispositions, and its own summaries, so twenty calls teach the team what that vertical worries about. The next twenty calls open with it, and the assessment proposal arrives pre-written in the prospect’s own vocabulary.
The reporting shows which verticals answer and which ignore, and the founder’s choice of the next vertical list becomes an evidence decision instead of a guess. Attempt caps and the internal DNC list apply per list, so a practice that said no in one vertical does not reappear because it was added to another.
What you need to start
- Your own Telnyx account with numbers and caller ID.
- Prospect and client lists as CSVs with industry and contact on each row.
- A recording disclosure and one headset per rep.
- A disposition set that separates book work from new discovery.
The 14-day trial runs in a sandbox with test numbers. Load a sample block of local SMBs, run a three-line discovery block, and read the engineer briefings before real prospects are called.