Customer Health Check Meeting Agenda: Surface Outcomes, Friction and Next Steps

A customer health check meeting agenda should uncover whether the customer is progressing toward the outcomes they value. It creates a shared view of evidence, friction, risk and the next actions needed from both sides.

The meeting is not a disguised renewal pitch or an automated score review. Start with the customer’s context, use traceable evidence and make uncertainty discussable.

Define the purpose and meeting boundary

Write one sentence that explains why this health check is happening now. The purpose might be to review onboarding progress, restore adoption after a team change, resolve recurring friction, prepare for a new phase or check whether an existing success plan still reflects reality.

Define what the meeting will not decide. Contract changes, commercial commitments, technical incident conclusions or legal interpretations may require different owners and processes. Route those items rather than improvising authority in the room.

Select a cadence based on lifecycle stage, customer preference, risk and the speed of change. A regular monthly review may suit an active rollout, while an event-triggered check may be better after a sponsor change or unresolved blocker. The customer onboarding meeting agenda is a better starting point when the relationship is still establishing goals, roles and first milestones.

Invite the people who can clarify and act

Keep attendance purposeful. The customer should have someone who understands desired outcomes and someone close enough to the work to describe real use and friction. The provider should include the customer owner and any specialist needed to resolve a known item.

Assign explicit roles:

• facilitator: keeps the conversation outcome-led;
• customer outcome owner: validates priorities and progress;
• evidence owner: prepares source data and definitions;
• note owner: captures decisions, questions and actions;
• escalation owner: receives issues that exceed meeting authority.

Do not invite senior leaders merely to add pressure. If an executive sponsor needs a concise strategic review, prepare that separately. Send the purpose, time box, evidence and questions in advance so the customer can correct assumptions before the meeting.

Prepare a balanced evidence pack

Combine quantitative and qualitative evidence. Useful inputs may include agreed outcome measures, milestone status, relevant product usage, service cases, training completion, customer feedback, open actions and changes in the customer’s organization. Record source, date range, definition and known gaps.

Avoid treating logins, seats or feature clicks as outcomes. Usage may help explain behavior, but it needs context. A low number may reflect a seasonal workflow or a successfully automated task; a high number may reflect repeated failure. Ask before interpreting.

Review the prior client status report template and action log for commitments. Separate facts, customer statements and internal inferences. Remove information the attendees do not need, and never surprise the customer with an unexplained score assembled from opaque inputs.

Prepare an evidence note for every important signal: what question it helps answer, where it came from, who owns the source, which period it covers and what limitation could change its meaning. Reconcile obvious conflicts before the meeting, but leave genuine uncertainty visible. For example, product activity may show that a workflow ran while the customer reports that it required a costly workaround. Both facts can be true. Bring the source owner only when their presence will help the customer understand or resolve the gap; otherwise assign a follow-up. This keeps the meeting focused while preserving a route back to the underlying record.

Copy this 45-minute customer health check agenda

CUSTOMER HEALTH CHECK — 45 MINUTES

Purpose:
Customer outcomes in scope:
Facilitator / note owner / decision owners:

1. OPEN AND CONFIRM CONTEXT — 5 min
   What changed since the last check?
   Does the purpose still match the customer's priorities?

2. OUTCOME PROGRESS — 10 min
   Intended outcome / current evidence / confidence / gap

3. ADOPTION AND EXPERIENCE — 10 min
   What is working? Where is effort, confusion or delay appearing?

4. RISKS AND BLOCKERS — 8 min
   Evidence / impact / current response / needed escalation

5. DECISIONS AND SUPPORT — 5 min
   Decision / owner / deadline / information required

6. ACTIONS AND CLOSE — 7 min
   Action / one owner / due date / success evidence
   Confirm next checkpoint and distribution

Adjust timings to the purpose, but keep enough time for the customer’s account of what is happening. A health check dominated by provider slides will miss the evidence it was meant to surface.

Open with outcomes and changed context

Begin by confirming the desired outcomes in the customer’s language. Ask what has changed in strategy, team, process, volume, constraints or timing since the last review. A previously important use case may no longer matter, and a stable adoption plan can become unrealistic after an organizational change.

State the evidence period and known limitations. Invite correction: “This is the picture we prepared from the agreed sources. What is missing or misleading?” That question makes the review collaborative without abandoning accountable preparation.

Do not lead with an internal color or churn label. If a status label is used, define it and explain the evidence behind it. Allow “unknown” when an owner must investigate. False certainty encourages bad follow-up.

Review progress against customer outcomes

Take one intended outcome at a time. Compare the baseline, current evidence, target or success condition, confidence and next learning step. Distinguish delivered capabilities from realized customer value.

Ask what has become easier, faster, safer or more reliable from the customer’s perspective, without forcing those categories when they do not fit. Capture counter-evidence as carefully as positive evidence. If the original measure no longer represents value, agree who will revise the success plan and who must approve the change.

Explore adoption and friction without blame

Review the real workflow, not only aggregate activity. Ask which users are succeeding, where handoffs break, what requires workarounds, which training is missing and what has stopped people from using the intended process. The aim is to diagnose conditions, not label a customer as resistant.

Separate product friction, implementation gaps, internal customer constraints and unclear expectations. Each may require a different owner. Avoid recommending more training when the evidence points to a product defect, permissions issue or poorly designed workflow.

Use specific examples and dates. “Adoption is low” is an interpretation; “three of eight intended teams completed the configured workflow during the stated period” is reviewable evidence. Ask the customer whether the denominator and period are meaningful.

Surface risks, support needs and decisions

Turn vague concern into a governable item. Record description, evidence, potential effect, urgency, current response, owner and next review. Distinguish a risk from an issue that is already affecting the customer.

For decisions, state the question, options, decision owner, deadline and consequence of delay. If the meeting lacks authority, assign an escalation action. Preserve the result in a decision log rather than burying it in prose notes.

Do not use the health check to make unsupported promises about delivery dates or commercial exceptions. Capture the customer’s need accurately, then route it to the authorized owner. Tell the customer when and how they will receive an answer.

Agree actions with evidence of completion

Every action needs one directly accountable owner, a due date and a visible completion condition. “Improve adoption” is not an action. “Customer enablement lead will run the approved workflow session for Team B by 30 July; attendance and completed setup will be reviewed at the next checkpoint” is actionable.

Balance actions across both organizations. If every action belongs to the customer, test whether the provider is avoiding responsibility. If every action belongs to the provider, confirm that customer decisions and access dependencies are visible.

Use meeting follow-up practices to send one reviewed record, invite corrections and update the durable action system. Close obsolete actions explicitly instead of letting them disappear.

Capture the conversation responsibly

Customer discussions may contain personal data, confidential plans, support details or commercial information. Record only when there is a clear purpose and the organization has authorized the method. Give clear notice, obtain required agreement, minimize capture, restrict access and follow retention rules.

For a customer health check with authorized, clearly consented capture, Kuno can help draft notes, decisions and actions for responsible human review. It does not determine customer health or commit either organization. Explore Kuno

If AI assists with notes, verify speakers, metrics, commitments, sentiment-like interpretations and deadlines against source evidence. Remove material the final audience does not need. Human account owners remain responsible for relationship judgment and follow-through.

Close, distribute and update the health record

End by summarizing the customer’s stated outcomes, the most important evidence, unresolved questions, decisions and actions. Ask the customer to correct the summary in the room. Confirm the next checkpoint and the escalation route for anything urgent.

Send the follow-up promptly through the agreed channel. Link to source records rather than copying sensitive detail into multiple systems. Update the customer plan, action tracker, risk record and decision log so the meeting does not create a parallel truth.

Use a QBR meeting agenda when the next conversation needs broader strategic and relationship review. Keep operational actions moving between formal meetings.

Run the final health check QA

Before closing the record, confirm:

• Purpose, scope and authority were explicit.
• The customer had meaningful time to describe current reality.
• Outcomes were reviewed before activity metrics.
• Every measure includes a source, period and definition.
• Facts, customer statements and internal inferences are distinguishable.
• Adoption signals were interpreted with workflow context.
• Risks and active issues are separated and owned.
• Decisions have an owner, deadline and escalation route.
• Actions have one owner, due date and completion evidence.
• Recording and AI assistance followed authorization and consent requirements.
• The customer can correct the distributed record.
• Durable customer systems were updated.

Convert an authorized conversation into reviewable follow-up, not an automatic health verdict. Kuno supports consented capture and draft documentation; customer and provider owners verify the evidence, meaning and commitments. See Kuno