Guide
How do I document client preferences so the whole team knows them?
You document client preferences so the whole team knows them by writing a one-page preference sheet per account and pinning it on the internal Slack canvas of that client's channel. Include how they like to be talked to, who actually decides, standing exceptions, recap length, and landmines. A CRM contact form that says they prefer email is a neighboring job. A 40-page SOP in Drive is a document nobody opens.
By The Concrete team · Published
We make Concrete.
What the job actually is
You document client preferences so the whole team knows them by writing a one-page preference sheet per account. How they like to be talked to. Who actually decides. Standing exceptions. Recap length and report format. Landmines. Pin that sheet on the internal Slack canvas of the client's channel, shown by default. The designer, the media buyer, and the freelancer open that page instead of pinging the account manager.
The account manager is still in the building. The leak is that every preference still lives in one head, so the rest of the shop waits. Monday.com's client information sheet treats this as contact details, billing, and whether they prefer email, phone, or text. That form is useful. It is not the sentences the account manager already says to themselves while they work the account.
Agencies run the work 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. Keep the shop's preference sheet off the thread the client can read.
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 extra ping of how does this client like to be talked to comes out of those 20 hours.
Write a reply target into the channel and onto the sheet. 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. monday.com's 2024 world of work report, cited on its client information sheet, found 57% of employees reported an increase in the number of software platforms used compared with the previous year. The preference sheet has to live where the team already is, or people keep asking.
The buying prompt collapses four jobs: a CRM form the client fills, a team-facing preference sheet, a company handbook, and a rule learned from a rejected draft. Getting the whole book out of one head after someone quits is a neighboring job, on how to get client knowledge out when the account manager quits. Corrections that stick are on the agent that learns from Slack corrections. Decisions written out of a thread are on how founders keep track of Slack-thread decisions.
What belongs on the preference sheet
Write the sentences you already say to yourself while you work the account. Wiro names the layer that walks out of one head: the approver who hates emojis, the brand manager who wants to see everything before their director does, the color the client will never accept. On r/CustomerSuccess in May 2026, operators said the layer that costs the most time is the stuff that never gets documented, and they ask three questions: who really makes decisions here, who needs extra handling and why, and what would you tell me in the first five minutes of a call.
Rock puts a client brief at one page for a simple engagement and two pages for a complex one, and says a brief longer than three pages will not get read. File Request Pro says fifteen fields cover most service businesses, and that a form past twenty-five fields is collecting data nobody uses. The ICO's data minimisation principle says personal data must be adequate, relevant, and limited to what is necessary for the purpose. Billing contacts and tax IDs belong on the intake form. They do not belong here.
| Document | Include or leave out | Why |
|---|---|---|
| How they like to be talked to | Include | Recap length, emoji, who sees the draft before their director, the color they will never accept. Wiro names these as preferences nobody recorded. |
| Who actually decides, and who is day-to-day | Include | The person who pings Slack may not sign the retainer. On r/CustomerSuccess, operators said who really makes decisions is the line that saves the next person the most time. |
| Standing exceptions | Include | Who hates Monday calls. Which CMO wants a one-line summary. Which account has a standing exception on revisions. A new designer arrives with clean process and zero history without this line. |
| Reply-time target and meeting cadence | 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. |
| Recap length, report format, approval path | Include | Weekly deck or a three-line Slack update. Who signs off before it goes to their boss. Rock's working-agreement section is this row: if it is missing, new people default to their own habits. |
| One example they like, one they dislike, and why | Include | Sourav Mahapatra, writing 10 November 2026: ask for one example the client likes and one they dislike, then record the reasons in the brief rather than relying on the examples alone. |
| Landmines, politics, ongoing frustrations | Include | Why the last campaign was pulled. Which competitor they are sensitive about. What went wrong with the previous agency. The first five minutes of a call. |
| Named owner of the sheet, with an author and a date on each line | Include | Thierry Templier, writing 10 November 2026: a preference one of them guessed ends up reading like one you stated. An author and a date on each line let the next person tell which ones you would still sign. Rock wants a named owner on the brief itself. |
| Contact, billing, tax ID, payment terms | Leave out | That is the CRM and the invoice. Monday.com and File Request Pro win those fields. Mixing them with landmines makes a form nobody finishes and a sheet nobody trusts. |
| A full Slack export of the channel | Leave out | Search finds the thread if you remember a phrase. The next person on the account will not read 18 months of scrollback before the first client ping. |
| A process encyclopedia or 40-page SOP | Leave out | On r/agencynewbies, an owner who spent weekends on SOPs, Notion databases, and Loom videos found nobody used any of it. Finding the doc took longer than asking. |
| Brand bible, contracts, and invoices already on the drive | Leave out | Point to them. The sheet stays one page. Monday.com's creative-agency template can hold brand assets and approval process as a form. The preference sheet is the unwritten rules around those files. |
Which method wins which job
Fund the row that matches the leak. A CRM form, a client-filled onboarding sheet, and a one-page team brief are neighboring jobs.
| Job | Wins it | Why |
|---|---|---|
| Get the unwritten rules onto one page the team will open | One-page preference sheet | Write how they like to be talked to, who decides, exceptions, recap format, and landmines. One page per client. The sentences you already say to yourself. |
| Contact, billing, consent, and prefers email | Client information sheet | Monday.com and File Request Pro win the form the client fills: names, billing, payment terms, preferred contact method. That is intake. It is not the team brief. |
| The client fills onboarding fields once | A Client Information Document | On r/agency in July 2024, an operator issued a Google Sheet they called a CID, shared with the client to fill out, then updated when things changed. That is input. Someone still has to write the team-facing page. |
| A durable document in the internal channel | Slack canvas | Add a canvas as a tab on the internal twin of the client channel. Right-click the tab and select Show canvas by default. Canvases sit on paid Slack plans. Keep landmines off Slack Connect. |
| A team-facing brief pinned next to the work | Rock-style client brief | Rock wants the brief in the shared client workspace, pinned, one to two pages, with a named owner. It says a brief in a private Drive folder or a Notion page nobody else can find is the same information with worse access. |
| A company-wide wiki of how we work | Confluence or Notion | Atlassian's SSoT guide is the address for processes, templates, and brand guidelines used by every team. A preference sheet is one page per client, not a second handbook. |
| Personal writing-style memory | Slackbot | Slackbot memory saves preferences such as writing style from your conversations, checking weekly. Personal, not shared. A rejected client draft becoming a team rule is a different job. |
| A rule from a rejected or edited draft, a person still sends | Concrete | Every substantive answer is logged with the person's verdict, and the verdicts become written rules overnight. Send / Edit / Skip cards; no auto-send mode. Design-partner preview; see what it is. |
| Judgment, the live call, and the relationship | A person | Software stores the sheet. The client still needs a named owner who can say yes, and who confirms a guessed preference before it becomes a rule. |
Where the sheet has to live
The whole team knows the preferences when the sheet is the first thing they see in the channel they already open. Rock's line is the one to pin: the agencies that struggle run the brief in email, a private Drive folder, or a Notion page nobody else knows how to find. The information is as good. The access is not.
Mursa pins a canvas on every client channel with team contacts, response times, key links, and a decision log. That canvas is the first thing the client sees. Put response times and who to contact there. Put landmines, who actually decides, and never send them a long recap on the internal twin, named int- in Mursa's convention, with Show canvas by default. A bot message in Slack Connect is visible to the client.
Erin James Murphy, writing 20 August 2026, described a PR shop that had spent eight months getting client preferences, quirks, and relationship context into structured account briefs on a shared drive. When the best account manager left, a new one was fully operational on those accounts within six weeks. The briefs existed before the resignation. The sheet you write this week is the one the freelancer opening the channel on Thursday can use.
On r/PPC, one media lead's test for a brief was whether someone else could pick up the page and still execute if the client, the account person, and the media lead were all gone. Keep it one page. Rock says a good brief takes 30 to 45 minutes if you already have the sales notes and the questionnaire, and 3 to 4 hours if you do not. Karl Sakas puts a dedicated account manager at 4 to 8 accounts. That is a handful of pages, not a wiki rebuild.
The caveat that should decide the setup
The failure shops name first is a form that looks complete and still leaves the team asking. Monday.com and File Request Pro collect preferred contact method, meeting format, and billing. Guides that answer this prompt often start with a single source of truth and a client information sheet. Those pages occupy the intake row. The vacuum is the unwritten rules: never send them a long recap, hates Monday calls, CMO wants one line, the color they will never accept.
The second failure is a wiki dump nobody opens. Operators on r/agencynewbies spent weekends on SOPs, Notion, and Loom. Nobody used any of it. The docs were too long. Finding them took longer than asking. One page, in the internal channel, shown by default, is the address. Eighteen months of scrollback stays unread.
The third failure is putting the shop's internals in Slack Connect, or dumping the channel into an AI and calling that the record. People in that channel can see messages from bots and apps. A digest of landmines in the shared thread shows the client your private notes. Treat an AI extract as a draft. On r/CustomerSuccess, operators let AI pull raw material, then made a person confirm five fields: what they care about, recent promises, real stakeholders, next action, and landmines. A half-joking never send them a long recap can read like a real rule. Thierry Templier's test is an author and a date on each line, so a guessed preference does not look like one you stated.
A stale sheet is worse than a missing one. Rock updates after kickoff, when a stakeholder changes, and at the 30-day review. The ICO's data minimisation checklist includes a periodic review, and deleting what you no longer need. Update the sheet the same day a rule changes. Outdated context is what a new hire will follow with confidence.
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 starts from a ready-made role such as Customer Success or Chief of Staff, then adapts. It is in design-partner preview; the longer thesis is on the vision page. It does not write the preference sheet for you. The sheet still needs a page. Concrete keeps the work that page created. 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: write the preference sheet the team will open
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 freelancer has to ask how this client likes to be talked to.
- Step 1: Write the sentences you already say. How they like to be talked to. Who actually decides. Standing exceptions. Recap length and report format. Reply target. One like and one dislike, with reasons. Landmines. Finish the lines you already use: never send them, every month I have to remember to, if this is missing I.
- Step 2: Keep it one page. Rock: one page for a simple engagement, two for a complex one. Past three pages it will not get read. Point at the brand bible and the contract. Do not paste them. File Request Pro's fifteen-field cap is the same instinct on the intake side.
- Step 3: Pin it on the internal canvas, shown by default. Add the canvas as a tab on the internal twin, not the Slack Connect channel. Right-click the tab and select Show canvas by default. Mursa's naming is int- for the internal channel and client- for the shared one. A group in the channel recreates the bystander effect, so name one owner of the sheet.
- Step 4: Put an author and a date on every line. A preference one of you guessed reads like one the client stated. Write who recorded it and when. Rock wants a named owner on the brief. Transfer that ownership when the account lead changes, with a read-through, the same day.
- Step 5: Write the reply target into the channel and the sheet. 4 business hours standard, 1 business hour urgent, next business day after hours. Put it in the channel description so the client sees the working agreement, and on the internal sheet so the team sees the same clock.
- Step 6: Update the same day a rule changes. A new stakeholder, a new report format, a new never send them. Rock's three triggers are kickoff, a stakeholder change, and the 30-day review. A stale line is the one a new hire will follow. Open asks that sit overnight are a neighboring job, on the daily summary of open client asks.
- Step 7: Keep send as a tap. Draft the recap if you want speed. Send stays a tap. A bot message in Slack Connect is visible to the client. Treat an AI extract of the channel as a draft. A named owner still confirms who decides, the last exceptions, and the landmines.
Questions people ask
What should go on a client preference sheet for an agency team?
Write how they like to be talked to, who actually decides, standing exceptions, recap length and report format, the reply target, one like and one dislike with reasons, and the landmines. Karl Sakas puts a dedicated account manager at 4 to 8 accounts. That is a handful of pages, not a handbook.
Is a CRM client information sheet enough for the whole team?
It wins contact, billing, consent, and whether they prefer email or a call. Monday.com and File Request Pro occupy that row. The team still needs the unwritten rules: who hates Monday calls, which CMO wants one line, the color they will never accept. Those sentences live on a separate one-page brief.
Where should we keep client preferences so people actually open them?
Pin a one-page canvas on the internal Slack channel, shown by default. Rock says a brief in a private Drive folder or a Notion page nobody can find has the same information with worse access. Asana found workers spend 60% of time on work about work.
Should the preference sheet live in the Slack Connect channel with the client?
Put response times and who to contact on the shared canvas the client can see. Put landmines, who actually decides, and never send them a long recap on the internal twin. People in a Slack Connect channel can see messages from bots and apps. A private note in the shared thread is not private.
Can I dump Slack threads into an AI and call that the preference record?
Use the model as a draft. On r/CustomerSuccess, operators let AI pull raw material, then made a person confirm what they care about, recent promises, real stakeholders, next action, and landmines. A half-joking never send them a long recap can read like a real rule. Put an author and a date on each line.
How often should we update a client's preference sheet?
The same day a rule changes, and at kickoff, a stakeholder change, and the 30-day review. Rock treats the brief as a living note, not a launch document. The ICO's data minimisation checklist includes a periodic review, and deleting what you no longer need. A stale line is the one a new hire will follow.
How is a client preference sheet different from a client brief?
Rock's client brief covers snapshot, outcome, metrics, stakeholders, scope, timeline, brand assets, risks, and working agreement. The preference sheet is the working-agreement row written as sentences: how they like to be talked to, exceptions, landmines. Keep it one page so a freelancer opening the channel on Thursday can use it.
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
- Build your Slackbot memory, read November 10, 2026
- Sakas & 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
- monday.com: Client information sheets templates, examples, and best practices, read November 10, 2026
- File Request Pro: Client information sheet template, what to include, read November 10, 2026
- Rock: Client brief template, 9 sections you can copy, read November 10, 2026
- Atlassian: Building a true Single Source of Truth for your team, read November 10, 2026
- ICO: Principle (c), data minimisation, read November 10, 2026
- Wiro: Handing over a client when someone leaves, read November 10, 2026
- r/agency: What info we collect on clients during onboarding, read November 10, 2026
- r/agencynewbies: How we finally killed the founder bottleneck, read November 10, 2026
- r/CustomerSuccess: Best practices for CSM account handover, read November 10, 2026
- r/PPC: What info is crucial in every brief, read November 10, 2026
- Erin James Murphy: structured account briefs before the AM left, read November 10, 2026
- Thierry Templier: author and date on each preference line, read November 10, 2026
- Sourav Mahapatra: one like, one dislike, record the reasons, 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.