Onboard

Check onboarding status

Summarizes onboarding milestone completion, active blockers, and time-to-value trajectory

One of 51 free, open-source prompts from Sonora — copy-paste-ready AI prompts for customer success and account management, organized by customer lifecycle stage. Copy this into any AI assistant, or run it on autopilot inside Sonora.

The prompt

Steps:

  1. Pull the Customer 360 for [Customer]: contract details (ARR, start date, renewal date, term), account tier, CSM ownership, primary contact, and exec sponsor.
  2. Retrieve the onboarding milestones and implementation plan from the Customer 360. For each milestone, determine: status (complete, in progress, blocked, not started), target date, actual completion date (if done), and owner.
  3. Calculate time-to-value metrics: days since contract start, percentage of milestones completed, days ahead or behind the original timeline, and estimated go-live date based on current pace.
  4. Review open issues and CX Cues related to onboarding or implementation from the past 60 days. Identify active blockers — issues preventing milestone completion.
  5. Pull recent touchpoint activity from the past 30 days: meetings, emails, and escalations related to onboarding progress.
  6. Assess engagement quality: frequency of customer participation in onboarding calls, stakeholder attendance trends, and any gaps in scheduled check-ins.

Formatting: Fit everything into a single-page onboarding status brief. Be dense, not verbose.

Header — “[Customer Name] Onboarding Status” as H1, followed by two lines (regular text). Bold each label but not the value: Line 1: Onboarding Phase: [current phase] | Progress: [X]% milestones complete | Timeline: [N days ahead/behind schedule] | Critical Blocker: [the single biggest blocker right now, or “None”] Line 2: ARR: $X | Contract Start: [date] ([N] days ago) | Target Go-Live: [date] ([N] days out) | Tier: [tier] | CSM: [name] | Primary: [name] | Exec Sponsor: [name]

Milestone tracker — Compact table showing each onboarding milestone: | Milestone | Status | Target Date | Actual/Est. Date | Owner | Notes |

Use status indicators: ✅ Complete, 🔄 In Progress, 🚫 Blocked, ⬜ Not Started.

Active blockers — Bullet list of issues preventing progress. Each in this format:

  • [Severity]: [Blocker name] — One-sentence description with evidence of impact on timeline. (Source)

If no blockers exist, state: “No active blockers identified.”

Recent activity — Two subsections: Progress signals

  • [Date]: [What happened — one sentence]. (Source) Concerns
  • [Date]: [What happened — one sentence]. (Source)

If either subsection has no data, include the header with: “No [progress signals/concerns] identified based on available data.”

Time-to-value assessment — 2-3 sentences synthesizing current trajectory: whether the account is on track, accelerating, or at risk of delayed go-live. Ground every claim in a specific milestone status or data point.

Next 14 days — Three actions as a table: | Action | Owner | By when | Expected outcome |

Edge cases:

  • If onboarding milestones are not defined in the Customer 360, state that clearly and reconstruct a best-effort timeline from meeting notes and touchpoint history.
  • If the account appears to be past the onboarding phase (all milestones complete or contract start > 180 days ago), note that and suggest running a health brief instead.
  • If any milestone has no target date, flag it as “[Target date not set]” rather than estimating.
  • If engagement data is sparse (fewer than 2 touchpoints in the past 30 days), flag the engagement gap explicitly.
  • Every claim must cite a specific data point, date, or interaction. No filler.

Data sources required

CRM / customer dataSalesforce, HubSpotMeeting transcriptsGong, Granola, FirefliesSupport ticketsZendesk, Intercom, PylonCustomer communicationsemail, SlackCSM notesNotion, Google Docs

The catch

A prompt is only as good as the data you feed it.

Run this well and you'll be stitching together 5 disconnected systems by hand, for one account at a time — and the answer is only ever as fresh as your last copy-paste. Sonora already has the context, live:

  • CRM / customer data — connected and continuously synced
  • Meeting transcripts — connected and continuously synced
  • Support tickets — connected and continuously synced
  • Customer communications — connected and continuously synced
  • CSM notes — connected and continuously synced

Inside Sonora this prompt runs grounded in your real customer data, on a schedule, across every account at once — and flags what needs you, before you have to ask.