Customer experience skill

The sale is not the finish line — it is the starting line.

by wondelai·MIT license·★ 2,235 Stars on the repo·GitHub ↗

Use now

Files of Customer experience

wondelai/main1 file
customer-experience.md
Show the full text220 lines

Customer Experience

The sale is not the finish line — it is the starting line. The AFTER phase begins the moment someone becomes a customer. Delivering a world-class experience turns a one-time buyer into a loyal advocate who stays longer, buys more, and brings others. Customer experience is the ultimate competitive moat because it cannot be easily copied.

Moments of Truth Framework

A "moment of truth" is any interaction that disproportionately shapes a customer's perception of your business. Not every touchpoint is equal — some carry far more emotional weight than others. Your job is to identify these critical moments and design them intentionally.

Identifying Moments of Truth

Map the customer journey from purchase to ongoing use. At each stage, ask: "If we get this wrong, does the customer leave? If we get this right, does the customer become a fan?" Those high-stakes touchpoints are your moments of truth.

Common Moments of Truth by Business Type
Stage SaaS Service Business E-commerce Local Business
First interaction post-purchase Welcome email / onboarding flow Kickoff call or welcome packet Order confirmation + shipping updates First appointment or service visit
First value delivered "Aha moment" when product solves their problem First deliverable or report Unboxing experience Completed service with visible result
First problem Bug or feature confusion Missed deadline or miscommunication Wrong item or damage Service issue or delay
Ongoing relationship Feature adoption, QBRs Progress reviews, milestone celebrations Reorder experience, loyalty program Return visits, loyalty treatment
Exit/churn Cancellation flow Final deliverable or transition Return/refund process Final visit experience
Designing Moments of Truth

For each moment of truth, define:

Component Questions to Answer
Current state What happens today? Is it intentional or accidental?
Desired emotion How do we want the customer to feel at this moment?
Minimum standard What is the baseline acceptable experience?
Wow factor What would make this moment unexpectedly delightful?
Fail point What could go wrong and how do we prevent or recover from it?
Owner Who on the team is responsible for this moment?
Measurement How do we know if we are delivering consistently?
Moment of Truth Design Example: SaaS Onboarding
Component Design
Current state User signs up and receives a generic welcome email
Desired emotion Excited, confident, cared for, eager to explore
Minimum standard Welcome email within 1 minute, link to getting-started guide
Wow factor Personalized welcome video from founder mentioning their company name and use case; first-week concierge support via Slack
Fail point User signs up and hears nothing for 24 hours; gets confused during setup
Owner Head of Customer Success
Measurement Time to first value event; 7-day retention rate; onboarding NPS

Net Promoter Score (NPS) Implementation

NPS is a simple, widely-used metric that measures customer loyalty with a single question: "On a scale of 0-10, how likely are you to recommend us to a friend or colleague?"

NPS Categories
Score Category What It Means
9-10 Promoter Loyal enthusiast who will refer others and fuel growth
7-8 Passive Satisfied but not enthusiastic; vulnerable to competitors
0-6 Detractor Unhappy; at risk of churning and may actively damage your reputation
Calculating NPS

NPS = % Promoters - % Detractors

Example: 100 responses. 60 are Promoters (9-10), 25 are Passives (7-8), 15 are Detractors (0-6). NPS = 60% - 15% = 45

NPS Benchmarks
NPS Range Assessment
Below 0 Serious experience problems; priority fix needed
0-30 Average; room for significant improvement
30-50 Good; strong customer satisfaction
50-70 Excellent; world-class experience
70+ Exceptional; iconic brands typically live here
NPS Best Practices
Practice Why It Matters
Ask at consistent touchpoints Comparable data over time; common: after onboarding, quarterly, after support ticket
Always follow up with "Why?" The score is a signal; the open-ended response is the insight
Close the loop with Detractors Contact every Detractor within 24 hours; understand and resolve their issue
Celebrate Promoters Thank them, ask for a testimonial or referral, give them VIP treatment
Track NPS over time Monthly or quarterly trending is more valuable than any single score
Share NPS with the team Make it visible; what gets measured and seen gets improved
NPS Action Framework
Category Action Timeline
Detractor (0-6) Personal outreach, understand the issue, offer resolution Within 24 hours
Passive (7-8) Ask what would make it a 9 or 10; identify gaps Within 1 week
Promoter (9-10) Thank them; ask for a review, testimonial, or referral Immediately

Surprise and Delight Systems

The "wow factor" does not have to be expensive. It has to be unexpected and personal. Surprise and delight moments create emotional memories that drive loyalty and word-of-mouth.

Surprise and Delight Ideas by Business Type
Business Type Low-Cost Wow Medium-Cost Wow High-Cost Wow
SaaS Personalized Loom video from CSM Feature upgrade on anniversary Invite to exclusive beta with founder
Consultant Handwritten thank-you card after kickoff Relevant book sent when mentioned in conversation Custom strategy gift (framed roadmap, printed case study)
E-commerce Handwritten note in package Free surprise sample of a new product Surprise upgrade to premium shipping
Local service Team leaves area cleaner than they found it Small gift (branded item or local treat) Discount on next service "just because"
Systematizing Surprise and Delight

Surprises should not be random — they should be triggered by specific events or milestones:

Trigger Surprise Owner
First purchase / sign-up Personalized welcome gift or message Customer success
30-day milestone Check-in call or email with a small bonus Customer success
Birthday or anniversary Personalized card or discount Marketing automation
Customer reaches a success milestone Public recognition or private congratulations Customer success
Customer makes a referral Thank-you gift beyond the standard incentive Sales/marketing
Customer has a bad experience Proactive recovery with an extra gesture Support team
The Service Recovery Paradox

Customers who experience a problem that is resolved excellently often become more loyal than customers who never had a problem at all. This is the service recovery paradox. It means that how you handle failures is more important than avoiding all failures.

Service recovery framework:

  1. Acknowledge the problem immediately and sincerely
  2. Apologize without excuses or blame-shifting
  3. Act — fix the problem faster than the customer expects
  4. Add — do something extra to make up for the inconvenience
  5. Ask — follow up to confirm the issue is fully resolved

Tribes and Community Building

Customers who feel part of a community have dramatically higher retention, engagement, and lifetime value. They buy because of identity, not just utility.

The Tribe Framework
Element Description How to Build It
Shared identity Members feel part of something bigger than a transaction Create a name for your community; develop shared language and values
Shared enemy A common challenge, outdated approach, or frustration that unites the group Clearly articulate what you stand against, not just what you stand for
Shared rituals Recurring practices that reinforce belonging Weekly calls, annual events, onboarding rituals, milestone celebrations
Shared stories Narratives that inspire and teach Customer success stories, founder origin story, community member spotlights
Status and recognition Ways for members to earn standing within the community Badges, levels, featured member spotlights, exclusive access for active members
Community Building Tactics
Tactic Format Effort Level
Private online group Slack, Discord, Facebook Group, or Circle Low-Medium
Regular live sessions Weekly or monthly Q&A, masterclass, or workshop Medium
Annual event In-person or virtual conference, retreat, or summit High
Customer advisory board Small group of top customers who provide input on direction Medium
User-generated content Encourage customers to share their results, tips, and stories Low
Ambassador program Formalized role for your best customers to represent and spread the word Medium

Technology Systems for Consistent Experience

A world-class experience cannot depend on individual heroics. It must be systematized so it is delivered consistently regardless of who on the team is involved.

Essential Systems
System Purpose Examples
Onboarding automation Ensure every new customer goes through the same high-quality introduction Email sequences, in-app tours, welcome packets
Help desk / ticketing Track and resolve support issues consistently Zendesk, Intercom, Freshdesk, Help Scout
Knowledge base Enable customer self-service for common questions Notion, Confluence, dedicated help center
Customer health scoring Identify at-risk customers before they churn Usage data, engagement metrics, support ticket frequency
Feedback collection Systematically gather and act on customer input NPS surveys, CSAT surveys, in-app feedback widgets
Standard operating procedures Document how to handle every common scenario Internal wiki, process documentation
Quality assurance Regularly audit the experience for consistency Mystery shopping, call recording review, experience audits
The Technology Stack for Customer Experience
Layer Tools Purpose
Communication Email, SMS, in-app messaging, chat Stay connected across preferred channels
Support Ticketing system, knowledge base, chatbot Resolve issues efficiently
Feedback NPS tool, survey tool, review platform Collect and act on input
Analytics Customer health dashboard, usage analytics Spot trends and at-risk accounts
Automation Workflow automation, triggered actions Ensure nothing falls through the cracks
Community Community platform, social media groups Build belonging and peer support

Exercises

Exercise 1: Moments of Truth Map

Map your complete customer journey from purchase to ongoing use. Identify every touchpoint. Mark the 3-5 moments of truth — the interactions that most shape perception. For each, complete the Designing Moments of Truth template.

Exercise 2: NPS Implementation

If you are not measuring NPS, set it up this week. Choose your survey tool, decide when to send the survey (post-onboarding, quarterly, post-support), and create your follow-up process for each category (Promoter, Passive, Detractor).

Exercise 3: Surprise and Delight Calendar

Create a 12-month surprise and delight calendar with at least one planned moment per quarter. Define the trigger, the surprise, the owner, and the budget for each.

Exercise 4: Service Recovery Playbook

Document your service recovery process using the 5-step framework (Acknowledge, Apologize, Act, Add, Ask). Create specific scripts and actions for the three most common problems customers experience.

Exercise 5: Community Assessment

Evaluate whether a community makes sense for your business. If yes, choose a format (online group, live sessions, annual event) and draft a launch plan. If you already have a community, assess it against the Tribe Framework elements and identify gaps.

Checklist: Customer Experience Complete

  • Customer journey is mapped with all touchpoints identified
  • 3-5 moments of truth are designed intentionally (not left to chance)
  • NPS is being measured at consistent touchpoints
  • Detractor follow-up process is defined and happening within 24 hours
  • At least one surprise and delight system is in place and triggered automatically
  • Service recovery process is documented and the team is trained on it
  • SOPs exist for all common customer interactions
  • Customer health scoring (or equivalent early warning system) is in place
  • Community or tribe-building efforts are underway (if appropriate for your business)
  • Customer experience metrics (NPS, CSAT, retention, churn) are reviewed monthly
1# Customer Experience
2 
3The sale is not the finish line — it is the starting line. The AFTER phase begins the moment someone becomes a customer. Delivering a world-class experience turns a one-time buyer into a loyal advocate who stays longer, buys more, and brings others. Customer experience is the ultimate competitive moat because it cannot be easily copied.
4 
5## Moments of Truth Framework
6 
7A "moment of truth" is any interaction that disproportionately shapes a customer's perception of your business. Not every touchpoint is equal — some carry far more emotional weight than others. Your job is to identify these critical moments and design them intentionally.
8 
9### Identifying Moments of Truth
10 
11Map the customer journey from purchase to ongoing use. At each stage, ask: "If we get this wrong, does the customer leave? If we get this right, does the customer become a fan?" Those high-stakes touchpoints are your moments of truth.
12 
13### Common Moments of Truth by Business Type
14 
15| Stage | SaaS | Service Business | E-commerce | Local Business |
16|-------|------|-----------------|------------|----------------|
17| First interaction post-purchase | Welcome email / onboarding flow | Kickoff call or welcome packet | Order confirmation + shipping updates | First appointment or service visit |
18| First value delivered | "Aha moment" when product solves their problem | First deliverable or report | Unboxing experience | Completed service with visible result |
19| First problem | Bug or feature confusion | Missed deadline or miscommunication | Wrong item or damage | Service issue or delay |
20| Ongoing relationship | Feature adoption, QBRs | Progress reviews, milestone celebrations | Reorder experience, loyalty program | Return visits, loyalty treatment |
21| Exit/churn | Cancellation flow | Final deliverable or transition | Return/refund process | Final visit experience |
22 
23### Designing Moments of Truth
24 
25For each moment of truth, define:
26 
27| Component | Questions to Answer |
28|-----------|-------------------|
29| Current state | What happens today? Is it intentional or accidental? |
30| Desired emotion | How do we want the customer to feel at this moment? |
31| Minimum standard | What is the baseline acceptable experience? |
32| Wow factor | What would make this moment unexpectedly delightful? |
33| Fail point | What could go wrong and how do we prevent or recover from it? |
34| Owner | Who on the team is responsible for this moment? |
35| Measurement | How do we know if we are delivering consistently? |
36 
37### Moment of Truth Design Example: SaaS Onboarding
38 
39| Component | Design |
40|-----------|--------|
41| Current state | User signs up and receives a generic welcome email |
42| Desired emotion | Excited, confident, cared for, eager to explore |
43| Minimum standard | Welcome email within 1 minute, link to getting-started guide |
44| Wow factor | Personalized welcome video from founder mentioning their company name and use case; first-week concierge support via Slack |
45| Fail point | User signs up and hears nothing for 24 hours; gets confused during setup |
46| Owner | Head of Customer Success |
47| Measurement | Time to first value event; 7-day retention rate; onboarding NPS |
48 
49## Net Promoter Score (NPS) Implementation
50 
51NPS is a simple, widely-used metric that measures customer loyalty with a single question: "On a scale of 0-10, how likely are you to recommend us to a friend or colleague?"
52 
53### NPS Categories
54 
55| Score | Category | What It Means |
56|-------|----------|--------------|
57| 9-10 | Promoter | Loyal enthusiast who will refer others and fuel growth |
58| 7-8 | Passive | Satisfied but not enthusiastic; vulnerable to competitors |
59| 0-6 | Detractor | Unhappy; at risk of churning and may actively damage your reputation |
60 
61### Calculating NPS
62 
63**NPS = % Promoters - % Detractors**
64 
65Example: 100 responses. 60 are Promoters (9-10), 25 are Passives (7-8), 15 are Detractors (0-6).
66NPS = 60% - 15% = 45
67 
68### NPS Benchmarks
69 
70| NPS Range | Assessment |
71|-----------|-----------|
72| Below 0 | Serious experience problems; priority fix needed |
73| 0-30 | Average; room for significant improvement |
74| 30-50 | Good; strong customer satisfaction |
75| 50-70 | Excellent; world-class experience |
76| 70+ | Exceptional; iconic brands typically live here |
77 
78### NPS Best Practices
79 
80| Practice | Why It Matters |
81|----------|---------------|
82| Ask at consistent touchpoints | Comparable data over time; common: after onboarding, quarterly, after support ticket |
83| Always follow up with "Why?" | The score is a signal; the open-ended response is the insight |
84| Close the loop with Detractors | Contact every Detractor within 24 hours; understand and resolve their issue |
85| Celebrate Promoters | Thank them, ask for a testimonial or referral, give them VIP treatment |
86| Track NPS over time | Monthly or quarterly trending is more valuable than any single score |
87| Share NPS with the team | Make it visible; what gets measured and seen gets improved |
88 
89### NPS Action Framework
90 
91| Category | Action | Timeline |
92|----------|--------|----------|
93| Detractor (0-6) | Personal outreach, understand the issue, offer resolution | Within 24 hours |
94| Passive (7-8) | Ask what would make it a 9 or 10; identify gaps | Within 1 week |
95| Promoter (9-10) | Thank them; ask for a review, testimonial, or referral | Immediately |
96 
97## Surprise and Delight Systems
98 
99The "wow factor" does not have to be expensive. It has to be unexpected and personal. Surprise and delight moments create emotional memories that drive loyalty and word-of-mouth.
100 
101### Surprise and Delight Ideas by Business Type
102 
103| Business Type | Low-Cost Wow | Medium-Cost Wow | High-Cost Wow |
104|--------------|-------------|-----------------|---------------|
105| SaaS | Personalized Loom video from CSM | Feature upgrade on anniversary | Invite to exclusive beta with founder |
106| Consultant | Handwritten thank-you card after kickoff | Relevant book sent when mentioned in conversation | Custom strategy gift (framed roadmap, printed case study) |
107| E-commerce | Handwritten note in package | Free surprise sample of a new product | Surprise upgrade to premium shipping |
108| Local service | Team leaves area cleaner than they found it | Small gift (branded item or local treat) | Discount on next service "just because" |
109 
110### Systematizing Surprise and Delight
111 
112Surprises should not be random — they should be triggered by specific events or milestones:
113 
114| Trigger | Surprise | Owner |
115|---------|----------|-------|
116| First purchase / sign-up | Personalized welcome gift or message | Customer success |
117| 30-day milestone | Check-in call or email with a small bonus | Customer success |
118| Birthday or anniversary | Personalized card or discount | Marketing automation |
119| Customer reaches a success milestone | Public recognition or private congratulations | Customer success |
120| Customer makes a referral | Thank-you gift beyond the standard incentive | Sales/marketing |
121| Customer has a bad experience | Proactive recovery with an extra gesture | Support team |
122 
123### The Service Recovery Paradox
124 
125Customers who experience a problem that is resolved excellently often become more loyal than customers who never had a problem at all. This is the service recovery paradox. It means that how you handle failures is more important than avoiding all failures.
126 
127**Service recovery framework:**
1281. **Acknowledge** the problem immediately and sincerely
1292. **Apologize** without excuses or blame-shifting
1303. **Act** — fix the problem faster than the customer expects
1314. **Add** — do something extra to make up for the inconvenience
1325. **Ask** — follow up to confirm the issue is fully resolved
133 
134## Tribes and Community Building
135 
136Customers who feel part of a community have dramatically higher retention, engagement, and lifetime value. They buy because of identity, not just utility.
137 
138### The Tribe Framework
139 
140| Element | Description | How to Build It |
141|---------|-------------|----------------|
142| Shared identity | Members feel part of something bigger than a transaction | Create a name for your community; develop shared language and values |
143| Shared enemy | A common challenge, outdated approach, or frustration that unites the group | Clearly articulate what you stand against, not just what you stand for |
144| Shared rituals | Recurring practices that reinforce belonging | Weekly calls, annual events, onboarding rituals, milestone celebrations |
145| Shared stories | Narratives that inspire and teach | Customer success stories, founder origin story, community member spotlights |
146| Status and recognition | Ways for members to earn standing within the community | Badges, levels, featured member spotlights, exclusive access for active members |
147 
148### Community Building Tactics
149 
150| Tactic | Format | Effort Level |
151|--------|--------|-------------|
152| Private online group | Slack, Discord, Facebook Group, or Circle | Low-Medium |
153| Regular live sessions | Weekly or monthly Q&A, masterclass, or workshop | Medium |
154| Annual event | In-person or virtual conference, retreat, or summit | High |
155| Customer advisory board | Small group of top customers who provide input on direction | Medium |
156| User-generated content | Encourage customers to share their results, tips, and stories | Low |
157| Ambassador program | Formalized role for your best customers to represent and spread the word | Medium |
158 
159## Technology Systems for Consistent Experience
160 
161A world-class experience cannot depend on individual heroics. It must be systematized so it is delivered consistently regardless of who on the team is involved.
162 
163### Essential Systems
164 
165| System | Purpose | Examples |
166|--------|---------|----------|
167| Onboarding automation | Ensure every new customer goes through the same high-quality introduction | Email sequences, in-app tours, welcome packets |
168| Help desk / ticketing | Track and resolve support issues consistently | Zendesk, Intercom, Freshdesk, Help Scout |
169| Knowledge base | Enable customer self-service for common questions | Notion, Confluence, dedicated help center |
170| Customer health scoring | Identify at-risk customers before they churn | Usage data, engagement metrics, support ticket frequency |
171| Feedback collection | Systematically gather and act on customer input | NPS surveys, CSAT surveys, in-app feedback widgets |
172| Standard operating procedures | Document how to handle every common scenario | Internal wiki, process documentation |
173| Quality assurance | Regularly audit the experience for consistency | Mystery shopping, call recording review, experience audits |
174 
175### The Technology Stack for Customer Experience
176 
177| Layer | Tools | Purpose |
178|-------|-------|---------|
179| Communication | Email, SMS, in-app messaging, chat | Stay connected across preferred channels |
180| Support | Ticketing system, knowledge base, chatbot | Resolve issues efficiently |
181| Feedback | NPS tool, survey tool, review platform | Collect and act on input |
182| Analytics | Customer health dashboard, usage analytics | Spot trends and at-risk accounts |
183| Automation | Workflow automation, triggered actions | Ensure nothing falls through the cracks |
184| Community | Community platform, social media groups | Build belonging and peer support |
185 
186## Exercises
187 
188### Exercise 1: Moments of Truth Map
189 
190Map your complete customer journey from purchase to ongoing use. Identify every touchpoint. Mark the 3-5 moments of truth — the interactions that most shape perception. For each, complete the Designing Moments of Truth template.
191 
192### Exercise 2: NPS Implementation
193 
194If you are not measuring NPS, set it up this week. Choose your survey tool, decide when to send the survey (post-onboarding, quarterly, post-support), and create your follow-up process for each category (Promoter, Passive, Detractor).
195 
196### Exercise 3: Surprise and Delight Calendar
197 
198Create a 12-month surprise and delight calendar with at least one planned moment per quarter. Define the trigger, the surprise, the owner, and the budget for each.
199 
200### Exercise 4: Service Recovery Playbook
201 
202Document your service recovery process using the 5-step framework (Acknowledge, Apologize, Act, Add, Ask). Create specific scripts and actions for the three most common problems customers experience.
203 
204### Exercise 5: Community Assessment
205 
206Evaluate whether a community makes sense for your business. If yes, choose a format (online group, live sessions, annual event) and draft a launch plan. If you already have a community, assess it against the Tribe Framework elements and identify gaps.
207 
208## Checklist: Customer Experience Complete
209 
210- [ ] Customer journey is mapped with all touchpoints identified
211- [ ] 3-5 moments of truth are designed intentionally (not left to chance)
212- [ ] NPS is being measured at consistent touchpoints
213- [ ] Detractor follow-up process is defined and happening within 24 hours
214- [ ] At least one surprise and delight system is in place and triggered automatically
215- [ ] Service recovery process is documented and the team is trained on it
216- [ ] SOPs exist for all common customer interactions
217- [ ] Customer health scoring (or equivalent early warning system) is in place
218- [ ] Community or tribe-building efforts are underway (if appropriate for your business)
219- [ ] Customer experience metrics (NPS, CSAT, retention, churn) are reviewed monthly
220 

Discussion