30-60-90 day plan for customer experience managers

A 30-60-90 day plan for a new customer experience manager should spend the first 30 days auditing how the company listens (every survey, its question, audience, response rate and who reads it), recalculating the headline scores from raw responses, walking one high-volume customer journey end to end, and checking review and survey practices against the FTC's rules; days 31-60 building a closed loop in which unhappy customers get a follow-up and the top recurring cause gets an owner in another team; and days 61-90 showing one measured change in that journey plus a quarterly plan. As of November 2026, the FTC's Consumer Reviews and Testimonials Rule, in effect since October 21, 2024, bars fake reviews, incentives conditioned on positive or negative sentiment, undisclosed insider reviews and review suppression.

This plan is for the head of customer experience, chief customer officer, COO or general manager hiring a customer experience (CX) manager to run the feedback program and push fixes across teams the manager does not run. The contact center's own plans are in the 30-60-90 day plan for customer service managers (contact reasons and quality) and the 30-60-90 day plan for call center managers (staffing by interval). Account management in subscription businesses is in the 30-60-90 day plan for customer success managers.

How is a customer experience manager's job different from customer service and customer success?

Because a CX manager owns few of the fixes, the 90 days are judged on two things: whether the numbers can be trusted, and whether one cause found in the feedback was actually fixed by the team that owns it.

What does the 30-60-90 day plan look like?

30-60-90 day plan — [Name], Customer Experience Manager, [business]
Reports to: [head of CX / COO]    Start date: [date]
Customers: [segments]    Channels: [stores / web / app / phone]
Feedback: [relationship survey], [post-transaction surveys],
          [reviews on (sites)], [complaints], [contact reasons]
Systems: [survey platform], [CRM], [review management], [BI]

DAYS 1-30 — Audit how we listen; walk one journey
Goals:
- List every survey: question, scale, audience, trigger, response
  rate, owner, who reads it, what happens to low scores
- Recalculate NPS and satisfaction from raw responses for the last
  [12] months; note any exclusions or weighting
- Walk one high-volume journey as a customer (example: order to
  delivery to first support contact); record every handoff
- Read [200] verbatim comments and [50] complaints; code causes
- Review how review requests, incentives and replies work today
  against the FTC rules below, with legal
- Meet the owners of the journey's steps in each team
Deliverables by day 30:
- Listening audit: what to keep, merge or stop
- Baseline scores with response counts; top five causes
Check-in: day 30

DAYS 31-60 — Build the closed loop
Goals:
- Inner loop: low scores get a follow-up from a named team within
  [2] business days; outcomes recorded
- Outer loop: top recurring cause assigned to an owner in the team
  that runs that step, with a date
- Merge or retire surveys that overlap; fix triggers that miss
  unhappy customers (example: no survey after a failed delivery)
- Monthly CX review with the step owners: scores, causes, fixes
Deliverables by day 60:
- Loop running for [4] weeks with follow-up rate tracked
- One cause with an owner, a fix and a date
Check-in: day 60

DAYS 61-90 — Show one change; plan the quarter
Goals:
- Measure the fixed step against the day-30 baseline (complaints,
  repeat contacts, drop-off, scores from that step's customers)
- Journey map for the next journey, built from data, not workshop
  guesses
- Quarterly plan: the next two causes, owners, dates, measures
Deliverables by day 90:
- One measured change held for at least a month
- Quarterly plan agreed with the step owners
Check-in: day 90 — full review

Numbers in brackets are examples. Use the business's own segments, survey triggers and channels.

How do you calculate NPS, CSAT and CES, and when is a change real?

Recalculating the scores from raw responses is the fastest way to find out whether the dashboard can be trusted. Net Promoter Score has a published definition; the others vary by company, so write down the one in use.

• NPS: per the Net Promoter System's own page, customers answer "How likely are you to recommend us to a friend or colleague?" on a 0-10 scale. Scores of 9 or 10 are promoters, 7 or 8 passives and 0 to 6 detractors; NPS is the percentage of promoters minus the percentage of detractors.
• CSAT: a satisfaction question after a transaction. A common convention reports the share of 4 and 5 answers on a 5-point scale, but companies differ, so record the scale and the cut-off.
• CES: a customer effort question ("How easy was it to ...?"). Scales differ even more; compare only like with like.

An example with invented numbers:

1. NPS: 800 responses last quarter: 360 promoters (45 percent), 280 passives (35 percent) and 160 detractors (20 percent). NPS is 45 minus 20, or 25.
2. A small segment: this month, one region has 90 responses and an NPS of 31. Moving just five customers from detractor to passive changes that region's score by more than five points.
3. Baseline spread: over the last 12 months the company's monthly NPS ranged from 21 to 29. A month at 31 is worth watching; three months above 29 is worth reporting.

Always show the number of responses beside each score, and check who is missing. A survey sent only after a completed delivery never hears from customers whose delivery failed. The same arithmetic applied to job candidates is in candidate NPS for recruiters.

Which review, survey and cancellation rules does a new CX manager check?

These federal rules are summarized from eCFR and the FTC's and FCC's own texts as they read in November 2026. They are not legal advice; state consumer protection, privacy and automatic renewal laws add more, so review the program with legal.

The FTC notes that courts can impose civil penalties for knowing violations of the reviews rule. The checkout and subscription side of these rules is covered in more depth in the 30-60-90 day plan for ecommerce managers.

How does the closed loop work in practice?

1. Inner loop: each low score or complaint goes to a named team (the store, the service queue, the delivery partner manager), which contacts the customer within a set time, fixes what it can and records the outcome.
2. Coding: the CX team codes the cause of every low score and complaint the same way, so a monthly count by cause is possible.
3. Outer loop: the top recurring cause goes to the owner of that step in the journey, with the evidence (counts, verbatims, cost where finance can supply it) and an agreed date.
4. Close back: when a fix ships, customers who raised it hear about it, and the CX team measures that step's scores and complaints against the baseline.

A loop that only follows up with individual customers improves service recovery but leaves the cause in place. A loop that only produces monthly reports changes nothing for the customer who complained. The plan needs both.

Which numbers belong in the baseline?

The measures below are examples. Agree each definition with finance and the step owners in month one.

What does "on track" look like at day 30, 60 and 90?

A filled example

How should the hiring manager use this plan in the final interview?

Give every finalist the same brief: the business, its surveys, 12 months of anonymized scores with response counts and a sample of verbatim comments. Score the plans with the rubric in how to evaluate a 30-60-90 day plan in an interview. Questions for CX managers:

• "Our NPS rose eight points last month. What do you ask before we celebrate?"
• "Marketing wants to send review requests only to customers who gave us a 9 or 10. What do you say?"
• "Detractors keep naming delivery, which you do not own. How do you get it fixed?"
• "We run three surveys with a 4 percent response rate. What do you change first?"

Strong candidates ask for the response count and the 12-month range before reacting to the NPS change, raise the review-gating risk and send it to legal, and describe a fix owned by the delivery team with evidence and a date rather than a CX project.

What should the hiring manager ask at the check-ins?

• Day 30: Which of our scores can we trust, and who are we not hearing from? What did you find when you walked the journey?
• Day 60: What share of unhappy customers got a follow-up in time? Which cause has an owner outside your team?
• Day 90: What changed for customers, and how do you know? What are the next two causes and who owns them?

What the hiring manager owes a new customer experience manager

• Raw survey responses, not only dashboards, and access to complaints, reviews and contact reason data.
• A named owner for each step of the main journeys and a standing monthly review with them.
• A legal contact for review practices, survey consent and marketing messages.
• Agreement that a fix owned by another team counts as the CX manager's result.

Common mistakes

Adapting the plan

• Business-to-business software: score at the account and user level, and run the loop with customer success; see the customer success manager plan.
• Multi-location retail, restaurants and hospitality: report by location with response counts, and make store managers the inner-loop owners.
• Healthcare and financial services: agree with compliance which survey data may be collected and stored, and how complaints are logged, before changing any survey.
• Contact-center-heavy businesses: share contact reason codes with the customer service manager so complaints and calls are coded the same way.

If the role is still open, the customer success manager interview questions include questions on health scores and escalations that carry over to CX candidates who come from account management.