Client Reply Voice Guide — Nora Reference

Purpose: How Kathryn replies to client emails. Use this when drafting any reply on Kathryn's behalf — acknowledgments, quick follow-ups, status responses, pre-session confirmations.

This is NOT the advisory email skill. The advisory email skill (advisory-client-email-SKILL.md) covers post-session strategic communications. This guide covers everything else — the short, everyday replies that make up 80% of client correspondence.

Source: Derived from Kathryn's sent mail (May 2026) across multiple clients — Nicole Albrecht, Jenn Barr, Ruben Cruz, Christi Bender. Patterns confirmed by Kathryn.

The Pattern

Every client reply follows the same 4-beat structure. Most replies are 3-6 lines.

Beat 1: Acknowledge what they sent

Name the specific thing. Not "thanks for your email" — what did they actually give you?

• "Thanks for sending the pre-work over."
• "Got your recording — thank you!"
• "You're very welcome."

Beat 2: Appreciate or validate specifically

What was good about it, or what it means for the work. One sentence.

• "I appreciate the detailed answers — it gives us a strong starting point."
• "90 minutes walking through every dimension of the Phase 3 engagement, and most of it is ready to go straight into the proposal."

Beat 3: State what happens next

Clear, simple. The client should know exactly where things stand.

• "I have everything I need for our June 2 session."
• "Let me know once you've scheduled a follow-up conversation."
• "Here's the link to restart the monthly payment. I've canceled the current one."

Beat 4: Open door + close

One line offering help, then sign off. Always the same close.

• "Let me know if anything comes up before then."
• "If I can be of any help, just let me know."
• "Let me know if you have any questions!"

Close: "Talk soon, Kathryn" — every time.

Voice Rules

Short sentences. One idea per line. Line breaks between thoughts.

Dashes for quick replies: "Hi Nicole --" (double hyphen). Em dashes (—) in longer, more composed emails.

One exclamation mark max. Usually on the thank-you line. Never two in a row.

Confidence without pressure. "I have everything I need" — not "Once you send X, I can start." States the reality and trusts the client.

Forward-looking energy, not hype. "Looking forward to digging in and seeing us move the needle." Not "I'm so excited to get started!" or "This is going to be great!"

No filler. Never: "Just wanted to," "I was thinking," "I hope you're well," "I hope this finds you."

No coaching language. Never: "I hear you," "That's a great question," "I'm proud of how you handled that," "Great job," "I'm so impressed."

No summarizing their email back to them. They wrote it. They know what they said. Acknowledge the delivery, not the content.

No unnecessary follow-up questions. If you have what you need, say so. Don't manufacture engagement by asking questions you don't need answered.

Before You Draft

Read the engagement context first. Before drafting any reply, read the client's active engagement — what Kathryn is working on with them, what's been discussed, what's coming up. Every reply exists inside an engagement. A casual question about tools becomes an advisor directive when you know Kathryn delivers AI deployment as part of her consulting practice. A vague "how's it going" becomes a constraint signal when you know the client's CPM.

Every reply is an engagement moment. Even a 4-line acknowledgment reinforces the relationship — that Kathryn is tracking, prepared, and in command. The reply isn't just answering a question; it's demonstrating that the engagement is active and valuable.

Surgical edits, not structural rewrites. When Kathryn edits a draft, find the specific phrase she changed and understand why — don't rewrite the whole email. One phrase does different work than another. "I have a lot to share" positions Kathryn as an information source. "It's something I work on directly with my clients" positions her as a practitioner who delivers this as a professional service. The difference is one clause.

Length Guide

Default: If the reply doesn't need substance (bullets, links, decisions), keep it under 6 lines.

What Kathryn Does NOT Do in Replies

• Repeat back what the client said in her own words
• Add context the client already has
• Ask follow-up questions she doesn't need answered
• Use "I'm excited," "I can't wait," or emotional amplifiers
• CC anyone without a reason
• Use sign-offs like "Best," "Warmly," "Cheers," "All the best"
• Add postscripts or "P.S." lines
• Include her full email signature in short replies (just "Kathryn")
• Reference the engagement terms, pricing, or contract language
• Over-explain what happens next — one sentence, not a timeline

Greeting Format

Golden Examples (from Kathryn's sent mail, May 2026)

Example 1: Acknowledging substantive client input (Nicole — pre-work reply)

Hi Nicole -- thanks for sending the pre-work over.

I appreciate the detailed answers -- it gives us a strong starting point.

I have everything I need for our June 2 session.

Looking forward to digging in and seeing us move the needle.

Let me know if anything comes up before then.

Talk soon,
Kathryn

Why it works: Acknowledges (pre-work), appreciates specifically (detailed answers), states impact (strong starting point), confirms next step (June 2), forward energy (move the needle), open door, close. Six lines. No fluff.

Example 2: Quick follow-up when client shared new info (Jenn — retro reply)

Hi Jenn -- you're very welcome. Let me know once you've scheduled a
follow-up conversation. I'll be curious to know what changed between
last week and the retro.

If I can be of any help, just let me know.

Talk soon,
Kathryn

Why it works: Acknowledges (you're welcome), directs next step (schedule follow-up), shows she's tracking the situation (what changed), open door, close. Doesn't ask about Kim/Rita/Susan by name — doesn't probe. Trusts Jenn to bring it when ready.

Jenn-specific tone lesson (from May 28, 2026 proposal update reply): With Jenn, lean warm and human — not analytical. Kathryn's edits to the drafted reply: cut "That's good instinct" (don't evaluate her decisions), added :) (lighter than explaining), added "Hang in there!" (personal warmth). The pattern: Jenn doesn't need her advisor grading her judgment ("smart call," "good instinct," "right read"). She needs to feel Kathryn is in her corner. Short human touches (:), "hang in there") do more than validated analysis. Don't over-explain — one line of warmth beats two lines of reasoning.

Example 3: Sending a resource (Ruben — payment link)

Hi Ruben -- here's the link to restart the monthly payment. I've
canceled the current one.

[link]

Let me know if you have any questions!

Talk soon,
Kathryn

Why it works: States what it is, confirms what she's done on her end, link, open door, close. Three lines of actual content.

Example 4: Expertise/opinion request (Nicole — Claude vs. ChatGPT)

Hi Nicole -- great question.

I'm all in on Claude. It's what I use to run my own practice -- client
prep, session follow-up, content, operations. It's significantly better
than ChatGPT for the kind of thinking advisory and accounting firms
actually need.

We'll dig into this as part of our work together -- AI readiness was one
of your EntreLeadership priorities, and it's something I work on directly
with my clients. Hold off on any AI decisions or subscriptions until we
talk -- I want to make sure we set it up the right way for your team and
business.

Short answer for now: yes, I will want you to switch to Claude. I'll
show you why (and how I recommend we do it) on June 2.

Talk soon,
Kathryn

Why it works: Acknowledges (great question), states position clearly (all in on Claude), shows credibility through specifics (client prep, session follow-up, content, operations), connects to their engagement (EntreLeadership priorities), claims the domain ("I work on directly with my clients"), protects from premature action ("hold off"), uses advisor directive language ("I will want you to"), and gives forward hook (June 2). Doesn't over-explain what Claude is — Nicole already knows. Doesn't ask follow-up questions — Kathryn has what she needs. Elevates a casual question into evidence of the engagement's value.

What makes expertise/opinion replies different: The 4-beat pattern still applies, but Beat 2 shifts from appreciation to credibility — you're showing your position through what you actually do, not validating what they sent. The key move is connecting their question to the work you're doing together. Answer directly, don't hedge, don't teach — you're the expert, they asked you.

Direct and protect: When a client is about to make a decision that falls in Kathryn's domain, the reply doesn't just answer — it holds the client from acting prematurely. "Hold off on any AI decisions or subscriptions until we talk" prevents Nicole from spending money or making tool choices before Kathryn can direct the approach. This is advisor authority: the client asked because they trust your judgment, so use it — direct them clearly AND protect them from wrong moves between now and when you can guide them properly. "I will want you to" is an advisor directive, not a suggestion. "Switch to Claude" is peer advice.

When This Guide Does NOT Apply

• Post-session advisory emails — use advisory-client-email-SKILL.md
• Session recap emails — use the session recap skill
• Pre-work or intake emails — these are outbound with structure/questions, not replies. Follow the pre-work email pattern (see Nicole pre-work email as reference).
• Formal proposals or SOWs — different format entirely

Created: 2026-05-27 | Updated: 2026-05-28 | Source: Kathryn's sent mail analysis (Nicole Albrecht, Jenn Barr, Ruben Cruz, Christi Bender). Example 4 updated with final approved Nicole "claude" reply. "Before You Draft" and "Direct and protect" sections added from same exercise. Jenn tone lesson added from May 28 proposal update reply edits.