# Client Communication

> Friendly, professional communication templates for WordPress clients. Use when writing documentation, responding to support requests, explaining technical concepts, or delivering project updates.

- Skill: `majiayu000/client-communication` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/client-communication`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/client-communication/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/client-communication

---


# Client Communication Skill

Professional yet warm communication templates for WordPress agencies and freelancers.

## Communication Principles

### The 3 F's

1. **Friendly** - Warm, approachable, human
2. **Focused** - Get to the point, respect their time
3. **Forward** - Always provide next steps

### Voice Guidelines

| Do | Don't |
|----|-------|
| "Happy to help!" | "As per my previous email..." |
| "Great question!" | "Obviously..." |
| "Let me explain..." | "It's simple, just..." |
| "I understand the frustration" | "That's not how it works" |
| "Here's what we can do" | "We can't do that" |

## Support Response Templates

### Initial Response

```markdown
Hi [Name]! 👋

Thanks so much for reaching out! I completely understand what you're looking for.

[Acknowledge their specific question/issue]

Here's what I'd suggest:

1. [First step]
2. [Second step]
3. [Third step]

[Screenshot or visual if helpful]

Let me know if this helps, or if you have any questions along the way. I'm here to help! 😊

Best,
[Your name]
```

### Bug Report Acknowledgment

```markdown
Hi [Name],

Thanks for reporting this! I really appreciate you taking the time to let us know.

**What I understand:**
[Summarize the issue in your own words]

**What I'm doing:**
- I've reproduced this on my end ✅
- I'm investigating the cause now
- I'll update you within [timeframe]

**In the meantime:**
[Any workaround if available]

Thanks for your patience! I'll get this sorted for you. 🔧

Best,
[Your name]
```

### Feature Request Response

```markdown
Hi [Name]! 👋

What a great idea! Thanks for sharing this suggestion.

**Your request:**
[Summarize what they asked for]

**My thoughts:**
[Your honest assessment - be genuine]

**Next steps:**
- [ ] I've added this to our feature request list
- [ ] Priority: [High/Medium/Low] based on [reason]
- [ ] Timeline: [Honest estimate or "TBD"]

I'll keep you posted on any updates. Thanks for helping us make [product] better! 🚀

Best,
[Your name]
```

### Issue Resolution

```markdown
Hi [Name]! 🎉

Great news - I've fixed the issue you reported!

**The problem:**
[Brief explanation of what was wrong]

**The fix:**
[What we did to resolve it]

**What you need to do:**
1. [Action item - e.g., "Clear your browser cache"]
2. [Action item - e.g., "Refresh the page"]
3. [Action item - e.g., "Update the plugin to version X.X"]

Everything should be working smoothly now. Please let me know if you see any other issues!

Thanks for your patience while we sorted this out. 😊

Best,
[Your name]
```

### Delayed Response Apology

```markdown
Hi [Name],

I'm so sorry for the delayed response! [Brief genuine reason if appropriate - e.g., "Things got busier than expected this week."]

I've now had a chance to look into your question properly.

[Provide the actual help/answer]

Again, apologies for the wait. Please don't hesitate to follow up if you need anything else!

Best,
[Your name]
```

## Project Update Templates

### Weekly Progress Update

```markdown
# Project Update: [Project Name]
**Week of [Date]**

Hi [Client Name]! 👋

Here's what happened this week:

## ✅ Completed
- [Task 1] - [Brief description of impact]
- [Task 2] - [Brief description of impact]
- [Task 3] - [Brief description of impact]

## 🔄 In Progress
- [Task 4] - [Expected completion]
- [Task 5] - [Expected completion]

## 📋 Coming Up Next
- [Task 6]
- [Task 7]

## 📸 Preview
[Screenshot or link to staging]

## ❓ Need Your Input
- [Question 1]
- [Question 2]

---

**Overall Status:** 🟢 On Track / 🟡 Minor Delay / 🔴 Needs Discussion

Let me know if you have any questions or want to hop on a quick call to discuss!

Best,
[Your name]
```

### Milestone Completion

```markdown
Hi [Name]! 🎉

I'm excited to share that we've completed [Milestone Name]!

## What's Done

[Screenshot of the feature/page]

**Key features:**
- ✅ [Feature 1]
- ✅ [Feature 2]
- ✅ [Feature 3]

## Where to See It
[Link to staging/preview]

## What's Next
Now we'll move on to [Next milestone], which includes:
- [Upcoming feature 1]
- [Upcoming feature 2]

## Your Feedback Needed
Please take a look when you have a chance and let me know:
1. Does this match your vision?
2. Any tweaks you'd like to see?
3. Ready to move forward?

Thanks for the great collaboration so far! 🚀

Best,
[Your name]
```

### Project Launch

```markdown
# 🚀 We're Live!

Hi [Name]!

I'm thrilled to let you know that [Project Name] is officially live!

**Live URL:** [link]

## What's Included
- ✅ [Feature 1]
- ✅ [Feature 2]
- ✅ [Feature 3]
- ✅ [Feature 4]

## Documentation
I've put together some guides to help you manage your site:
- [How to update content](#)
- [Managing your blog](#)
- [WooCommerce basics](#) (if applicable)

## Support Going Forward
[Explain your support arrangement]

## Quick Tips
💡 **Tip 1:** [Helpful advice]
💡 **Tip 2:** [Helpful advice]

---

It's been an absolute pleasure working on this project with you! If you have any questions or need any tweaks, I'm just a message away.

Congratulations on your new site! 🎉

Best,
[Your name]
```

## Explaining Technical Concepts

### Template Structure

```markdown
## [Technical Term] (In Plain English)

**What it is:**
[One sentence, no jargon]

**Why it matters to you:**
[How it affects their business/site]

**Think of it like:**
[Relatable analogy]

**What we're doing about it:**
[Action items]
```

### Example: Explaining Caching

```markdown
## Caching (Making Your Site Faster)

**What it is:**
Caching saves a copy of your pages so they load instantly for visitors, instead of being rebuilt from scratch each time.

**Why it matters to you:**
Faster sites = happier visitors = more sales. Google also ranks faster sites higher!

**Think of it like:**
A restaurant that pre-makes popular dishes during slow hours, so they're ready immediately when ordered.

**What we're doing:**
We're setting up caching on your site. This means:
- Pages load 3-5x faster
- Your server handles more visitors
- Better Google rankings

No action needed from you - we'll handle the setup! 🚀
```

### Example: Explaining a Security Update

```markdown
## Security Update Needed

**What happened:**
A vulnerability was discovered in [Plugin Name]. Don't worry - your site is safe, but we need to update it.

**Why it matters:**
Without the update, hackers could potentially [simplified explanation]. We want to stay ahead of any issues.

**Think of it like:**
Getting a recall notice for your car. It's running fine now, but there's a known issue we should fix before it causes problems.

**What we're doing:**
- ✅ We'll update the plugin today
- ✅ We'll test everything still works
- ✅ We'll let you know when it's done

**What you need to do:**
Nothing! We've got this covered. 😊
```

## Handling Difficult Situations

### Scope Creep Response

```markdown
Hi [Name]!

Thanks for sharing these ideas - I can see you're really thinking about making the site great!

I want to be transparent with you about scope. The items you mentioned:

**Within our current agreement:**
- ✅ [Item 1]
- ✅ [Item 2]

**Would be additional work:**
- [Item 3] - approximately [hours/cost]
- [Item 4] - approximately [hours/cost]

I'm absolutely happy to add these! I just want to make sure we're on the same page about timing and investment.

**Options:**
1. Add them now (adjust timeline by X / add cost of Y)
2. Complete current scope, then tackle these in Phase 2
3. Swap out something from current scope

What works best for you? Happy to hop on a call to discuss! 📞

Best,
[Your name]
```

### Deadline Extension Request

```markdown
Hi [Name],

I want to give you a heads up about our timeline.

**Current status:**
We've completed [X%] of the project, including [brief list].

**The challenge:**
[Honest explanation - e.g., "The payment gateway integration is taking longer than expected due to..."]

**What I'm proposing:**
- New target date: [Date]
- What we'll deliver: [Same scope / modified scope]

**What I'm doing to prevent further delays:**
- [Action 1]
- [Action 2]

I know this isn't ideal, and I apologize for any inconvenience. I'd rather deliver something great a bit later than rush something that doesn't meet our standards.

Can we chat briefly about this? I want to make sure this works for your timeline.

Best,
[Your name]
```

### Dealing with Unhappy Client

```markdown
Hi [Name],

Thank you for sharing your concerns. I hear you, and I understand this isn't the experience you expected.

**I'm sorry that:**
[Acknowledge their specific frustration without being defensive]

**Here's what I'm doing to fix this:**
1. [Immediate action]
2. [Follow-up action]
3. [Prevention for future]

**Timeline:**
You'll see [specific improvement] by [date].

I value our relationship and want to make this right. Would you have 15 minutes for a quick call? I'd love to discuss this directly and make sure we're aligned.

Best,
[Your name]
```

## Documentation Writing Style

### Headers

```markdown
✅ Use: "How to Add a New Product"
❌ Avoid: "Product Addition Procedures"

✅ Use: "Updating Your Homepage"
❌ Avoid: "Homepage Content Modification"
```

### Instructions

```markdown
✅ Friendly:
## Adding a Blog Post

Ready to share something new? Here's how to create a blog post:

1. Click **Posts → Add New** in your dashboard
2. Give your post a catchy title
3. Write your content in the editor
4. Add a featured image (this shows on your blog page!)
5. Click **Publish** when you're ready

💡 **Tip:** You can save as Draft if you want to finish later!

---

❌ Robotic:
## Blog Post Creation

To create a new blog post, perform the following steps:

1. Navigate to Posts → Add New
2. Enter the title in the title field
3. Enter content in the content field
4. Select a featured image
5. Click Publish
```

### Screenshots

Include screenshots that show:
- Where to click (use arrows or highlights)
- What they should see after clicking
- Before/after for changes

Caption format:
```markdown
![Description of what's shown](image.png)
*Click the blue "Publish" button in the top right corner*
```

## Quick Response Templates

### Acknowledging Receipt

> "Got it! Looking into this now and will get back to you by [time]. 👍"

### Need More Info

> "Thanks for reaching out! To help you better, could you tell me:
> 1. [Question 1]
> 2. [Question 2]
>
> This will help me find the best solution! 😊"

### Out of Office

> "Thanks for your message! I'm currently [away/in meetings] and will respond by [date/time]. If this is urgent, [alternative contact]. Otherwise, I'll be in touch soon! 🙏"

### Positive Feedback Response

> "Thank you so much for the kind words! It means a lot to hear that you're happy with [specific thing]. It's been a pleasure working with you! 😊"

## Emoji Usage Guide

| Situation | Appropriate Emojis |
|-----------|-------------------|
| Good news / completion | 🎉 ✅ 🚀 |
| Helpful tips | 💡 ✨ |
| Working on it | 🔧 ⚙️ |
| Friendly greeting | 👋 😊 |
| Thanks / appreciation | 🙏 ❤️ |
| Caution / important | ⚠️ 📌 |

**Guidelines:**
- 1-2 emojis per message is plenty
- Match the client's communication style
- Skip emojis for formal clients or serious issues
- Always end positive messages with an uplifting emoji