โ SOPs
Client Communication
Cross-Cutting โ All Engagements๐ค Rick (Revenue) primary ยท All agents follow these guidelines
SOP โ Client Communication
**Tag**: Cross-Cutting โ All Engagements **Owner**: Rick (Revenue) primary ยท All agents follow these guidelines ---
Purpose
Every client interaction builds or erodes trust. This SOP defines how, when, and what we communicate to clients across all engagement types. The core principle: **clear not clever** โ 5th grade reading level, no jargon, outcomes-focused. ---
Communication Principles
1. **Clear not clever** โ All client-facing copy at 5th grade reading level (3rd grade = ideal) 2. **State facts, tell truth** โ Never exaggerate. If we don't have proof, say "we're in beta" 3. **Sell outcomes, not AI** โ Wrong: "Our multi-agent system automates your CRM." Right: "You'll never manually enter a lead again." 4. **Match the avatar** โ Use the client's language, not ours: - Dentists hear about receptionists and missed calls - HVAC hears about dispatchers and job scheduling - Lawyers hear about paralegals and intake screening 5. **Bad news fast** โ If something breaks or is delayed, tell the client immediately. Never hide problems. 6. **One owner per thread** โ Every client communication has one responsible agent. No conflicting messages. ---
Response Time SLAs
| Tier | First Response | Issue Resolution | Escalation Threshold | |------|---------------|-----------------|---------------------| | Free Pilot | 48 hours | 72 hours | 5 business days | | Starter ($5K) | 24 hours | 48 hours | 3 business days | | Growth Retainer ($2-3K/mo) | 12 hours | 24 hours | 2 business days | | Premium Retainer ($5-10K/mo) | 4 hours | 12 hours | 1 business day | | Upwork Project | 24 hours | 48 hours | Per milestone deadline | **"First Response"** = acknowledgment that we received the message and are working on it. Does NOT mean resolution. ---
Sales Phase
- `kickoff-pilot` โ Free pilot welcome + intake questions - `kickoff-starter` โ Starter package welcome + access checklist - `kickoff-standard` โ Standard package welcome + discovery scheduling - `kickoff-premium` โ Premium package welcome + dedicated point of contact intro - `proposal-upwork` โ Upwork proposal template (see sop-upwork.md) - `scope-confirmation-starter` โ Confirms agreed scope for Starter builds - `scope-confirmation-standard` โ Confirms agreed scope for Standard+ builds
Delivery Phase
- `progress-update` โ Weekly build progress update (Standard+) - `milestone-complete` โ Milestone delivered, here's what was done - `access-request` โ Request for tool credentials or system access - `delay-notification` โ Timeline is slipping, here's the new ETA and why
Handoff Phase
- `handoff-summary` โ What was built, how it works, where to find docs - `handoff-support` โ Post-handoff support window details and contact info - `training-recording` โ Link to recorded handoff/training session
Post-Delivery
- `feedback-request` โ "How's it working? Any issues?" (sent Day 2-3 post-handoff) - `testimonial-request` โ Ask for written quote, video, or Google review (sent Day 5-7) - `referral-ask` โ "Know anyone who'd benefit?" (sent with or after testimonial request) - `retainer-upsell` โ "Here's what ongoing management looks like" (sent Day 7-14) - `nps-survey` โ Net Promoter Score survey (sent Day 14)
Incident
- `incident-notification` โ Something broke, here's what we know and what we're doing - `incident-resolved` โ Issue fixed, here's what happened and what we changed - `incident-postmortem` โ Full incident report (for Premium clients on significant issues) ---
Free Pilot Timeline
- Day 0: `kickoff-pilot` - Day 1: Scope confirmation (inline email, not template) - Day 4: Demo scheduled (calendar invite) - Day 5: `handoff-summary` + `handoff-support` - Day 7: `feedback-request` - Day 10: `testimonial-request` + `referral-ask` - Day 14: `retainer-upsell`
Starter Timeline
- Day 0: `kickoff-starter` - Day 2: `scope-confirmation-starter` - Day 5: `milestone-complete` (build done) - Day 7: `handoff-summary` + `handoff-support` + `training-recording` - Day 10: `feedback-request` - Day 14: `testimonial-request` + `referral-ask` - Day 21: `retainer-upsell` + `nps-survey`
Standard/Premium Timeline
- Day 0: `kickoff-standard` or `kickoff-premium` - Day 3: `scope-confirmation-standard` - Weekly: `progress-update` (every Friday) - Per milestone: `milestone-complete` - Final day: `handoff-summary` + `handoff-support` + `training-recording` - Day 3 post: `feedback-request` - Day 7 post: `testimonial-request` + `referral-ask` - Day 14 post: `retainer-upsell` + `nps-survey`
Retainer (Ongoing)
- Monthly: performance report email - As needed: `incident-notification` / `incident-resolved` - Quarterly: business review call invitation - At renewal: renewal confirmation + scope review ---
DO
- Use short sentences (under 20 words) - Use bullet points for lists - Start emails with the most important information - Use the client's first name - End with a clear next step or CTA - Use "we" (team) not "I" (individual) for delivery updates
DO NOT
- Use jargon: "AI agent," "multi-modal," "orchestrator," "pipeline," "API" - Use filler: "Just wanted to check in," "Hope this finds you well," "Per our last conversation" - Use hedging: "Maybe we could," "I think perhaps," "It might be possible" - Send walls of text โ if it's more than 5 sentences, it needs bullet points or a call - CC people who don't need to be on the thread - Reply-all unless necessary
Translation Guide
| Internal Term | Client-Facing Term | |--------------|-------------------| | AI agent | Your automated assistant | | Cron job | Scheduled task / automated routine | | CRM sync | Your leads show up automatically | | API integration | We connected [Tool A] to [Tool B] | | Pipeline | Your lead tracking board | | Enrichment | We verified and filled in missing contact info | | Outreach sequence | Your follow-up emails | | Model cascade | (Never mention this to clients) | ---
Escalation Triggers
Escalate to Clayton immediately if: 1. **Client is angry or threatening** โ Any message with hostile tone, threats to leave reviews, or legal language 2. **Scope dispute** โ Client claims we agreed to something we didn't 3. **Payment dispute** โ Client requests refund or disputes charge 4. **Data breach or privacy concern** โ Client reports their data was exposed or mishandled 5. **Deliverable failure** โ Core automation isn't working and can't be fixed within SLA 6. **Platform risk** โ Upwork flags account, LinkedIn restricts, HubSpot rate-limits Escalation process: 1. Acknowledge the client's concern immediately (within SLA) 2. Do NOT promise resolution or make commitments 3. Send escalation summary to Clayton via Telegram 4. Wait for Clayton's direction before responding substantively ---
Channel Rules
- **Email**: Default for all formal communication (kickoffs, handoffs, proposals) - **Upwork Messages**: ONLY channel during active Upwork projects (until project closes) - **Phone/Zoom**: Discovery calls, handoff calls, escalations. Always follow up with written summary. - **Telegram**: Internal team only. Never share the team Telegram with clients. - **LinkedIn DMs**: Pre-sales only. Move to email as soon as prospect engages. ---
Agent Responsibilities
| Agent | Communication Role | |-------|-------------------| | Rick | All sales-phase comms, testimonial/review collection, upsell emails, escalation first response | | Devin | Technical updates, scope confirmations, handoff docs, incident technical details | | Alfred | Monitors SLA compliance, triggers escalation if response time breached | | Daniel | N/A (no direct client communication) | | Friedrich | Invoice-related communication only | ---
Anti-Patterns (Do NOT)
- Do NOT send more than one email per day to the same client (unless they're responding to you) - Do NOT use "AI" or "agent" in any client-facing communication unless the client uses it first - Do NOT make promises about timelines or outcomes that aren't confirmed in the scope document - Do NOT share internal documentation, SOPs, or agent details with clients - Do NOT skip the testimonial/referral ask โ it's the highest-value post-delivery action
View raw source
# SOP โ Client Communication **Tag**: Cross-Cutting โ All Engagements **Owner**: Rick (Revenue) primary ยท All agents follow these guidelines --- ## Purpose Every client interaction builds or erodes trust. This SOP defines how, when, and what we communicate to clients across all engagement types. The core principle: **clear not clever** โ 5th grade reading level, no jargon, outcomes-focused. --- ## Communication Principles 1. **Clear not clever** โ All client-facing copy at 5th grade reading level (3rd grade = ideal) 2. **State facts, tell truth** โ Never exaggerate. If we don't have proof, say "we're in beta" 3. **Sell outcomes, not AI** โ Wrong: "Our multi-agent system automates your CRM." Right: "You'll never manually enter a lead again." 4. **Match the avatar** โ Use the client's language, not ours: - Dentists hear about receptionists and missed calls - HVAC hears about dispatchers and job scheduling - Lawyers hear about paralegals and intake screening 5. **Bad news fast** โ If something breaks or is delayed, tell the client immediately. Never hide problems. 6. **One owner per thread** โ Every client communication has one responsible agent. No conflicting messages. --- ## Response Time SLAs | Tier | First Response | Issue Resolution | Escalation Threshold | |------|---------------|-----------------|---------------------| | Free Pilot | 48 hours | 72 hours | 5 business days | | Starter ($5K) | 24 hours | 48 hours | 3 business days | | Growth Retainer ($2-3K/mo) | 12 hours | 24 hours | 2 business days | | Premium Retainer ($5-10K/mo) | 4 hours | 12 hours | 1 business day | | Upwork Project | 24 hours | 48 hours | Per milestone deadline | **"First Response"** = acknowledgment that we received the message and are working on it. Does NOT mean resolution. --- ## Email Templates Index ### Sales Phase - `kickoff-pilot` โ Free pilot welcome + intake questions - `kickoff-starter` โ Starter package welcome + access checklist - `kickoff-standard` โ Standard package welcome + discovery scheduling - `kickoff-premium` โ Premium package welcome + dedicated point of contact intro - `proposal-upwork` โ Upwork proposal template (see sop-upwork.md) - `scope-confirmation-starter` โ Confirms agreed scope for Starter builds - `scope-confirmation-standard` โ Confirms agreed scope for Standard+ builds ### Delivery Phase - `progress-update` โ Weekly build progress update (Standard+) - `milestone-complete` โ Milestone delivered, here's what was done - `access-request` โ Request for tool credentials or system access - `delay-notification` โ Timeline is slipping, here's the new ETA and why ### Handoff Phase - `handoff-summary` โ What was built, how it works, where to find docs - `handoff-support` โ Post-handoff support window details and contact info - `training-recording` โ Link to recorded handoff/training session ### Post-Delivery - `feedback-request` โ "How's it working? Any issues?" (sent Day 2-3 post-handoff) - `testimonial-request` โ Ask for written quote, video, or Google review (sent Day 5-7) - `referral-ask` โ "Know anyone who'd benefit?" (sent with or after testimonial request) - `retainer-upsell` โ "Here's what ongoing management looks like" (sent Day 7-14) - `nps-survey` โ Net Promoter Score survey (sent Day 14) ### Incident - `incident-notification` โ Something broke, here's what we know and what we're doing - `incident-resolved` โ Issue fixed, here's what happened and what we changed - `incident-postmortem` โ Full incident report (for Premium clients on significant issues) --- ## When to Send What ### Free Pilot Timeline - Day 0: `kickoff-pilot` - Day 1: Scope confirmation (inline email, not template) - Day 4: Demo scheduled (calendar invite) - Day 5: `handoff-summary` + `handoff-support` - Day 7: `feedback-request` - Day 10: `testimonial-request` + `referral-ask` - Day 14: `retainer-upsell` ### Starter Timeline - Day 0: `kickoff-starter` - Day 2: `scope-confirmation-starter` - Day 5: `milestone-complete` (build done) - Day 7: `handoff-summary` + `handoff-support` + `training-recording` - Day 10: `feedback-request` - Day 14: `testimonial-request` + `referral-ask` - Day 21: `retainer-upsell` + `nps-survey` ### Standard/Premium Timeline - Day 0: `kickoff-standard` or `kickoff-premium` - Day 3: `scope-confirmation-standard` - Weekly: `progress-update` (every Friday) - Per milestone: `milestone-complete` - Final day: `handoff-summary` + `handoff-support` + `training-recording` - Day 3 post: `feedback-request` - Day 7 post: `testimonial-request` + `referral-ask` - Day 14 post: `retainer-upsell` + `nps-survey` ### Retainer (Ongoing) - Monthly: performance report email - As needed: `incident-notification` / `incident-resolved` - Quarterly: business review call invitation - At renewal: renewal confirmation + scope review --- ## Tone Guidelines ### DO - Use short sentences (under 20 words) - Use bullet points for lists - Start emails with the most important information - Use the client's first name - End with a clear next step or CTA - Use "we" (team) not "I" (individual) for delivery updates ### DO NOT - Use jargon: "AI agent," "multi-modal," "orchestrator," "pipeline," "API" - Use filler: "Just wanted to check in," "Hope this finds you well," "Per our last conversation" - Use hedging: "Maybe we could," "I think perhaps," "It might be possible" - Send walls of text โ if it's more than 5 sentences, it needs bullet points or a call - CC people who don't need to be on the thread - Reply-all unless necessary ### Translation Guide | Internal Term | Client-Facing Term | |--------------|-------------------| | AI agent | Your automated assistant | | Cron job | Scheduled task / automated routine | | CRM sync | Your leads show up automatically | | API integration | We connected [Tool A] to [Tool B] | | Pipeline | Your lead tracking board | | Enrichment | We verified and filled in missing contact info | | Outreach sequence | Your follow-up emails | | Model cascade | (Never mention this to clients) | --- ## Escalation Triggers Escalate to Clayton immediately if: 1. **Client is angry or threatening** โ Any message with hostile tone, threats to leave reviews, or legal language 2. **Scope dispute** โ Client claims we agreed to something we didn't 3. **Payment dispute** โ Client requests refund or disputes charge 4. **Data breach or privacy concern** โ Client reports their data was exposed or mishandled 5. **Deliverable failure** โ Core automation isn't working and can't be fixed within SLA 6. **Platform risk** โ Upwork flags account, LinkedIn restricts, HubSpot rate-limits Escalation process: 1. Acknowledge the client's concern immediately (within SLA) 2. Do NOT promise resolution or make commitments 3. Send escalation summary to Clayton via Telegram 4. Wait for Clayton's direction before responding substantively --- ## Channel Rules - **Email**: Default for all formal communication (kickoffs, handoffs, proposals) - **Upwork Messages**: ONLY channel during active Upwork projects (until project closes) - **Phone/Zoom**: Discovery calls, handoff calls, escalations. Always follow up with written summary. - **Telegram**: Internal team only. Never share the team Telegram with clients. - **LinkedIn DMs**: Pre-sales only. Move to email as soon as prospect engages. --- ## Agent Responsibilities | Agent | Communication Role | |-------|-------------------| | Rick | All sales-phase comms, testimonial/review collection, upsell emails, escalation first response | | Devin | Technical updates, scope confirmations, handoff docs, incident technical details | | Alfred | Monitors SLA compliance, triggers escalation if response time breached | | Daniel | N/A (no direct client communication) | | Friedrich | Invoice-related communication only | --- ## Anti-Patterns (Do NOT) - Do NOT send more than one email per day to the same client (unless they're responding to you) - Do NOT use "AI" or "agent" in any client-facing communication unless the client uses it first - Do NOT make promises about timelines or outcomes that aren't confirmed in the scope document - Do NOT share internal documentation, SOPs, or agent details with clients - Do NOT skip the testimonial/referral ask โ it's the highest-value post-delivery action