Clear response windows and channels prevent misread silence and after-hours burnout.
8 min readIntroduction
Clients get upset when they think you are ignoring them. You get tired when Slack pings at 2 a.m. Most fights are timing problems, not attitude problems.
This guide helps you set communication expectations without sounding cold. You will get scripts, a simple policy, and ways to reset when habits drift. See also when clients message after hours.
Why this matters
If you never say your hours, clients assume you match theirs. If you reply instantly once, that becomes the standard forever.
Clear rules protect good clients too. They know when to expect updates and who to contact for approvals.
Key concepts
Primary channel
Your primary channel is the one place for work requests. Email, Slack, or a task board. Pick one main door.
Response window
Your response window is how fast you reply during working hours. Not 24/7 unless you price for it.
Status rhythm
Status rhythm means regular updates even when nothing is wrong. Weekly for retainers, milestone notes for projects.
| Concept | What it prevents | Without it |
|---|---|---|
| Primary channel | Lost requests in five apps | Chaos and duplicate work |
| Response window | "You ghosted me" | Burnout from always-on |
| Status rhythm | Client anxiety | Extra "just checking" pings |
Salag's SHIELD Protocol framework
SHIELD keeps communication fair: say what is true, stick to what you agreed, invite clarity, write it down, repeat the rhythm.
Step 1: State the facts
List tools, timezone, and tasks. No vague "I am flexible" without limits.
Checkpoint: Did you name channel and hours?
Step 2: Honor the agreement
Open your welcome note or contract. Does the client want something outside it?
Checkpoint: Can you quote the line you agreed on?
Step 3: Invite questions
Ask what urgent means to them. Offer a backup contact path for true emergencies.
Checkpoint: Do they know what not to ping you for?
Step 4: Document decisions
Email a recap after kickoff: hours, channels, update day, approval owner.
Checkpoint: Is it in writing with a date?
Step 5: Lock the rhythm
Send updates on schedule. Predictable beats perfect.
Checkpoint: Did the client get this week's note?
Step-by-step guide
- Draft a one-page comms policy. Channel, PH hours, overlap window, response time, status day.
- Send it with your welcome packet. Ask the client to confirm or edit.
- Set Slack or email status if you use those tools. "Back tomorrow 9am PHT."
- Batch replies during focus blocks instead of constant partial answers.
- Use a status template every Friday or every milestone.
- Reset early if the client moves everything to WhatsApp without asking.
- Point back to the agreement kindly when patterns drift.
Common mistakes
| Mistake | Fix |
|---|---|
| Answering at midnight once | Sets 24/7 expectation |
| No primary channel | Pick one main app |
| Apologizing for having hours | State overlap windows calmly |
| Status only when asked | Proactive weekly notes |
Real-world example
A VA joins a client's Slack and replies within minutes for two weeks. Month two, the client messages at 1 a.m. PHT for "quick edits." The VA feels trapped.
Reset: Email the agreed PH window, offer next-morning turnaround for non-urgent items, and define urgent as site-down or launch blocker only.
Final thoughts
Good communication is kind and clear. You do not need to be always on to be reliable. Write the rules early and follow them consistently.
How Salag helps
- Agreement Builder: Add comms clauses to contracts
- Scope Creep Detector: Catch extra asks early
- Rate Calculator: Price rush or extended hours fairly
Move safer. Not faster.
In short
Set client communication expectations on day one: which app you use, how fast you reply during PH hours, and what counts as urgent. Filipino VAs win when clients know when you are online and when async is fine. Use Salag's SHIELD Protocol to write it once and reuse the script.
Common questions
Set client communication expectations on day one: which app you use, how fast you reply during PH hours, and what counts as urgent. Filipino VAs win when clients know when you are online and when async is fine. Use Salag's SHIELD Protocol to write it once and reuse the script.
Pick primary channel, your reply window in their timezone, and how urgent issues reach you.
State PH hours plainly, offer overlap windows, and confirm async is normal for non-urgent items.
Yes. Even three bullets on channels, hours, and response time save months of friction.
Offer defined hours or a paid on-call tier. Unlimited access should be priced, not assumed.
SHIELD: state facts, honor agreement, invite questions, document decisions, lock the rhythm.
When reply speed, channel hopping, or after-hours pings become the norm without agreement.
Yes. Send onboarding notes the client can forward to their team.
Agreement builders and scope tools help you write boundaries before day one.
Use Agreement Builder and Scope Creep Detector when scope and comms blur together.
One 30-minute kickoff plus a written recap beats weeks of guesswork.
Retainers need weekly status rhythm. Projects need milestone check-ins and a single owner for approvals.
Resend once, reference the agreement, then schedule a 15-minute reset call.