Most freelancers prefer email for follow-ups — and for good reason. But sometimes email isn’t getting traction, or the situation calls for a more direct conversation. Having a script ready means you’re not fumbling for words when the phone actually rings or when you have to leave a voicemail that sounds like a question mark.
When to call instead of email
Phone calls are higher-friction than emails for both parties. Before calling, ask whether the situation justifies that friction. Calling after one unanswered email is premature. Calling after three unanswered emails over two weeks is appropriate.
Good reasons to call: email has gone unanswered for two or more weeks, you have a time-sensitive question that’s blocking project work, an invoice is significantly overdue, or you have an established relationship with the client where a phone call is normal.
If you’re calling a prospect who only knows you through email, a call is an escalation. Use it intentionally and not more than once if they don’t pick up.
Script 1: Following up on a proposal
“Hi [Name], this is [Your Name] — I’m the [your specialty] who sent you a proposal for [Project Name] about [X weeks] ago. I wanted to follow up and see if you had any questions, or if there’s anything about the scope or budget I can adjust. Is now an okay time to talk for a few minutes?”
If they say they haven’t had time to review it: “No problem at all — is there a better time later this week when I could check back in?”
If they have concerns: listen, take notes, offer to send a revised version.
Script 2: Following up on an overdue invoice
“Hi [Name], this is [Your Name]. I’m calling about Invoice #[number] for [amount], which was due on [date]. I just wanted to make sure everything’s okay on your end and see when I can expect payment.”
If they say there’s a problem: “Thanks for letting me know — what would be the best way to resolve this? I’m happy to work something out.” (Then document whatever they say in writing after the call.)
If they say payment is coming: “Great, thanks for the update. Can you give me a rough timeline — are we talking this week or next?” (Pin down a specific date.)
Script 3: Voicemail after email goes unanswered
“Hi [Name], this is [Your Name]. I’ve sent a couple of emails about [brief context — proposal, invoice, project question] and wanted to try calling in case email isn’t the best way to reach you. No rush — you can call me back at [number] or just reply to my last email. Thanks.”
This is under 25 seconds. It covers the essential information, assumes good faith, and gives two response options.
Voicemails work best when they’re short enough that the recipient hears the callback number before getting impatient. State your name, the reason in one sentence, your phone number, and a backup (email). Nothing more.
Script 4: Following up after a discovery call
“Hi [Name], this is [Your Name]. We spoke on [day] about [Project Name]. I sent over the proposal on [date] and wanted to follow up to see if you had any initial reactions or questions. Do you have five minutes?”
If the timing is right, they’ll talk. If not, they’ll tell you — and now you have a specific callback window.
Script 5: Checking in with an existing client
“Hi [Name], this is [Your Name]. I know we wrapped up [Project Name] about [timeframe] ago — I wanted to check in and see how it’s going. Happy to help if there’s anything that’s come up, or just great to hear you’re getting value from it.”
This call has no sales agenda. It’s genuine relationship maintenance, which is what generates repeat work.
Handling common responses
“I’m not interested.” Respect it immediately. “No problem, thanks for letting me know. Happy to reconnect in the future if anything changes.” End the call.
“I’ll call you back.” “Of course — is there a day this week that works?” Get a specific day. If they don’t commit, follow up by email the next day.
“Send me more information.” “Absolutely — what specifically would be helpful? I want to make sure I send what you actually need.” A request for “more information” can be a stall or a genuine ask. Clarify before sending anything.
Using tracking data to know when to call
If you send proposals with a tool like Waco3, you can see when a client has opened the proposal. That read data is useful for the call too — you know they’ve engaged with the document, which means any questions they have are likely specific. You can open with: “I can see you’ve had a chance to look at the proposal — did anything come up that I can help clarify?”
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
