Guide

How do agency owners take a vacation without clients noticing?

Agency owners take a vacation without clients noticing by naming a coverage owner on every client Slack channel before they leave, handing that person a one-page brief of open asks and exceptions, keeping the same 4-business-hour reply target, and leaving send as a tap. An out-of-office in the shared channel is how they notice. Silence is how they notice. A bot that talks unsupervised is how they notice.

By The Concrete team · Published

We make Concrete.

What clients notice when the owner is gone

Agency owners take a vacation without clients noticing by naming a coverage owner on every client Slack channel before they leave, handing that person a one-page brief of open asks and exceptions, keeping the same 4-business-hour reply target, and leaving send as a tap. The client still gets the same agency, the same voice, and the same wait. The owner is missing from the thread.

Tide's Business Benchmark Index 2026, from a Censuswide survey of 500 UK small business owners in December 2025, found owners take an average of 15 full days off a year, defined as no calls, emails, or business admin. 17% take none. That share rises to 21% of sole traders. 56% take 10 days or fewer. Michael Jurek, a Tide member and co-founder of North London Storm, put the bottleneck this way: nobody else could fully step into his role because of the specific knowledge and context he held.

Karl Sakas writes that a dedicated account manager typically holds 4 to 8 accounts, and that an AM or PM will ideally bill around 20 hours a week. Databox surveyed 48 agencies and found almost 70% keep each account manager under 10 clients. At a 3-to-30 person shop the owner is still that person for most clients. Vacation is the week those 4 to 8 accounts have no one who already knows the exceptions.

Write a reply target into the channel and keep it while you are gone. Mursa publishes 4 business hours for standard client Slack, 1 business hour for urgent, and the next business day after hours. Its July 2026 workspace audit logged about 3,100 client-side messages across 14 client channels over 27 weeks, and recorded zero after-hours escalations. ClearFeed's agency guide, updated 31 October 2026, says an account manager can usually keep 10 client channels straight, someone misses a ping around 40, and a practical SLA is 4 hours for standard clients, 1 hour for high-touch, and 30 minutes for VIPs or launches. One of its SOP questions is who covers the channel when the owner is away.

Agencies run this in Slack Connect channels shared with the client. Slack has no native owner on a thread. People in that channel can see messages from bots and apps. Shared channels sit on paid Slack plans on both sides. The Free plan only allows one-to-one external DMs, and keeps 90 days of message history. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 11 November 2026. Business+ is $15 billed annually, or $18 billed monthly. Slack's native out-of-office is on Enterprise plans. Enterprise+ is $45 per user per month billed annually.

Asana's Anatomy of Work Index, which surveyed over 10,000 knowledge workers, found they spend 60% of their time on work about work, including searching for information and chasing the status of work. The same index found the average employee uses 10 different apps every day. A coverage brief that lives in the owner's head is that 60% for the person who stays.

Overnight coverage is a neighboring job, on how agencies keep client Slack answered after hours. Missing pings are on how agencies stop missing client messages in Slack Connect. A morning list of still-open asks is on the daily summary page. The dump when someone leaves for good is on getting client knowledge out of your head when the account manager quits. Standing exceptions belong on the preference sheet. Freelancers asking the same question from one client workspace are on always available in a client's Slack.

Which setup wins which job

Fund the row that matches the leak. A quieter phone, a coverage brief, and a draft a person still sends are neighboring jobs.

JobWins itWhy
Pause the owner's pingsSlack notification scheduleA notification schedule pauses alerts outside the hours you choose, on every Slack plan. Other people see a snooze icon on DMs and can override it once per day. None of that posts in the client channel.
A palm-tree next to your name in Slack ConnectSlack status, or Enterprise out of officeA status may be visible to members of other organizations in channels shared externally, depending on workspace settings. Slack's native out-of-office is Enterprise only. Mentions get a private auto-reply. The OOO message stays inside your organization. The emoji in a shared channel is how they notice.
A receipt that the message landedThena or ClearFeed auto-ackThena ships auto-responses for holidays, weekends, and missed SLAs. Auto-response is off by default and can run globally or per channel. ClearFeed tells agencies to auto-acknowledge after hours, then answer the next business day unless it is urgent. A receipt is a wait the client was told about.
A named person on every client channelA coverage owner and a backupMursa assigns a primary and a backup per client channel, and puts the rotation on the pinned canvas. ClearFeed's SOP asks who covers it when the owner is away. A group in the channel means everyone assumes someone else will answer.
The one-page brief of open asks and exceptionsAn internal Slack canvas, an Asana OOO plan, or a PTO handoff templateCanvases sit on paid Slack plans. Keep this one on the internal twin. Asana's out-of-office checklist, dated 24 July 2026, tells you to write a coverage plan, reassign work due while you are out, and set Away. Be Right Back's Notion template assigns coverage tasks before leave starts and keeps notes for return.
A morning list of still-open asksA daily still-open list, or a helpdesk digestSlack recaps catch you up on muted channels. A still-open list names an owner on every open ask. That job is on the daily summary page. Channel history hides thread replies unless you open them.
A draft the coverage person still sendsLindyLindy Team starts at $29.99 a month for 3,000 credits as of 11 November 2026. Its pricing FAQ says anything with outside impact waits for approval, including posting to another channel.
A human reply at 11pmNamed on-call, or follow-the-sunTrue overnight coverage costs a seat. After-hours setup lives on the after-hours page. Most 3-to-30 person shops auto-ack overnight and catch up in the morning.
Drafts plus follow-ups that survive the weekConcreteReceipt marks on inbound messages. Send / Edit / Skip cards; no auto-send mode. Follow-ups survive reboots. Each morning it nudges the owner of every open ask. Design-partner preview; see what it is.

What belongs on the coverage brief

Write the sentences you already say to yourself while you work the account. One page per client. Pin it on the internal twin, shown by default. A canvas in Slack Connect is visible to everyone in the channel, so keep this brief off the thread the client can read.

DocumentInclude or leave outWhy
Named coverage owner and backupIncludeMursa puts a primary and a backup on the pinned canvas. ClearFeed asks who covers the channel when the owner is away. One person owns the inbound queue and the send button.
Open asks still sitting in Slack or emailIncludeChannel history hides thread replies unless you open them. A catch-up that reads only top-level messages drops the actual ask. Put the thread link, the owner, and whether it is still open.
Last two promises the agency madeIncludeThe extra revision agreed in passing. The report format they were told would change next month. From the client's side, that was the agency's word.
Standing exceptionsIncludeWho hates Monday calls. Which CMO wants a one-line summary. Which account has a standing exception on revisions. The coverage person arrives with clean process and zero history without this line. Longer preference sheets live on the preferences page.
Who can say yes while you are goneIncludeScope, discounts, and timeline slips still need a named person. Founder-only yes is the row that cannot be hidden. Write the limit in one sentence.
What counts as urgentIncludeOutage, launch breakage, legal threat. Everything else waits for the next business morning. Mursa and ClearFeed both treat after-hours as next business day unless it is on that short list.
Access still in the owner's nameIncludeAd accounts, pages, and client chats set up on a personal login. The coverage person cannot send a file they cannot open.
The 4-business-hour reply targetIncludeKeep the same clock the client already has. Changing it for the week is how they notice. Put 4 business hours standard, 1 business hour urgent, next business day after hours on the same page.
An out-of-office posted in the client channelLeave outA palm-tree in Slack Connect is the notice. Slack's OOO message stays inside your organization. A public OOO in the shared channel tells them you left.
A 40-page SOP, or a full Slack exportLeave outThe coverage person will not read 18 months of scrollback before the first client ping. One page of open asks, exceptions, and who can say yes is the working set.
Pricing, margins, other-client work, landminesLeave out of the shared channelThose stay on the internal twin. Mursa keeps sausage-making internal. A screenshot of the shared channel can go to their boss.
Passwords, API keys, personal loginsLeave out of SlackName who grants access on the brief. Put the secrets in the password manager. A canvas in Slack Connect is visible to everyone in the channel.
An AI that sends unsupervisedLeave outPeople in Slack Connect can see messages from bots and apps. ClearFeed says AI should not auto-send replies without review, or replace the person responsible for the relationship. Send stays a tap.

What Slack itself does when you leave

A notification schedule pauses alerts outside the hours you choose. Workspace owners can set a default. Your own schedule overrides it. Other people see a snooze icon next to your name. When they send a DM they can override it once per day for an urgent message. You can add the coverage owner to a VIP list so their pings still come through. None of that posts in the client channel.

A status is the line next to your name. Availability is the green or grey dot. Slack sets you away after 10 minutes of desktop inactivity. You can schedule a status in advance. Depending on workspace settings, that status may be visible to people in Slack Connect. A palm-tree next to your name in the shared channel is the notice. Pause notifications and leave the status blank if you want the channel to look the same.

Slack's native out-of-office is on Enterprise plans. Other members see the out-of-office emoji next to your name. Mentions get a private auto-reply with your OOO details. Members of external organizations can see the status if your Enterprise settings allow it. The OOO message stays visible only to members of your organization. Most 3-to-30 person shops are on Pro or Business+. Native OOO is an Enterprise feature.

You can schedule a message for later from a channel, DM, or thread: on desktop, the arrow next to the paper plane; on mobile, tap and hold send. That is how a coverage person writes the reply at 10pm and has it land at 9am without training the client to expect 10pm.

Pin a canvas as a tab on the internal twin and show it by default. Put the named owner, the backup, the 4-business-hour target, who can say yes, and the open asks. Canvases sit on paid Slack plans. Mentioning someone in a canvas notifies them only if the canvas is already shared with them. Keep the coverage brief off the shared client channel.

The caveat that should decide the setup

The failure agencies name first is an AI that talks to the client unsupervised. One wrong reply can cost the account. People in a Slack Connect channel can see messages from bots and apps. Thena ships auto-responses for holidays, weekends, and missed SLAs. ClearFeed's agency guide says AI should not fully answer complex strategy questions, auto-send replies without review, or replace the person responsible for the relationship. On X in November 2026, Manny Bernabe wrote that the aim is an agent stack good enough to go on vacation without checking Slack continually, and that it still escalates when needed. Drafts can land overnight. Send stays a tap.

The louder failure is the public OOO. Slack's native out-of-office is Enterprise only, and the message stays inside your organization. The status emoji may still show in Slack Connect. A palm-tree in the shared channel, a beach photo, or a posted OOO is the client noticing. Pause notifications. Leave the status blank. Let the coverage owner answer as the agency.

The quieter failure is founder-only yes. Tide's 17% who take no full days off are often that person. Michael Jurek said nobody else could fully step into his role because of the knowledge he held. If only you can approve a scope change, a discount, or a timeline slip, the client will feel the gap the first time that question lands. Write the limit on the brief, or stay reachable for that short list.

On r/antiwork, operators tell people never to mention PTO to a client. Speak in workload dates: what will ship, and when. The coverage owner is already on the channel as the backup. The client already has a 4-business-hour target. Vacation is using that setup for a week.

Concrete is an AI employee that works in existing Slack channels: every incoming message gets a receipt mark, drafts land as Send / Edit / Skip cards, and there is no auto-send mode. After downtime it sweeps channel history, thread replies included. Follow-ups survive reboots. Each morning it nudges the owner of every open ask. It is in design-partner preview; the longer thesis is on the vision page. Safety of putting an agent in that channel is on the shared-channel page. Drafting the client-facing reply is on the approval-before-send page.

Step by step: the setup for a 3-to-30 person shop

This is the boring version that holds when the owner is still the account manager for most clients. Pin it two weeks before you leave, while there is still time to name a backup who has done the work once.

  • Step 1: Rank clients by who would feel you were gone. Sakas puts a dedicated AM at 4 to 8 accounts. Start with the accounts where you are still the person who says yes. A long weekend on the quietest book is the first test. Tide's average owner takes 15 full days a year. A week is the working target once coverage holds.
  • Step 2: Name a coverage owner and a backup per channel. One person owns the inbound queue and the send button. The backup is named on the same canvas. ClearFeed: do not add every internal person just in case. Mursa lets the client see the rotation as the account team.
  • Step 3: Write the one-page brief. Open asks, last promises, standing exceptions, who can say yes, the urgent list, and access still in your name. Pin it on the internal twin, shown by default. Asana's OOO checklist is the same plan if the work already lives on a board: reassign anything due while you are out.
  • Step 4: Move open work onto named follow-ups. Every still-open line gets an owner. Channel history hides thread replies unless you open them. File due-date work into Asana, ClickUp, or the tracker you already use. Promises typed in the thread are on the chief of staff page.
  • Step 5: Keep OOO internal, and auto-ack only if you already use a helpdesk. Pause notifications. Leave the Slack status blank in Connect. Do not post a palm-tree in the client channel. If Thena or ClearFeed already auto-acks after hours, keep that receipt. It names when a person will look. The reply still needs the coverage owner.
  • Step 6: Keep send as a tap, and sweep threads each morning. Drafts can land overnight. People in Slack Connect can see bot messages, so keep drafts off the shared thread. The coverage person opens the threads where the asks live. A morning still-open list is on the daily summary page. Priced options live on the AI tools roundup.
  • Step 7: Take Slack off your phone, or mute everyone except the coverage owner. Remove Slack so you cannot peek, or add the coverage owner to a VIP list so only that person can break through. Everything else waits. Founder-only yes is the one ping you keep, and only if that limit is on the brief.

Questions people ask

Should I tell clients I am on vacation?

If coverage holds, speak in workload dates. On r/antiwork, operators say never mention PTO to a client; name what will ship and when. The leak is a palm-tree in Slack Connect, a silent channel, or a bot that talks.

Can I just set a Slack out of office?

Slack's out-of-office status is on Enterprise plans. Mentions get a private auto-reply. The OOO message stays inside your organization. External people in Slack Connect may see the status emoji, depending on org settings. A palm-tree next to your name in a shared channel is how they notice.

What if I am a solo founder with no team?

Tide found 21% of sole traders take no full days off. Michael Jurek said nobody else could step into his role because of the knowledge he held. Write the brief anyway. Name a backup freelancer or a partner shop, or tell the client the dates in workload terms.

Should an AI reply in the client channel while I am away?

People in Slack Connect can see messages from bots and apps. One unsupervised reply can cost the account. ClearFeed says AI should not auto-send replies without review. Lindy waits for approval on anything with outside impact. Drafts can land overnight. Send stays a tap.

How long can an agency owner be gone?

Tide's 2026 index found UK small business owners take 15 full days off a year on average, and 56% take 10 or fewer. A long weekend is the usual first test. A week holds when a coverage owner has the brief and the same 4-business-hour target. Founder-only approvals still need you.

What is a good reply time while the owner is out?

Keep the same target you already write into the channel. Mursa publishes 4 business hours for standard client Slack, 1 business hour for urgent, and the next business day after hours. ClearFeed's practical SLA is 4 hours standard, 1 hour high-touch, and 30 minutes for VIPs or launches.

How do I keep the coverage person from pinging me on the beach?

Name who can say yes on the brief, and a short urgent list. Everything else waits. Put the coverage owner on your Slack VIP list if you keep the app, or uninstall it. Mursa assigns a primary and a backup per channel so one person owns the queue.

Do clients see my Slack status in a shared channel?

They might. Slack says status may be visible to members of other organizations in channels shared externally, depending on workspace settings. The Enterprise OOO message stays internal. Pause notifications without a palm-tree if you want the channel to look the same.

Do both the agency and the client need a paid Slack plan for a shared channel?

Yes. Slack Connect channels require each organization to be on a paid plan. The Free plan allows only one-to-one external DMs and keeps 90 days of history. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 11 November 2026.

Sources

If your team already runs its work in Slack, start with one role in one channel. Concrete is an AI teammate that works in your Slack channels and asks a person to approve before anything goes out. It is not a chatbot builder, and it never sends on its own.