When a Client Expects You Available 24/7 (Set Boundaries Without Losing the Claude Code Client)
- A client who messages at night and on weekends is usually not being difficult. They just never heard when you work, and every fast reply you sent taught them to expect the next one. The fix is to set the expectation clearly, not to resent it quietly.
- Use the Profit Room's Response Window Reset: send one calm message that states your working hours and reply times, defines what counts as an emergency on their build, gives them one channel for real emergencies, and offers faster support as a paid add-on.
- Then hold it consistently. Reply inside your window, not outside it, keep sending weekly updates so they never feel in the dark, and write response times into every agreement from now on. If a client truly needs round-the-clock cover, that is a support plan with a price, not a favor.
The Short Answer
When a client expects you to be available 24/7, tell them clearly, once, how you work: your hours, how fast you reply inside them, what counts as an emergency, and how to reach you when one happens. Then offer faster or after-hours support as a paid option for clients who genuinely need it. Do not just reply slower and hope they take the hint. Silence reads as neglect, and a client who feels ignored starts to doubt the build, not just your schedule.
That is the Response Window Reset. It works because most always-on clients are not trying to own your evenings. They are anxious about something they paid for, they never saw a written expectation, and you trained them by answering a midnight message within minutes. Replace the guesswork with a clear rule and most of them relax.
Why Clients Start Expecting Round-the-Clock Replies
Before you send anything, figure out which of these is driving it. The message changes depending on the cause.
- You set the pattern. Early on, you replied to every message fast, including late at night, to make a good impression. The client now treats that as the standard.
- They do not know what is happening. If they only hear from you when they ask, every quiet day feels like a problem. Anxiety turns into messages.
- Their business runs at different hours. A restaurant owner, a shop with weekend peaks, or a client in another time zone may simply be awake and working when you are not.
- The build is live and something matters to them. Once a client's customers use the build, every hiccup feels urgent, even when it is not.
- Nothing was ever agreed. No response times in the agreement, no definition of an emergency, no support plan. Without a rule, the default becomes 'whenever I message.'
Notice that most of these are fixed by information, not by pushing back. That is why the reset leads with clarity and a path for real emergencies, not with a list of things the client is doing wrong.
Run the Response Window Reset
Send one message, in writing, ideally right after you have delivered something good so it lands as an upgrade in how you work, not a complaint. Cover these five things.
- Your working hours and time zone. State them plainly, for example weekdays during your business hours, in your time zone.
- Your reply time inside those hours. Pick something you can keep every time, such as the same business day. A promise you always keep beats a fast one you sometimes break.
- What counts as an emergency. Be specific to their build: the live system is down, customers cannot complete a purchase or booking, or data looks wrong or exposed. A new feature idea, a copy change, or a question about next month is not an emergency.
- One channel for real emergencies. A single phone number or a tagged message type, used only for the emergencies you just defined. Everything else goes through your normal channel and gets answered in your window.
- A paid option for faster cover. If they want after-hours or weekend response, offer it as a support plan with its own price. [Packaging a maintenance plan for AI builds](/blog/package-a-maintenance-plan-for-ai-builds) covers how to structure one.
Make the Window Easy to Live With
A boundary only works if the client feels looked after inside it. These habits do most of the work.
- Send a [weekly client update](/blog/weekly-client-update-prevents-fires). A short note on what was done, what is next, and anything you need from them answers most questions before they get asked at night.
- Hold the line consistently. If you answer a non-urgent message at 11pm 'just this once,' you have reset the expectation back to always-on. Schedule the reply for the morning instead.
- Batch their small requests. Ask them to drop non-urgent ideas into one shared list or document, and review it together once a week. It turns a stream of pings into one tidy conversation.
- Show them the live status themselves. A simple status page or [client reporting dashboard](/blog/build-a-client-reporting-dashboard-with-claude-code) lets the client check that the build is running without having to ask you.
- Build monitoring into the build. A basic alert that tells you when the live system errors, set up with Claude Code during the build, means you often know about a real problem before the client does. [When a client finds a bug after launch](/blog/client-finds-a-bug-after-launch) covers how to respond when one slips through.
| What the client says | What it usually means | How to respond |
|---|---|---|
| Other freelancers answer right away | They want reassurance, not speed | Point to your emergency line and weekly updates, and offer the extended support plan. |
| My business runs on weekends | They have real off-hours needs | Quote a support plan that covers their peak hours, priced as its own service. |
| It is only a quick question | They do not see the cost of interruptions | Answer it in your window, and suggest adding quick questions to the shared list. |
| Fine, but I am not happy | The relationship may not fit | Keep the boundary, deliver well inside it, and see [how to fire a client without burning the relationship](/blog/how-to-fire-a-client-without-burning-the-relationship) if it keeps eroding. |
How to respond when the client pushes back
Set It Up Before the Next Project Starts
- Write response times into the agreement. A line in your [one-page agreement](/blog/one-page-agreement-before-you-build) covering working hours, reply times, and what counts as an emergency settles the question before the first message.
- Cover it in onboarding. Say it out loud on the kickoff call, the same way you cover scope and payment. [Setting client expectations before a Claude Code build](/blog/set-client-expectations-before-a-claude-code-build) walks through what to cover.
- Do not reply instantly in week one. Your first-week reply times become the client's standard. Reply quickly and well, inside your window.
- Sell support as a product. Offer after-hours or weekend cover as a priced tier from the start, so a client who truly needs it can buy it instead of expecting it free.
- Charge for real urgency. When a client wants something rushed outside your normal pace, [charge a rush fee](/blog/charge-a-rush-fee-without-losing-the-client) instead of quietly working the weekend.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
What should I do when a client expects me to be available 24/7?
Send one calm message in writing that states your working hours, how fast you reply inside them, what counts as an emergency on their build, and one channel for real emergencies. Offer after-hours or weekend cover as a paid support plan for clients who genuinely need it.
Is it unprofessional not to reply to clients at night?
No. Replying reliably inside clear working hours is professional. What feels unprofessional to a client is not knowing when they will hear back. Tell them your reply times, keep them every time, and give them a way to reach you for true emergencies.
What counts as an emergency on a Claude Code build?
Define it for each build, in writing. A common definition is: the live system is down, customers cannot complete a purchase or booking, or data looks wrong or exposed. Feature ideas, copy changes, and planning questions are not emergencies and go through your normal channel.
Should I charge extra for after-hours support?
Yes, if the client wants it. Faster or round-the-clock response costs you time and focus, so offer it as a separate support plan with its own price. Clients who truly need it will pay, and clients who do not will happily use your normal hours.
How do I stop the next client from expecting 24/7 replies?
Put working hours, reply times, and an emergency definition in your agreement, say them out loud on the kickoff call, and avoid instant late-night replies in the first week. The pattern you set early becomes the client's expectation.
Last reviewed October 12, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →