Your Client Just Added You to Their Slack or Teams Channel: Setting Communication Boundaries Before You Reply

04 October 2026·4 min read

Quick answer: Before you reply in that new Slack or Teams channel, decide (and briefly state) your response-time expectations, which topics belong there versus in your actual project tools or email, and whether notifications are even on for you. Say it once, warmly, in the first message — it's far easier to set the norm on day one than to walk it back after three weeks of answering 9pm pings. 📱

It usually starts innocently: "Hey, I've added you to our Slack so it's easier to chat!" and suddenly you're one notification away from being treated like an internal team member, on someone else's always-on schedule, inside a tool you don't control and can't export history from easily. 💖 It's not a red flag on its own — plenty of great client relationships run partly through a shared channel — but it's a moment that deserves a deliberate response, not just an automatic "sounds good!"

What most service providers get wrong

Most people say yes immediately and figure out the boundaries later, by accident, usually after they've already answered a Saturday message and accidentally set the expectation that they will. Once that precedent exists, it's awkward to reverse — the client isn't being unreasonable, they're just following the norm you set without meaning to. The other common mistake is being too rigid in the opposite direction, declining the invite entirely and coming across as difficult, when a short, friendly note about how you'll use the channel solves the same problem without the friction.

The first-message boundary script:

"Thanks for adding me! Quick note so we're on the same page — I'll check this channel during business hours [specify days/hours], and for anything urgent or time-sensitive, [email/phone/your usual project tool] is the fastest way to reach me. Happy to use this for quick questions and updates in the meantime. 🤝"

If notifications are on by default and you don't want them:
Mute the channel immediately (every platform allows this) and set a specific time once or twice a day to check it, rather than reacting in real time to every message.

If a request comes through the channel that needs a formal record (a scope change, a brief, a decision with cost implications):
"Great, let's confirm this over email so it's on record for both of us" — said warmly, not as a rebuke.

A freelance consultant working with a mid-sized company client: she was added to their Teams workspace in week one and, without thinking much of it, replied to a message at 8pm because it happened to come through while she was already on her phone. Within a fortnight, evening messages had become the norm, and she had to have an awkward, delayed conversation to reset expectations that would have taken ten seconds to set up front.

A small agency onboarding a new retainer client: their policy — stated plainly in the onboarding email before the Slack invite even arrived — was "we're happy to use Slack for quick check-ins, but anything involving scope, budget or deadlines goes through email so it's documented." The client appreciated the clarity rather than resenting it, and it headed off a dispute months later when a verbal-sounding Slack request turned out to need a real paper trail.

How to set this up without it feeling like a lecture

Decide your policy before you're in the moment, not while a notification is actively pinging — it's much easier to sound calm and considered in advance.
Keep the first message short and warm, not a formal policy document — one or two sentences does the job.
Check your notification settings immediately, not after a week of unwanted pings — most tools default to notifying you on every message.
Repeat the boundary gently if it slips, rather than letting resentment build silently — "just a reminder, I'll pick this up properly tomorrow morning" is enough.

💡 The honest trade-off: setting this boundary clearly won't stop every client from occasionally messaging out of hours — some will, and that's a judgement call about the relationship, not a rule you can always enforce. What it does do is make it your choice whether to reply, instead of a habit they didn't realise they'd trained into you.

Mistakes to avoid

Replying out of hours "just this once" without saying anything. That one reply quietly becomes the new expectation.
Letting important decisions live only in chat. Scope changes and approvals need a record somewhere searchable and exportable.
Treating the invite as an insult or overreach. Most clients mean it as convenience, not a power move — respond accordingly.
Never actually checking the channel. If you set hours and then miss them anyway, the boundary loses credibility fast.

Frequently asked questions

Is it unprofessional to decline joining a client's Slack or Teams entirely?

Not necessarily, but it depends on the relationship and how central the tool is to how they operate — for some clients, declining will feel like friction for no reason. A short note about how you'll use it is usually the better middle ground.

What if the client gets annoyed when I don't reply instantly?

Restate the boundary calmly once, and hold it — a client who's genuinely annoyed by reasonable business-hours expectations is telling you something worth noting about the relationship going forward.

Should this boundary be in a written contract, or is a casual message enough?

For most relationships, a friendly message is enough day to day — but if communication expectations matter a lot to how you work, it's worth including a line about response times and preferred channels in your actual service agreement too, so it's not just a one-off conversation nobody remembers in six months.

Keep reading 🤍

Written by

Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦