Guide
How do I follow up with clients who go quiet?
You follow up with clients who go quiet by putting silence on a clock, then sending a short chase that names the last ask and makes no as easy as yes. Wait about three business days, follow up once more around a week, then close the loop. Just checking in gives them nothing to reply to. A person still sends.
By The Concrete team · Published
We make Concrete.
What the job actually is
You follow up with clients who go quiet by putting silence on a clock, then sending a short chase that names the last ask and makes no as easy as yes. The thread is not a reminder, a ticket, or a sequence until something else happens to it.
Agencies and consultants run this job in email and in Slack Connect channels shared with a client. You asked for the assets, the approval, or a yes on the proposal. They were in the thread last week. This week the channel is still. Shared channels sit on paid Slack plans on both sides. The Free plan only allows one-to-one external DMs. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 9 November 2026.
A Databox survey of 48 agencies found almost 70% of account managers handle fewer than 10 clients each. 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 at 50-plus channels you need unanswered-message alerts. 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. AgencyAnalytics asked 220-plus agency leaders and found 81% name strong relationships as the biggest retention factor, with 67% pointing to effective communication.
The buying prompt collapses four jobs: a reminder you remembered to set, a nudge when sent mail got no reply, a live phone chase, and a written follow-up a person still sends. Inbound asks you have not answered are the other direction, on the AI teammate page. Silence as a churn signal is on how to know which clients are unhappy. Promises you typed are on how to stop forgetting emails you promised. Sent mail still waiting on their reply is on how to keep track of emails you're waiting on. A sales cadence that sends on its own is a different product, on founder-led sales follow-up.
Which tool wins which job
Fund the row that matches the leak. A snooze, a waiting-time alert, and a phone call are neighboring jobs.
| Job | Wins it | Why |
|---|---|---|
| A reminder you already remembered to set | Slack To-dos | Hover a message and pick Remind me about this, or type /remind. Creating a to-do does not set a reminder by default. Guests cannot create channel reminders. Silence is not a reminder. |
| A suggestion on some sent mail | Gmail Nudges | Nudges can suggest emails to follow up on, and emails you forgot to reply to. Free. Conversation view has to be on. It suggests some threads. Silence on every sent ask still sits. |
| Awaiting-reply drafts in Gmail | Fyxer | Fyxer flags Awaiting reply or To follow up after a wait you set, then drafts. It does not send on your behalf. Pro is $37 per person per month billed annually, or $49 billed monthly, as of 9 November 2026. |
| A nudge when a customer in Slack Connect is still waiting on you | Follow Up Bot | Follow Up Bot watches unanswered Slack Connect customer messages. Customers never see the bot. That is inbound silence. Enterprise Connect is $82.50 per month billed annually, as of 9 November 2026. |
| A flagged Slack message with an owner and a due date | Chaser | Chaser turns a Slack message into a task. Reminders post in the thread. Unacknowledged work gets a private nudge. Choose Seats is $11 per seat per month billed annually, or $16 billed monthly, as of 9 November 2026. External Connections are free. |
| Phone calls, live chase of a person who went dark | A virtual assistant | Software tracks the loop. A person closes it live. The split is on AI assistant vs hiring a virtual assistant. A Slack ping still sits if they have gone dark. |
| A morning list of silent threads, a person still sends | Concrete | Each morning it nudges the owner of every open follow-up. Send / Edit / Skip cards; no auto-send mode. Follow-ups survive reboots. Design-partner preview; see what it is. |
Just checking in gives them nothing to reply to
The line operators reach for first is just checking in. It asks them to remember the thread, decide what you want, and write a reply from scratch. Ray Higdon wrote the line that stuck. Every follow-up should bring a reason, a resource, or a question. Beth Azor puts checking in, circling back, and following up in the same pile. They add no new information.
Name the last ask in sentence one. The homepage draft from Tuesday is still waiting on your notes. We need the brand assets by Friday to keep the 18th. If the timing has slipped, reply pause and we will hold. One fact they already know, one date, one easy out. Giant Creates writes the same close as make no as easy to send as yes.
Match the chase to the stall. ManyRequests splits seven stalls: a proposal, feedback on delivered work, a missed call, a missed payment, a project stuck mid-delivery, a finished project you want back, and a let me think about it. A generic check-in treats all seven as one mood. The blocked project needs the asset named. The finished project needs a reason to reply, not a pulse check. People on r/smallbusiness say the same thing after a site launch. I noticed X, want me to fix it gets an answer. Just checking in does not.
Three attempts, then close the loop
Decide the clock before anyone goes quiet. ManyRequests publishes a 3-attempt rule for most non-urgent work: first follow-up around three business days, second around one week, third around two weeks, then close the file. After you deliver work, use the review window you already wrote. After a missed call, follow up within 24 hours. Giant Creates uses the same outer shape. A few days, a couple of weeks, then a graceful close. Three touches, spaced out.
The third message is the close, not another bump. Hi Name, I have reached out a few times and have not heard back. I am going to pause the project on my end. If the timing has shifted, reply here and we can pick it up. That line often gets the reply, because it gives them a decision instead of another open loop. Adrian writes the last email as I have to assume your priorities have shifted, and I wanted to close the loop. Half the time people reply because they forgot.
Then update the list. Mark the request paused or closed. Take the slot off the morning board. Giant Creates names the harder cost. You cannot plan around a maybe. If they come back in four months, the door is still open because the last note was calm. Open asks that sit overnight are a neighboring job, on the daily summary of open client asks.
The caveat that should decide the setup
The failure operators name first is sounding desperate. The quieter failure is an AI that sends the chase on its own. Fyxer states that it drafts, and you decide what gets sent. Boomerang's Send Later if No Reply will send the second email automatically if nobody replies. A prompt that says draft only is not a send gate. Worst case with a draft is you delete it. Worst case with auto-send is you explaining the email on Monday.
A second caveat is public chase. People in a Slack Connect channel can see messages from bots and apps. A reminder posted in the client thread shows the client you are chasing them, or chasing your own team. Follow Up Bot keeps customer alerts internal. Chaser reminds in the task thread. For a shared client channel, keep the owner's nudge off the thread the client can read. Safety of putting an agent in that channel is on the shared-channel page.
A third caveat is the inverse job. Follow Up Bot wins when the customer is still waiting on you. This prompt is the other way. You are waiting on them. A waiting-time alert will not fire because they went quiet. Gmail Nudges watch some sent mail. Slack's own reminder only fires if someone set it. The leak is the outbound ask with no clock.
A fourth caveat is the phone. A written chase can sit in the same pile as the last three. The live call is the seat a virtual assistant still wins. Use it on the third attempt, or sooner if the work is blocked on a decision. Quiet can also mean the work is going well. Compare this client to their own usual pace before you escalate. Two signals moving together is the conversation on the unhappy-clients page.
Concrete is an AI employee that works in existing Slack channels and reads Gmail alongside them. It keeps every thread waiting on a reply as a follow-up. Each morning it nudges the owner. It drafts the chase as a Send / Edit / Skip card in Slack. A Gmail send needs the same tap. There is no auto-send mode. Follow-ups survive reboots. After downtime it sweeps channel history, thread replies included. It is in design-partner preview; the longer thesis is on the vision page. It does not run sequences or cadences. It does not pick up the phone.
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 in the internal channel, before the next Friday spent refreshing Sent.
- Step 1: Name the leak. Inbound waiting, outbound silence, a promise you typed, and churn detection are different. A waiting-time bot covers them waiting on you. Nudges cover some sent mail. This job is the ask you sent that got no reply.
- Step 2: Write a reply-time target and a review window. Mursa's rule is 4 business hours for standard messages, 1 business hour for urgent, and the next business day after hours. ClearFeed uses 4 hours standard, 1 hour high-touch, and 30 minutes for VIP or launch. When you send work for review, write the window in the same note. Feedback within three business days so we keep the 18th.
- Step 3: Put silence on a clock before anyone goes quiet. Three business days, then a week, then a close around two weeks. ManyRequests publishes that cadence. Do not decide whether to follow up in the moment. The clock is the process.
- Step 4: Name the last ask and give them one easy out. The asset, the approval, the date. Reply pause and we will hold. Just checking in puts the work of remembering back on them.
- Step 5: Keep the owner's chase off Slack Connect. Nudge the owner in a private channel or a DM. People in a shared client channel can see bot messages. The note the client sees still waits for a person to send.
- Step 6: Switch channel or pick up the phone on the third attempt. If the last two notes were email, try Slack, or the other way around. If the work is blocked, call. A virtual assistant wins that live chase. A fourth written bump is usually noise.
- Step 7: Close the loop and take them off the morning list. Pause the project, close the proposal, or mark the request complete. Leave the door open. A quiet maybe still holding a designer week is the leak.
- Step 8: Sweep still-open asks every morning, threads included. Channel history hides thread replies unless you open them. Use a private digest or a morning list. Keep that list off the shared channel. The setup is on the daily summary page. Priced options for client Slack live on the AI tools roundup.
Questions people ask
How long should I wait before following up with a silent client?
For most non-urgent client work, three business days is the first chase. ManyRequests publishes that window, then a second follow-up around a week, then a close around two weeks. After delivering work, use the review window you already wrote. After a missed call, follow up within 24 hours. Write the clock before anyone goes quiet.
What should I write instead of just checking in?
Name the last ask in sentence one and give them one line they can answer. The homepage draft from Tuesday is still waiting on your notes. We need those by Friday to keep the 18th. If the timing has slipped, reply pause and we will hold. A generic check-in puts the work of remembering back on them.
How many times should I follow up before I stop?
Three attempts over two to three weeks is the outer limit ManyRequests publishes for most non-urgent work. Giant Creates uses the same shape. A few days, a couple of weeks, then a graceful close. The third message pauses the project or closes the proposal and leaves the door open. A fourth written bump is usually noise.
Should I chase a quiet client in the Slack Connect channel they can read?
Keep the owner's nudge off that thread. People in a Slack Connect channel can see messages from bots and apps. A reminder in the shared channel shows the client you are chasing them, or chasing your own team. Follow Up Bot keeps customer alerts internal. The note the client sees still waits for a person to send.
Is a waiting-time bot the same as following up with a quiet client?
Follow Up Bot alerts your team when a customer in Slack Connect has waited past your target. Customers never see it. That is them waiting on you. This prompt is you waiting on them. A waiting-time alert will not fire on outbound silence. Slack's reminder only fires if someone set it.
Should an AI send the follow-up without me tapping send?
For a client-facing thread, a wrong send is the failure that costs the relationship. Fyxer drafts and you decide what gets sent. Boomerang's Send Later if No Reply will send the second email automatically if nobody replies. Concrete has no auto-send mode. Draft the chase. A person still sends.
When should I pick up the phone instead of sending another message?
On the third written attempt, or sooner if the work is blocked on a decision they owe you. A Slack ping still sits if they have gone dark. A virtual assistant wins the live chase. Software tracks the loop. A person closes it. The split is on AI assistant vs hiring a virtual assistant.
What if the quiet client is actually happy with the work?
Quiet can mean the work is going well. Compare this client to their own usual pace. A client who always takes three days is fine at three days. An hour-reply client who now takes three days has changed. Two signals moving together is the cue to ask, on how to know which clients are unhappy.
Sources
- Slack pricing, read November 9, 2026
- Slack Connect guide: Work with external organizations, read November 9, 2026
- Set a reminder (Slack), read November 9, 2026
- Later is now To-dos (Slack), read November 9, 2026
- Gmail: Reply to messages (Nudges), read November 9, 2026
- Databox: Account manager burnout, how many clients are too many (survey of 48 agencies), read November 9, 2026
- ClearFeed: Slack for client communication, a guide for agencies, read November 9, 2026
- Mursa: Slack for clients, manage communication and scope, read November 9, 2026
- AgencyAnalytics: 2025 Marketing Agency Benchmarks Report (220+ leaders), read November 9, 2026
- ManyRequests: How to follow up with clients who went silent, read November 9, 2026
- Giant Creates: When a client goes quiet, read November 9, 2026
- Follow Up Bot for Slack, read November 9, 2026
- Chaser for agencies, read November 9, 2026
- Chaser FAQ (pricing, reminders, Slack Connect), read November 9, 2026
- Fyxer pricing, read November 9, 2026
- Fyxer: Track email follow-ups (Awaiting reply), read November 9, 2026
- Boomerang: Send Later if No Reply, read November 9, 2026
- Ray Higdon: Just checking in gives them nothing to reply to, read November 9, 2026
- Beth Azor: Following up, checking in, and circling back, read November 9, 2026
- Adrian: Close the loop when a lead goes silent, read November 9, 2026
- r/smallbusiness: Client ghosted after 8 months, read November 9, 2026
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.