AGENT SKILL

client-comms-cadence

Design an agency's client communication operating system - a channel contract per client tier, the weekly pulse / monthly report / quarterly QBR ladder, same-business-day response SLAs, the no-surprises rule for bad news, and internal escalation triggers. Use when an agency owner says "clients keep asking what we're working on", "every client pings us on a different channel at all hours", "we got fired and never saw it coming", or "my team is drowning in client Slack messages". Do NOT use for planning the content of the monthly report itself - use agency-monthly-report instead.

License 许可
MIT
所属仓库
SkillMedev/skills
最近更新
2026-10-14
Stars
★ 25
Forks
3

01 前言 Front Matter

name
client-comms-cadence
description
Design an agency's client communication operating system - a channel contract per client tier, the weekly pulse / monthly report / quarterly QBR ladder, same-business-day response SLAs, the no-surprises rule for bad news, and internal escalation triggers. Use when an agency owner says "clients keep asking what we're working on", "every client pings us on a different channel at all hours", "we got fired and never saw it coming", or "my team is drowning in client Slack messages". Do NOT use for planning the content of the monthly report itself - use agency-monthly-report instead.

03 SKILL.md 正文

Client Comms Cadence

Agencies rarely get fired for bad work; they get fired for silence. The client who "never hears from you" mentally cancels the retainer months before procurement does, and the costly mistake this skill prevents is reactive communication - answering whatever arrives, on whatever channel, whenever - which reads to the client as chaos and burns the team out. A communication cadence is a contract: the client knows exactly when they will hear from you, so they stop wondering whether the retainer is working.

Work the example agency throughout: Northbeam Digital, an 8-person marketing agency with 11 retainer clients averaging $6,500/month and a 62 percent gross margin target.

Operating procedure

Set tiers first, then channels, then the ladder - the cadence a client gets is a function of what they pay, and per retainer-economics-calculator, account manager communication time is delivery cost, so over-communicating with a small retainer destroys its margin.

Step 1: Tier the client book

Split clients into two or three tiers by retainer size and strategic value. Northbeam uses two: Tier A at $7,000/month and up (5 clients: Crestline SaaS, Verra Health, Pillar Home, Onyx Fitness, Bluepine Outdoors), Tier B below (6 clients). Tiering is internal; clients see their own contract, never the tier list.

Check the load while tiering: one account manager can properly run roughly 8-10 retainer accounts on this cadence - fewer if the book skews Tier A, since the weekly call alone adds 30 minutes per client per week. An AM carrying 14 accounts will skip pulses under load, and skipped pulses are the exact silence this system exists to prevent.

Step 2: Write the channel contract per tier

One primary channel per client, agreed in writing at onboarding (route onboarding itself to client-onboarding-system). The contract names: the channel, who answers, the response SLA, and the escalation path for genuine emergencies.

Budget the cost of the contract before signing it: communication and account management should run about 10-15 percent of a retainer's delivered hours. Past 20 percent, the comms load is eating the work the client is actually paying for - at Northbeam's 62 percent gross margin target, a $4,000/month Tier B client getting Tier A treatment goes underwater on AM time alone.

  • Tier A: shared Slack channel, weekly 30-minute call, monthly report call, quarterly QBR.
  • Tier B: email as primary, biweekly 20-minute call, monthly report by email with a call on request, quarterly QBR.
  • Response SLA for both tiers: same business day for any message received before 3pm, next business morning otherwise. Same business day is the practitioner standard for retainer work - under an hour is a pager, not an agency, and pricing does not support it.
  • Emergencies (site down, ad account suspended, public brand issue): phone the account manager, 2-hour response, any day.

Step 3: Install the cadence ladder

Three rungs, each answering a different client question:

  1. Weekly pulse - "are they working?" A 5-bullet async update, sent the same weekday every week: what shipped, what is in progress, what is blocked and by whom, one number, what is next. Ten minutes to write, under 200 words to read - if it takes longer to produce or reads like a report, it will be skipped under load. Never skip it in a bad week; a skipped pulse in a bad week is exactly the silence that kills accounts.
  2. Monthly report - "is it working?" Results against goals, owned by agency-monthly-report. Same delivery date every month (Northbeam: fifth business day).
  3. Quarterly QBR - "should we continue and expand?" Owned by agency-qbr-upsell.

Each rung has one named owner. At Northbeam, the account manager owns the pulse and the report draft; a founder joins every QBR.

Step 4: Enforce the no-surprises rule

Bad news travels first and fast: the client hears about a miss, an overspend, a delay, or a mistake from the agency before they could discover it themselves, within one business day of the agency knowing. Deliver it with the three-part frame - what happened, what the impact is in their numbers, what is already being done. A client told early about a problem sees a professional; a client who finds it in the monthly report sees a cover-up. Never let the monthly report be the first mention of a problem.

Step 5: Set internal escalation triggers

The account manager escalates to the owner, same day, when any of these fires. These same signals feed the early-warning ranking in client-churn-save - escalating here is what makes a save possible there.

  • Client response rate drops: two consecutive pulses with no reply or reaction from a client who used to engage.
  • A standing call is skipped or cancelled twice in a row by the client side.
  • "Budget review," "procurement," "re-evaluating vendors," or a competitor's name appears in any message.
  • The champion (day-to-day contact) goes quiet, changes roles, or leaves.
  • Any missed SLA on the agency side, or any bad news that has not yet been delivered to the client.

Inputs to collect

  • Client list with retainer sizes (from retainer-economics-calculator).
  • Current channels in actual use per client, and where the sprawl is worst.
  • AM hours actually spent on communication per client; if untracked, label the estimate a guess.
  • Any contractual communication promises already made.

Worked artifact: channel contract template

Send at onboarding, per client:

COMMUNICATION AGREEMENT - [FILL: client name] x Northbeam Digital

Primary channel:      [FILL: shared Slack channel / email]
Who answers:          [FILL: AM name], backed by [FILL: backup name]
Response time:        Same business day (received before 3pm); next morning otherwise
Emergencies:          Call [FILL: AM phone]. 2-hour response, any day.
                      Emergency = site down, ad account suspended, public brand issue.

What you'll hear from us:
  Weekly (every [FILL: weekday]):  5-bullet progress pulse
  Monthly (5th business day):      results report [FILL: + 30-min call, Tier A]
  Quarterly:                       business review (60 min, [FILL: founder name] attends)

Our commitment: if anything goes wrong, you hear it from us first -
within one business day of us knowing.

Deliverable

A one-page comms operating system: the tier list with each client assigned, the channel contract per tier ready to send, the cadence ladder with a named owner and fixed day for each rung, and the five internal escalation triggers posted where the delivery team works.

Do NOT

  • Do not promise an SLA the team cannot staff - a broken same-day promise is worse than an honest next-day one.
  • Do not let every client pick a bespoke channel; channel sprawl is how messages get missed and SLAs silently break.
  • Do not give Tier B clients Tier A cadence out of guilt - AM time is delivery cost, and unpriced communication is margin leak.
  • Do not sit on bad news until the monthly report; the no-surprises rule exists because discovered problems end retainers and disclosed problems build trust.
  • Do not treat a skipped client call as a scheduling accident twice in a row - it is a churn signal; escalate per client-churn-save.

Quality bar

  • Every client has exactly one primary channel, one named AM, and a written SLA.
  • Every rung of the ladder has an owner and a fixed calendar day.
  • The escalation triggers are specific and observable (countable events, not "seems unhappy").
  • The weekly pulse takes 10 minutes or less to produce, or it will be skipped under load.

Escalation and neighbors

Install after retainer-economics-calculator (tiers follow margin and retainer size). The monthly rung is produced by agency-monthly-report; the quarterly rung by agency-qbr-upsell; fired triggers route to client-churn-save. New-client setup, including the channel contract signing, belongs to client-onboarding-system.

04 同仓库更多 Skills

SkillMedev
SkillMedev/skills

有氧运动计划

zone-2-cardio-plan

当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练,或提高静息心率、最大摄氧量或耐力时,可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导,不构成医疗建议。请勿用于设计力量或举重训练计划(请使用力量训练计划)、高强度间歇训练 (HIIT) 或循环训练(请使用体能训练和 HIIT 计划),或灵活性/柔韧性训练(请使用灵活性训练计划)。

★ 25
SkillMedev
SkillMedev/skills

youtube-script-writer

Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.

★ 25
SkillMedev
SkillMedev/skills

win-back-campaign

Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.

★ 25
SkillMedev
SkillMedev/skills

wikipedia-style

Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.

★ 25
SkillMedev
SkillMedev/skills

whitepapers

Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.

★ 25
SkillMedev
SkillMedev/skills

white-space-analysis

Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.

★ 25