Example 1
“Can you jump on this now?”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
Pricing pressure scenario
Unavailable is easiest to hear when it comes with a clean next window, not a long excuse.
Paste your client messageStart here on this page
2 free drafts
Paste the client message and the next time you can realistically respond. FlowDockr will help you say unavailable clearly without sounding flaky. Start with the exact message and generate without leaving this scenario page.
Review the suggested approach and choose the response that best fits your client conversation.
Your polished reply will appear here
Generate a result to see the send-ready message, the reasoning behind it, and follow-up guidance if the client keeps pushing.
These are the kinds of pushback messages this page is designed to help you answer.
Example 1
“Can you jump on this now?”
Example 2
“Are you free to handle this today?”
Example 3
“I need to know if you are available for this right away.”
When to use: Use when you know when you can next pick the issue up.
Risk: If the next window is vague, the reply still feels uncertain.
Example wording: I am not available to take this on right now, but I can pick it up in the next working window and update you from there.
When to use: Use when you do not need to justify the reason for being unavailable.
Risk: If the wording is too short, it can sound dismissive.
Example wording: I am not available to respond in real time on this right now, so I will come back to it once I am back in my normal working block.
When to use: Use when the client may genuinely need a faster decision path than you can provide.
Risk: If the fallback is too open, you recreate the pressure you are trying to reduce.
Example wording: If timing is critical before then, let me know the hard deadline and I can tell you whether there is a realistic way to handle it cleanly.
I am not available to pick this up right now, but I can come back to it in the next working window and update you from there.
I am not available to respond to this in real time right now, but I will pick it up in the next working window and let you know the next step from there.
I am not available for this right now. I will return to it in the next working block rather than respond in real time outside that window.
Most reply quality drops when freelancers concede or over-explain too early.
State that you are unavailable, give the next realistic window if you have one, and avoid over-explaining unless it truly helps.
Usually no. The client mainly needs clarity about timing, not a full reason.
A calm tone and a specific next window make the reply feel reliable rather than evasive.
Move to the next likely decision path instead of restarting from scratch.
Tell a client you are unavailable without sounding flaky, guilty, or over-explanatory.
Trigger stage
mid project
Pressure type
availability boundary
Real risks
boundary erosion, burnout risk, lose deal
Decision goals
set boundary, protect capacity, move to close
In scope
Out of scope
Paste the client message and the next time you can realistically respond. FlowDockr will help you say unavailable clearly without sounding flaky.
Choose another pricing situation from the decision console.