Guide
How do I stop answering the same client questions over and over?
You stop answering the same client questions over and over by writing the five to ten questions that actually repeat, pinning the answers on the Slack canvas the client already opens, and keeping a saved reply for the ones who still ping. Status questions such as any update need a visible current-work list. A Zendesk help center is a neighboring job for a support team with tickets.
By The Concrete team · Published
We make Concrete.
What the job actually is
You stop answering the same client questions over and over by writing the five to ten questions that actually repeat, pinning the answers where the client already looks, and keeping a saved reply for the ping that still arrives. How to request work. Where last week's report lives. Who to ask for access. Reply hours. The revision process. Those lines stay true for months. Any update is a different job. It needs a current-work list, because the answer changes this week.
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 10 November 2026. Canvases sit on paid plans. Add the FAQ as a tab, then right-click and select Show canvas by default so it opens the first time someone visits.
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. Every retyped answer comes out of those 20 hours.
Write a reply target into the channel. 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.
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. The FAQ has to live in Slack, or people keep asking.
Zendesk analyzed 165 million intent-labeled tickets from paid accounts in Q2 FY26, last updated 7 October 2026, and found 49% of genuine service requests were repeatable tasks such as order status, account updates, and receipts. That is the neighboring ticket-center job. Zendesk and Intercom win a public help center for product support. The vacuum here is the five to ten repeating questions in a client Slack channel.
The buying prompt collapses five jobs: a client-facing FAQ where they already look, a saved reply so you stop retyping, a public help center for product tickets, a status list for open work, and a draft from knowledge that a person still sends. Internal unwritten rules belong on the preference sheet. Getting the whole book out of one head is on how to get client knowledge out when the account manager quits. Overnight coverage is on how agencies keep client Slack answered after hours. Open asks that sit overnight are on the daily summary of open client asks.
What belongs on the client FAQ
Write the questions you already answer from memory. Hamza Khurshid, writing 5 November 2026, starts with the last 30 questions and groups the recurring themes. On r/smallbusiness in February 2026, an owner wrote that 80% of questions were the same five things, hours, delays, pricing, delivery, and support, then saved short replies and added a pinned message. Intercom says an FAQ becomes a wall of text past 20 or 30 entries. Five to ten is the working set for a retainer client.
Put stable process on the shared canvas the client can see. Put landmines, who actually decides, and never send them a long recap on the internal twin. Those sentences belong on the preference sheet.
| Document | Include or leave out | Why |
|---|---|---|
| How to request work | Include | Where to post, what to attach, and who owns the first look. This is the line clients retype every month. |
| Where last week's report lives | Include | A Drive folder nobody can find is the reason they ping Slack. Put the link on the canvas they already open. |
| Who to ask for access | Include | Name the person who grants logins. The password itself stays in the password manager. |
| Reply hours and who to ping | Include | Mursa's rule is 4 business hours for standard client Slack, 1 business hour for urgent, next business day after hours. Put the same target in the channel description. |
| Revision process and meeting cadence | Include | How many rounds, where feedback goes, and when you meet. New stakeholders arrive with zero history without this line. |
| Link to current open work | Include | Point at the still-open list. The FAQ names where status lives. This week's dates belong on that list. |
| How invoices and billing questions work | Include | Who to email, when invoices go out, and what to do if a PO is missing. Keep pricing and margins off this page. |
| Passwords, API keys, and personal logins | Leave out | Name who grants access. Store secrets in the password manager. A canvas in Slack Connect is visible to everyone in the channel. |
| This week's changing status | Leave out | Any update goes stale the first time a deadline moves. That job is a current-work list, on the daily summary of open client asks. |
| Landmines, politics, and internal notes | Leave out | Those sentences are for the team. Put them on the internal preference sheet. A bot message in Slack Connect is visible to the client. |
| A 40-page SOP or a full Slack export | Leave out | On r/SideProject in March 2026, a 7-person shop running about 20 client apps found Notion docs, FAQ pages, and Gmail canned replies did not stick, because clients wanted to ask rather than search. One page they already open beats a handbook they skip. |
| Pricing, margins, and other-client work | Leave out | Mursa keeps those in the internal int- channel. The client needs the outcome. The sausage-making stays internal. |
Which method wins which job
Fund the row that matches the leak. A public help center, a saved reply, and a canvas FAQ are neighboring jobs.
| Job | Wins it | Why |
|---|---|---|
| Repeating answers where the client already looks | Slack canvas FAQ | Add a canvas as a tab on the client channel and show it by default. Five to ten questions. Canvases sit on paid Slack plans. |
| Paste the same answer without retyping | Intercom macros, or a Slack workflow the agency starts | Intercom macros insert a ready-made reply you still send. In Slack, a slash-command workflow your team starts can paste the same block. External people cannot start a keyword-triggered workflow, a custom-step workflow, or a connector step that needs their login. |
| A public help center for product support tickets | Zendesk or Intercom Help Center | Zendesk treats an FAQ as the first step toward a help center. Intercom says an FAQ is the right format under about 15 distinct questions, and a knowledge base once answers need steps and exceptions. That is the ticket-center row. |
| Auto-answer FAQs in an internal Slack channel | Slackbot custom responses, Channel Expert on a legacy install | Slackbot custom responses post in internal channels. Slack says they do not post in Slack Connect. Channel Expert cannot be added to channels with external organizations, and Slack stopped allowing new adds on 4 May 2026. |
| Status of open work | A current-work list | Pin a still-open list, or use the daily summary of open client asks. Recaps catch you up on yesterday. The queue is the still-open list. |
| Draft from knowledge a person still sends | Concrete | Drafts land as Send / Edit / Skip cards. There is no auto-send mode. Every incoming message gets a receipt mark. Design-partner preview; see what it is. |
| Judgment and the relationship | A person | The FAQ stores the stable answers. A named owner still says yes, handles the exception, and confirms a guessed line before it becomes a rule. |
The caveat that should decide the setup
Clients re-ask because the answer only matters at the moment they need it. That is the caveat the occupier pages already repeat. It was in the kickoff deck. It was in the welcome email. They still ping Slack the week the report is due, because that is when the question is live. Put the answer in the channel they already open, and keep a saved reply that points at it.
A Drive FAQ nobody opens is the first failure. On r/SideProject, a 7-person agency found Notion docs, FAQ pages, and Gmail canned replies did not stick. Intercom says an FAQ past 20 or 30 entries becomes a wall of text visitors scan without confidence. Five to ten questions, on the canvas shown by default, is the address.
A second failure is mixing knowledge with status. How to request work stays true. Any update changes this week. If the FAQ tries to be both, it is stale the first time a deadline moves. Zendesk's deflection page measures whether the issue was actually completed. A link that sends the client away from the queue still fails if they come back with the same ask. Zendesk also reports that 74% of consumers find repeating themselves frustrating.
A third failure is an unsupervised reply in Slack Connect. People in that channel can see messages from bots and apps. Slackbot custom responses do not post there. Channel Expert cannot be added there. External people cannot start keyword-triggered workflows. ClearFeed's agency guide says AI should not auto-send replies without review on complex work. 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. There is no auto-send mode. Every substantive answer is logged with the person's verdict, and the verdicts become written rules overnight, so a correction does not have to be repeated. Follow-ups survive reboots. Each morning it nudges the owner of every open task or ask. After downtime it sweeps channel history, thread replies included. It is in design-partner preview; the longer thesis is on the vision page. How to run an agent in a shared channel is on using an AI agent in a Slack channel shared with a client. Drafting the client-facing reply is on the approval-before-send page.
Step by step: pin the answers where the client already looks
This is the boring version that holds when the owner is still the account manager for most clients. Pin it during onboarding, before the fifth time someone asks where last week's report lives.
- Step 1: Pull the last 30 questions. Open the client channel and the last month of email. Write every repeating ask on one page. Hamza Khurshid groups those into recurring themes. You are hunting the five to ten that actually repeat.
- Step 2: Write short answers in the client's words. If they type where is the report, the heading is where is the report. Intercom's rule is to pull questions from real conversations. Two to five sentences each. Link out if a step-by-step lives in Drive.
- Step 3: Pin the FAQ on the Slack canvas, shown by default. Add the canvas as a tab on the shared client channel. Right-click the tab and select Show canvas by default. Put how to request work, report links, reply hours, and who to ping there. Put landmines on the internal twin.
- Step 4: Keep a saved reply that points at the canvas. One block you paste, with the canvas link, for the people who still ping. In Intercom that is a macro you still send. In Slack it is a note or a workflow your team starts. The client gets the answer in the thread they opened.
- Step 5: Write the reply target into the channel. 4 business hours standard, 1 business hour urgent, next business day after hours. Put it in the channel description and on the canvas. Point at the FAQ in the first reply. Acknowledgment still counts as the first response.
- Step 6: Keep status on a current-work list. Pin what is open this week, or use a morning list of still-open asks. When the client types any update, send the list. Leave that line off the FAQ so the FAQ stays true.
- Step 7: Update the same day a rule changes, and keep send as a tap. A new report folder, a new revision round, a new owner. A stale canvas is the one a new hire will follow. Draft if you want speed. Send stays a tap. A bot message in Slack Connect is visible to the client.
Questions people ask
Why do clients keep asking things I already covered in the kickoff?
Clients re-ask because the answer only matters when they need it, often weeks after kickoff. Put the canvas where they already open Slack. Write the five to ten questions that actually repeat, pin them, and keep a saved reply that points at the same page.
Should a small agency build a Zendesk help center for client questions?
Zendesk and Intercom win a public help center for product support tickets. Zendesk analyzed 165 million tickets and found 49 percent of genuine requests were repeatable. A 3-to-30 person shop answering how to request work in Slack Connect needs a canvas FAQ and a saved reply.
What is the difference between an FAQ and a status update in Slack?
An FAQ holds answers that stay true for months: how to request work, where reports live, who to ping. A status update answers what is open this week. Pin the FAQ on the canvas. Put current work on a still-open list. Mixing them makes the FAQ stale the first time a deadline moves.
Can I auto-reply to FAQs in a Slack Connect client channel?
Slackbot custom responses do not post in Slack Connect. Channel Expert cannot be added to channels with external organizations, and Slack stopped allowing new Channel Expert adds on 4 May 2026. External people also cannot start keyword-triggered workflows. Keep a person on send.
Where should a client FAQ live if we already work in Slack?
Pin a Slack canvas on the shared client channel, shown by default. Canvases sit on paid Slack plans. Put how to request work and reply hours there. Put landmines on the internal twin. People in Slack Connect can see messages from bots and apps.
How many questions belong on a client FAQ?
Intercom says an FAQ becomes a wall of text past 20 or 30 entries. On r/smallbusiness, one owner wrote that 80 percent of questions were the same five things. Start with five to ten that actually repeat. Add a line the week it repeats twice.
How fast should we reply if the answer is already on the canvas?
Write 4 business hours for standard Slack, 1 business hour for urgent, and the next business day after hours. Point at the canvas in the first reply. Acknowledgment still counts as the first response. The saved reply is how you hit the clock without retyping.
Sources
- Slack pricing, read November 10, 2026
- Slack Connect guide: Work with external organizations, read November 10, 2026
- Use a canvas in Slack, read November 10, 2026
- An introduction to Slackbot, read November 10, 2026
- Set up and manage Channel Expert (legacy), read November 10, 2026
- Manage workflow usage in Slack Connect conversations, read November 10, 2026
- Sakas and Company: How many accounts can one AM handle, read November 10, 2026
- Databox: Account manager burnout, how many clients are too many, read November 10, 2026
- Mursa: Slack for clients, manage communication and scope, read November 10, 2026
- ClearFeed: Slack for client communication, a complete guide for agencies, read November 10, 2026
- Asana: How work about work gets in the way of real work, read November 10, 2026
- Zendesk: What 165 million tickets reveal about customer service, read November 10, 2026
- Zendesk: Creating an FAQ page, read November 10, 2026
- Zendesk: Ticket deflection vs resolution, read November 10, 2026
- Intercom: FAQ vs knowledge base, read November 10, 2026
- Intercom: Using macros in the Inbox, read November 10, 2026
- Kognetiks: If clients keep asking the same questions, it is not a client problem, read November 10, 2026
- r/smallbusiness: How do you handle replying to the same customer questions every day, read November 10, 2026
- r/SideProject: How I stopped answering the same 5 support questions every day, read November 10, 2026
- Hamza Khurshid: 4 steps to stop answering the same Slack questions, read November 10, 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.