Client playbooks and call scripts for SDR teams
Keep each client's call scripts, objections and FAQs inside the project your SDRs work in, and test script versions against each other.
Tip · "We just renewed"
Ask when the next review is, then offer a short call before it.
posted by Shelley L. · project FAQ
What's in it
Scripts per client project
Each project carries its own call scripts, by category, where the SDR is working.
Script A/B tests
Run script versions against each other and see which turns into meetings.
Project tips and FAQ
Rostered SDRs and the account manager post and read tips, objections and answers per project.
Scoped to the roster
Only SDRs rostered on the project (and its account manager) see its playbook.
Client knowledge is scattered across docs and chats
Every client starts with a kickoff deck and a call script. The real learning comes later — which objection keeps coming up, who actually picks up — and it lives in chat threads and in the heads of the SDRs who were there. An SDR who joins the project, or switches between three clients in a day, needs the current version.
The playbook lives in the client project
Each client project has its own call scripts (openers, objection handling, voicemail and more) and a tips and FAQ board. Rostered SDRs and the account manager read and write to it, so an answer found on Tuesday is there for everyone on Wednesday. The script sits next to the leads, open during the call.
A/B test call scripts per client
- 1
Write two versions
Two scripts in the same project, for example two openers.
- 2
Start the test
The project's leads are split between version A and version B.
- 3
SDRs call as usual
Each call and booking is tied to the lead and its version.
- 4
Compare meetings
See leads, calls and meetings per version, and keep the one that books.
The result is which version produced meetings, not which one felt better on the phone.
Related: call recording and transcription and the lead lifecycle.