# BlueHill — Customer Operations Glossary > Definitions of the key terms in customer success, customer support, customer operations, onboarding, and revenue retention. --- # Customer Advocacy **Customer advocacy** is the stage where customers go beyond using your product and actively promote it — through referrals, reviews, case studies, conference talks, and inbound introductions to peers. ## Advocacy activities - Public reference calls for prospects - Case studies / customer stories - G2, Capterra, Trustpilot reviews - Speaking on webinars or at conferences - Social media mentions - Customer advisory board participation - Referrals to peer companies ## Why advocacy matters Advocates lower CAC: a referred customer closes 2–3× faster and has higher LTV. They also create social proof that compounds — case studies and reviews influence buyers years after publication. ## How to build advocacy - Identify promoters (NPS 9–10) - Make it easy (provide drafts, talking points, templates) - Give back (early access, exec dinners, swag) - Track participation per advocate - Don't burn advocates with too many asks ## How BlueHill helps Tag customer records with advocacy state (potential, active, fatigued). Track participation history. Surface promoter accounts on the dashboard so the right ask goes to the right person. Related: [Lifecycle](/glossary/lifecycle) · [NPS](/glossary/nps) --- # Customer Effort Score (CES) **CES** measures how much effort a customer had to expend to accomplish a task — getting a ticket resolved, completing onboarding, using a feature — usually with the question "How easy was it to ___?" on a 1–7 scale (1 = very easy, 7 = very difficult). ## Why CES matters CES is the strongest predictor of repurchase intent. Customers who report low effort are far more likely to renew than customers who report low effort *and* high satisfaction. Effort beats delight. ## When to use CES After a specific transactional touchpoint: - Support ticket resolution - Onboarding milestone completion - Feature discovery / adoption - Self-service journey ## Benchmarks Aim for over 5 average on a 1–7 scale (where 7 is "very easy"). Drops below 4.5 should trigger root-cause analysis. ## How BlueHill helps CES surveys auto-trigger after key milestones. Internal notes capture root cause when CES is low ("portal navigation was confusing"; "form field labels unclear"), feeding the product roadmap. Related: [CSAT](/glossary/csat) · [NPS](/glossary/nps) · [Self-service](/glossary/self-service) --- # Churn **Churn** is the rate at which customers stop subscribing, paying, or using your product over a given period. Two common types: - **Customer churn** — % of customers lost (count-based) - **Revenue churn** — % of MRR lost (dollar-based) ## Formula ``` Customer churn = Customers lost ÷ Customers at start × 100 Revenue churn = MRR lost ÷ MRR at start × 100 ``` Healthy SaaS churn varies by segment: SMB churn of 5%/month is normal; mid-market is 1–2%; enterprise is under 1%. ## Voluntary vs involuntary churn - **Voluntary** — customer chose to leave (unhappiness, budget, found a better tool) - **Involuntary** — payment failures, expired cards, billing system issues Involuntary churn is often 20–30% of total churn and is usually recoverable with dunning and card-update workflows. ## Why churn matters In a SaaS model, every churned customer means you have to acquire a replacement just to stand still. At 5% monthly churn you replace your entire book every 20 months. Churn compounds — a 1% improvement in churn often unlocks 10% in long-term revenue. ## How customer operations affects churn Operational excellence reduces churn through: - Faster onboarding (early churn is largest) - Proactive health monitoring (catch at-risk accounts) - Consistent QBRs (re-anchor value) - Lower friction support (frustration drives churn) ## How BlueHill helps reduce churn BlueHill's customer health view, interaction timeline, and status reports make at-risk accounts visible weekly rather than at renewal. Onboarding templates reduce time-to-value (the biggest predictor of first-year churn). Related: [NRR](/glossary/nrr) · [GRR](/glossary/grr) · [Customer health score](/glossary/customer-health-score) · [Renewal](/glossary/renewal) --- # Customer Cohort A **customer cohort** is a group of customers who share a starting characteristic — most commonly the month they signed up — whose behavior is then tracked over time as a single unit. ## Common cohort analyses - **Retention by cohort** — what % of January-2025 signups are still customers 12 months in? - **Expansion by cohort** — how much has the Q1 cohort grown vs the Q3 cohort? - **TTV by cohort** — has time-to-value improved for newer cohorts? - **NRR by cohort** — comparing across acquisition periods ## Why cohort analysis matters Aggregate metrics (total ARR, total customer count) hide trends because they mix old and new customers. Cohort analysis isolates what's happening to *this* group, which reveals whether your motion is improving over time. ## How BlueHill helps Customer records carry signup date and segment tags. Reports can be filtered to compare cohorts (e.g., "Q1 2026 onboarding completions vs Q1 2025"). Related: [Segment](/glossary/segment) · [Lifecycle](/glossary/lifecycle) --- # Customer Satisfaction Score (CSAT) **CSAT** measures customer satisfaction with a specific interaction or experience — usually a support ticket, onboarding session, or product release — on a 1–5 (or 1–10) scale, asked immediately after the event. ## Formula ``` CSAT = (Satisfied responses ÷ Total responses) × 100 ``` "Satisfied" typically means a 4 or 5 on a 1–5 scale. ## When to use CSAT vs NPS - **CSAT** — transactional, specific event ("how was that ticket resolution?") - **NPS** — relational, holistic loyalty ("how likely are you to recommend us?") ## Benchmarks B2B SaaS support CSAT averages 85%. Best-in-class lands at 92%+. ## How BlueHill helps CSAT surveys auto-send after ticket resolution. Responses live on the customer record so a low CSAT on Tuesday's ticket is visible during Thursday's QBR. Related: [NPS](/glossary/nps) · [CES](/glossary/ces) · [Tickets](/glossary/tickets) --- # Customer Health Score A **customer health score** is a composite metric — typically rendered as red/yellow/green or 0–100 — that summarizes how likely a customer is to renew, expand, or churn. ## Common inputs - **Product usage** — DAU/WAU, feature adoption, depth of use - **Engagement** — NPS/CSAT scores, response to outreach, portal logins - **Outcomes** — completion of onboarding milestones, business value achieved - **Sentiment** — support ticket tone, exec engagement - **Contractual** — months until renewal, payment status ## Why health scores matter A good health score lets you triage your CSM book. The 20% of accounts trending red get the proactive intervention; the 60% in green get light-touch motion; the top 20% are expansion candidates. Without a health score, CSMs spread effort evenly — which means the loudest customer (often a healthy one) gets the most attention. ## Common pitfalls - Too many signals → opaque, no one trusts the number - All product signals, no human signals → misses sentiment shifts - Updated monthly, not weekly → too lagging - Not tied to a CS playbook → score moves but no one does anything ## How BlueHill helps BlueHill's interaction-timeline view aggregates the human signals (emails, calls, notes) that pure usage-based health scores miss. Status reports tie health to weekly playbooks. Related: [Churn](/glossary/churn) · [NRR](/glossary/nrr) · [QBR](/glossary/qbr) --- # Customer Journey The **customer journey** is the end-to-end sequence of stages a customer moves through with your company — from first awareness, through evaluation, purchase, onboarding, ongoing use, renewal, and either expansion or churn. ## Common stages 1. **Awareness** — discovers the problem and your product 2. **Consideration** — comparing options 3. **Purchase** — signs the contract 4. **Onboarding** — first 30–60 days 5. **Adoption** — daily / weekly use 6. **Expansion** — adds seats, tiers, modules 7. **Renewal** — contract continues 8. **Advocacy** — refers others, writes reviews ## Why mapping it matters A documented customer journey helps every team — marketing, sales, CS, support, product — know what the customer is experiencing right now and what they need next. Without a map, each team optimizes locally and the customer feels handoff friction. ## How BlueHill helps BlueHill represents every stage of the post-sale journey natively — onboarding templates, ongoing project work, QBRs, renewal pipeline, expansion tracking — so the journey isn't theoretical, it's operational. Related: [Lifecycle](/glossary/lifecycle) · [Milestone](/glossary/milestone) · [Onboarding](/glossary/onboarding) --- # Customer Lifecycle Management (CLM) **Customer Lifecycle Management (CLM)** is the discipline and tooling that orchestrates every stage of a customer's relationship with your company — from first acquisition through onboarding, adoption, growth, renewal, and either advocacy or churn. ## CLM components - **Acquisition** — marketing, sales pipeline - **Onboarding** — first 30–90 days - **Adoption** — ongoing product use - **Renewal** — contract continuation - **Expansion** — upsell / cross-sell - **Advocacy** — promoters becoming brand assets - **Churn / win-back** — recovery motions ## Why CLM matters Treating customers as a single undifferentiated group wastes effort. CLM puts the right motion at the right time — onboarding nudges for new customers, QBRs for adopted customers, retention plays for at-risk customers, advocacy asks for promoters. ## CLM software vs CRM vs Customer Operations - **CRM** — sales pipeline focus - **CLM** — broader post-sale lifecycle - **Customer operations platform** — the workflow plumbing that executes CLM playbooks ## How BlueHill helps BlueHill is the operational layer underneath CLM strategy. Lifecycle stage is a property on every customer; playbooks differ by stage; reports filter by stage. Without operational tooling, CLM is just a slide. Related: [Lifecycle](/glossary/lifecycle) · [Customer journey](/glossary/customer-journey) · [Customer success](/glossary/customer-success) --- # Customer Portal A **customer portal** is a self-service web destination — typically branded as the vendor's product — where customers log in to view their account, submit tickets, upload documents, complete forms, and track project status. ## What a good portal includes - Account summary (contract status, plan, key contacts) - Open and historical tickets - Project/onboarding status - Documents (contracts, invoices, deliverables) - Forms (intake, feedback, change requests) - Resource center (training videos, knowledge base) ## Why portals matter A good portal reduces inbound "what's the status?" emails by 50–70%, especially for implementation-heavy customers. It also serves as a trust signal: serious vendors have portals. ## Common pitfalls - Portal exists but customers don't know about it - Portal exists but isn't kept up-to-date - Portal asks customers to log in to a separate place from the product (creates friction) - Portal looks generic, undermining brand ## How BlueHill helps BlueHill includes a fully branded customer portal on every paid plan. Customers see only the tasks, documents, and forms shared with them. Role-based access ensures the right view for the right person. Related: [Self-service](/glossary/self-service) · [Tickets](/glossary/tickets) · [Onboarding](/glossary/onboarding) --- # Customer Success **Customer success (CS)** is the discipline of proactively ensuring customers achieve their desired outcomes with your product. It's the function that owns post-sale relationship health, retention, and expansion. ## CS vs support vs sales - **Sales** — sells the product - **Support** — reactively resolves tickets - **Success** — proactively drives outcomes - **Operations** — the underlying workflow plumbing that lets all three function ## CS team responsibilities - Onboarding new customers - Running QBRs and EBRs - Tracking customer health - Identifying expansion opportunities - Renewing contracts - Acting as the voice of customer back to product ## Metrics CS owns NRR, GRR, churn rate, expansion rate, time-to-value, NPS/CSAT, customer health score, renewal forecast accuracy. ## How BlueHill helps CS teams Status reports, interaction timelines, customer health views, and onboarding templates give CSMs the operational picture they need without spending half their day in spreadsheets. Related: [Customer operations](/what-is-customer-operations) · [QBR](/glossary/qbr) · [NRR](/glossary/nrr) · [Churn](/glossary/churn) --- # Customer Support **Customer support** is the function that responds to customer questions, issues, and requests. It's typically reactive — the customer reports a problem, support diagnoses and resolves it. ## Support vs success - **Support** — reactive ticket resolution; SLA-driven; metric is response/resolution time - **Success** — proactive outcome management; renewal-driven; metric is retention/expansion Most companies have both, often with shared tooling but separate playbooks. ## Common support channels - Email - In-product chat - Knowledge base / self-service - Phone (enterprise only at most SaaS) - Community forum ## Core support metrics - First-response time - Time to resolution - CSAT / NPS / CES - SLA attainment - Backlog (open tickets) - Cost per ticket ## How BlueHill helps support teams Support tickets, internal notes, and customer history live together. SLAs track automatically. Escalation paths bake into workflow. CS and support share the same customer record, so handoffs are seamless. Related: [Tickets](/glossary/tickets) · [SLA](/glossary/sla) · [Knowledge base](/glossary/knowledge-base) · [Customer success](/glossary/customer-success) --- # Executive Business Review (EBR) An **EBR** is a strategic review between the customer's executive sponsor and the vendor's account executive — annual or semi-annual, much higher altitude than a QBR. ## Agenda 1. Year in review — outcomes against the success plan 2. ROI scorecard — quantified value delivered 3. Strategic alignment — where the customer's business is going 4. Roadmap preview — what's coming from the vendor side 5. Multi-year vision — partnership trajectory 6. Renewal + expansion conversation ## EBR vs QBR - **QBR** — quarterly, tactical, CSM-led - **EBR** — annual, strategic, AE-led with exec sponsor ## How BlueHill helps EBR templates pull rolled-up data — total time invested, tickets resolved, milestones delivered, expansion in seat count — directly from the customer's BlueHill record. Related: [QBR](/glossary/qbr) · [Renewal](/glossary/renewal) · [Success plan](/glossary/success-plan) --- # Escalations An **escalation** is the process of moving a customer issue from the front-line owner to a more senior or specialized resource when it cannot be resolved at the current tier. ## Common triggers - SLA breach (or imminent) - Customer requests "speak to a manager" - Issue requires deeper technical or product knowledge - Bug confirmed and needs engineering involvement - Customer is at risk of churn or has filed a complaint ## Escalation paths - **Tier 1 → Tier 2 / specialist** — for technical complexity - **CSM → CS manager → VP** — for relationship-level escalation - **Support → Engineering** — for product bugs - **Standard → Critical incident** — for outages or data issues ## Tracking escalations Volume of escalations is a key support metric. Healthy support orgs target under 5% of tickets escalated. Higher than that means front-line enablement gaps. ## How BlueHill helps Escalations flag automatically when SLAs breach or specific keywords appear ("furious", "cancel", "lawyer"). Internal notes keep the escalation context visible to everyone in the chain without exposing it to the customer. Related: [Tickets](/glossary/tickets) · [SLA](/glossary/sla) --- # Expansion Revenue **Expansion revenue** is additional recurring revenue from existing customers — upsells, cross-sells, seat additions, and tier upgrades. It's the engine behind NRR above 100%. ## Types of expansion - **Seat expansion** — customer adds users - **Tier upgrade** — Starter → Professional → Enterprise - **Module/add-on purchase** — new SKU added to the contract - **Usage overage** — consumption above included limits ## Why expansion matters Acquiring new customers is 5–7× more expensive than expanding existing ones. The most efficient SaaS growth comes from customers paying you more over time, not just paying for longer. A customer with 130% NRR pays you $1.30 for every $1.00 of starting ARR by year-end. Compound that for 3 years and starting cohorts are worth 2.2× their original value. ## How to drive expansion - **Identify expansion triggers in product usage** — hitting plan limits, adopting advanced features - **Time-based plays** — natural review points (renewal, QBR) - **Customer success initiated** — CSM identifies new use cases - **Automated** — usage-based pricing triggers upsell at hit limits ## How BlueHill helps with expansion BlueHill surfaces utilization signals and milestones on the customer record so CSMs can spot expansion moments earlier. Status reports make it easy to track which accounts are growing vs flat. Related: [NRR](/glossary/nrr) · [Renewal](/glossary/renewal) · [QBR](/glossary/qbr) --- # Gross Revenue Retention (GRR) **Gross Revenue Retention (GRR)** measures the percentage of recurring revenue retained from existing customers over a period, **excluding expansion**. It's the purest measure of churn — what you kept of what you had. ## Formula ``` GRR = (Starting MRR − Contraction − Churn) ÷ Starting MRR × 100 ``` GRR is always ≤ 100% by definition (you can't gain ground without expansion). A GRR of 92% means you lost 8% of the cohort's revenue over the period. ## GRR vs NRR NRR includes expansion; GRR doesn't. If NRR is 120% and GRR is 90%, you're growing — but you're burning a leaky bucket fast. Healthy SaaS companies post GRR ≥ 92%. ## How customer operations affects GRR GRR improves with stronger retention work: better onboarding (fewer early churners), better support (less frustration churn), and proactive health monitoring (catching at-risk accounts before they cancel). ## How BlueHill helps with GRR BlueHill surfaces churn-risk signals on the customer record (drop in interactions, missed milestones, low portal usage) so CSMs can intervene early. The status report view makes it easy to QBR-prep weekly rather than scrambling at renewal. Related: [NRR](/glossary/nrr) · [Churn](/glossary/churn) · [Renewal](/glossary/renewal) --- # Implementation **Implementation** is the technical phase of customer onboarding — the work between contract signature and the customer being live and using the product day-to-day. ## Typical workstreams - **Data import / migration** — from spreadsheets, prior tools, or APIs - **Integration setup** — connecting to existing systems (CRM, email, billing) - **User provisioning** — accounts, roles, SSO - **Configuration** — workflows, templates, automations - **Training** — admins first, then end users ## Implementation models - **Self-serve** — documented checklist, async support - **Concierge / standard** — CSM-led, 4–8 week guided plan - **Professional services** — paid implementation team, custom data work ## Implementation risk The two biggest risks: scope creep (the customer keeps adding requirements) and stakeholder churn (the buyer leaves the company mid-implementation). Mitigate with a tight scope doc and an executive sponsor on both sides. ## How BlueHill helps Implementation templates encode your standard methodology so every customer gets the same proven sequence. Internal notes keep the team aligned on customer-specific nuances without polluting the customer-facing view. Related: [Onboarding](/glossary/onboarding) · [Kickoff](/glossary/kickoff) --- # Customer Kickoff A **customer kickoff** is the formal first meeting between the customer and your implementation or customer success team after the contract is signed. It anchors the onboarding plan. ## What to cover 1. **Why you bought it** — customer recaps the problem they're solving (anchors success criteria) 2. **Stakeholders** — exec sponsor, project owner, end users 3. **Success criteria** — measurable outcomes for 30/60/90 days 4. **Implementation plan** — milestones, owners, dates 5. **Communication cadence** — weekly standup vs biweekly vs Slack 6. **Risks + dependencies** — IT involvement, data access, change management ## Common pitfalls - Skipping the "why you bought it" recap → drift toward features - No exec sponsor identified → escalation path is unclear at first hiccup - Vague success criteria ("better collaboration") → impossible to declare value ## How BlueHill helps Kickoff templates clone with relative dates; kickoff agenda + meeting notes live in the customer interaction timeline; action items become tasks with owners and due dates in one click. Related: [Onboarding](/glossary/onboarding) · [Implementation](/glossary/implementation) · [Success plan](/glossary/success-plan) --- # Knowledge Base A **knowledge base (KB)** is a structured collection of articles, FAQs, troubleshooting guides, and how-to content that customers and agents consult to find answers without contacting support. ## What goes in a KB - **Getting started** — first-week onboarding - **Feature guides** — how each feature works - **Troubleshooting** — error codes, common issues - **FAQs** — quick answers to recurring questions - **Release notes** — what changed - **Integrations** — how to connect to other tools ## Why KBs matter A well-tended KB deflects 30–50% of tickets and shows up in Google for long-tail product queries — driving organic awareness. Agents also use the KB internally as a source of truth. ## KB hygiene - Review every article quarterly for accuracy - Track searches that return no results — that's your content gap list - Tie new article creation to repeated ticket categories - Surface KB suggestions in the support inbox ## How BlueHill helps BlueHill's portal embeds KB articles inline with ticket submission, so customers see relevant answers before asking. Ticket categorization data feeds the KB content roadmap. Related: [Self-service](/glossary/self-service) · [Tickets](/glossary/tickets) --- # Customer Lifecycle The **customer lifecycle** is the model that classifies every customer by what stage they're in. Most B2B SaaS companies use 5 stages: 1. **Onboarding** — first 30–90 days 2. **Adoption** — using the product but not yet at full value 3. **Growth / value** — getting business outcomes; potential expansion 4. **Renewal** — within 90 days of contract end 5. **Advocacy** — referring others, in case studies Each stage has different goals, playbooks, and metrics. ## Why lifecycle staging matters Treating a Day-7 customer the same as a Day-300 customer wastes effort and confuses the customer. A lifecycle model lets CS playbooks be specific to where the customer is right now. ## How BlueHill helps BlueHill tags each customer record with a lifecycle stage. Status reports group accounts by stage. Different automations fire by stage (onboarding → daily nudges; renewal → forecast updates). Related: [Customer journey](/glossary/customer-journey) · [Renewal](/glossary/renewal) · [Advocacy](/glossary/advocacy) --- # Milestone A **milestone** is a defined checkpoint in the customer's journey, tied to a specific outcome that marks meaningful progress. ## Examples - "Account provisioned" (Day 1) - "First admin trained" (Day 7) - "First report generated" (Day 14) - "Go-live" (Day 30) - "First QBR" (Day 90) - "First expansion" (Day 180) - "Renewal commit" (Day 330) ## Why milestones matter Milestones create a shared scoreboard between vendor and customer. They make progress visible, anchor QBR conversations, and let you forecast renewal health (customers who hit early milestones renew at 2–3× the rate of those who don't). ## How BlueHill helps Milestones are first-class objects in BlueHill — tied to onboarding templates, visible on the customer record, surfaced in status reports. Hitting (or missing) a milestone triggers automations or flags health-score changes. Related: [Customer journey](/glossary/customer-journey) · [Onboarding](/glossary/onboarding) · [Success plan](/glossary/success-plan) --- # Net Promoter Score (NPS) **NPS** measures customer loyalty on a single question: "How likely are you to recommend [product] to a friend or colleague?" on a 0–10 scale. ## How it's scored - **Promoters** (9–10) — loyal advocates - **Passives** (7–8) — satisfied but unenthusiastic - **Detractors** (0–6) — at risk of churning or spreading negative WOM **NPS = % Promoters − % Detractors** Range: −100 (worst) to +100 (best). B2B SaaS benchmark: 30–50 is good, 50+ is excellent. ## When to send NPS - 30 days post-onboarding - 6 months in - Quarterly thereafter - After major support interactions (transactional NPS) ## Limitations NPS is a lagging indicator and easy to game. Pair with CSAT, CES, and qualitative feedback. ## How BlueHill helps NPS responses live on the customer's interaction timeline; detractor scores auto-create at-risk tasks; promoter scores feed the advocacy pipeline. Related: [CSAT](/glossary/csat) · [CES](/glossary/ces) · [Voice of customer](/glossary/voice-of-customer) --- # Net Revenue Retention (NRR) **Net Revenue Retention (NRR)** measures the percentage of recurring revenue retained from existing customers over a given period — typically 12 months — including expansion (upsells, cross-sells), contraction (downgrades), and churn. ## Formula ``` NRR = (Starting MRR + Expansion − Contraction − Churn) ÷ Starting MRR × 100 ``` If you started the year with $1M in MRR from a customer cohort, expanded by $200k, lost $50k to contraction, and churned $80k, NRR = ($1M + $200k − $50k − $80k) ÷ $1M = **107%**. ## Why NRR matters NRR above 100% means existing customers grew you net of churn. Best-in-class B2B SaaS companies post 120%+ NRR. Below 90% is a churn problem masquerading as a growth problem. NRR is the single most predictive metric of long-term company health in SaaS — more than CAC, payback period, or even net-new ARR — because it reflects how much customers value the product. ## How customer operations affects NRR Operational excellence drives NRR three ways: 1. **Reducing churn** via faster onboarding (time-to-value), proactive risk management, and consistent QBRs 2. **Driving expansion** by exposing usage data and identifying upsell triggers 3. **Compressing contraction** by addressing health-score signals before renewal conversations ## How BlueHill helps with NRR BlueHill's interaction timeline, status reports, and customer health-score views give CS teams the operational picture they need to spot risk early and run expansion plays at the right moment. Time tracking shows where CSMs spend effort, which often correlates inversely with NRR. Related: [GRR](/glossary/grr) · [Churn](/glossary/churn) · [Expansion revenue](/glossary/expansion-revenue) · [Renewal](/glossary/renewal) --- # Customer Onboarding **Customer onboarding** is the structured process of guiding a new customer from signup or contract signature to first measurable value with your product. ## What good onboarding includes - **Welcome + expectation-setting** — what happens in the next 30 days - **Kickoff call** — alignment on goals, success criteria, timeline - **Implementation steps** — data import, integrations, user provisioning - **Training** — admin enablement, end-user training - **First-value milestone** — the moment the customer feels payoff - **Handoff to ongoing success/support** ## Onboarding by segment - **Self-serve SMB** — async checklists, in-product guides, email nudges - **Mid-market** — concierge CSM, weekly check-ins, 30/60/90 milestones - **Enterprise** — dedicated implementation manager, multi-month rollout ## Why onboarding is critical Early churn (under 90 days) is overwhelmingly caused by onboarding failure. Customers who don't reach value in their first 30 days are 3–5× more likely to churn at first renewal. ## How BlueHill helps Relative-date onboarding templates ("Day 1: send forms; Day 5: kickoff; Day 14: go-live") clone with one click. The customer portal lets customers self-serve documents, forms, and status — eliminating "what's next?" emails. Related: [Time to value](/glossary/time-to-value) · [Kickoff](/glossary/kickoff) · [Implementation](/glossary/implementation) --- # Quarterly Business Review (QBR) A **Quarterly Business Review (QBR)** is a recurring meeting between a CSM (or account team) and a customer — typically the exec sponsor and core stakeholders — to review progress against the success plan, demonstrate value delivered, and align on what's next. ## Agenda (typical 45–60 min) 1. Last quarter recap — what was done, what was missed 2. Value scoreboard — metrics agreed in the success plan 3. Use-case expansion — new ways to leverage the product 4. Roadmap preview — what's coming that's relevant to them 5. Risks and asks — what they need from you, what you need from them 6. Next quarter commitments ## Cadence - **Quarterly** — default for mid-market and enterprise - **Monthly Business Review (MBR)** — for high-touch enterprise - **Executive Business Review (EBR)** — annual, exec-to-exec ## Why QBRs matter A QBR is the renewal pre-conversation. By the time you're 60 days from renewal, the customer should already know they're renewing because the QBR cadence has been demonstrating value all along. Skip QBRs and renewals become surprise conversations. ## How BlueHill helps QBR templates pull data from the customer's BlueHill timeline automatically — tickets resolved, time spent, milestones hit, expansion signals — so CSMs prep in 15 minutes instead of 90. Related: [EBR](/glossary/ebr) · [Success plan](/glossary/success-plan) · [Renewal](/glossary/renewal) --- # Renewal **Renewal** is the moment when a customer's contract term ends and they either continue (renew), upgrade, downgrade, or churn. ## The renewal timeline (mid-market default) - **T-120 days** — renewal forecast created, risk flagged - **T-90 days** — pre-renewal QBR - **T-60 days** — renewal proposal sent (often with expansion) - **T-30 days** — verbal confirmation - **T-0** — paperwork signed, new term begins ## Renewal motion types - **Auto-renewal** — opt-out contracts (most SaaS) - **Active renewal** — customer must affirmatively sign - **Tacit renewal** — month-to-month silently continues ## Risk signals that a renewal is in trouble - Drop in product usage - Champion leaves the company - Reduced response to outreach - Increased support tickets - Failed expansion conversation - Quiet QBR feedback ## How BlueHill helps with renewals The renewal pipeline view in BlueHill rolls up every account by close date, dollar value, and health signal — so you forecast accurately and identify the 20% of renewals that need executive intervention. Related: [Churn](/glossary/churn) · [NRR](/glossary/nrr) · [QBR](/glossary/qbr) · [Success plan](/glossary/success-plan) --- # Customer Segment A **customer segment** is a grouping of customers who share characteristics that warrant differentiated motions. Common segmentation axes: - **Size** — SMB, mid-market, enterprise - **Plan tier** — Starter, Professional, Enterprise - **Industry / vertical** — SaaS, agency, education, healthcare - **Use case** — onboarding-heavy, support-heavy, billable services - **Region** — NAM, EMEA, APAC - **Maturity** — first-year customer vs 5-year tenured ## Why segmentation matters A 1,000-employee bank doesn't want the same CS motion as a 5-person startup. Segmentation lets you build a 1:few playbook for SMB (digital, scalable) and a 1:1 playbook for enterprise (high-touch) without burning your CS budget. ## Common pitfalls - Too many segments (8+) → playbooks become unmanageable - Segments based on intuition not data - Segment doesn't update as customers grow - Tooling can't filter or report by segment ## How BlueHill helps BlueHill tags every customer record with segment fields (industry, plan, ARR band, lifecycle stage). All dashboards and reports filter by segment. Related: [Cohort](/glossary/cohort) · [Lifecycle](/glossary/lifecycle) --- # Self-Service **Self-service** is the model where customers solve their own problems — answers, status checks, account changes, document downloads — via documentation, knowledge base, in-product guides, and customer portals, without contacting a human. ## Why it matters - Customers prefer it for small questions (89% of customers expect a self-service portal) - Deflects 30–50% of support volume - Available 24/7 - Scales without linear headcount growth ## Self-service ingredients - Searchable knowledge base - Branded customer portal - In-product tooltips and onboarding flows - Status / progress dashboards - Self-serve account management (cancel, upgrade, change payment) - Community / forum (for larger products) ## When self-service falls short - Complex multi-step issues - Account-specific data needed - Emotional / sensitive issues (billing disputes) - New user with no context The best CX strategies offer self-service as default + easy escalation to human when needed. ## How BlueHill helps BlueHill's customer portal ships with self-service ticket submission, document upload, status visibility, and form completion. Knowledge-base embedding suggests articles inline before ticket creation. Related: [Knowledge base](/glossary/knowledge-base) · [Customer portal](/glossary/customer-portal) · [CES](/glossary/ces) --- # Service Level Agreement (SLA) A **Service Level Agreement (SLA)** is a documented commitment to specific levels of service. SLAs typically cover: - **First-response time** — e.g., reply within 4 business hours for high-priority tickets - **Resolution time** — e.g., resolve within 2 business days - **Uptime** — e.g., 99.9% monthly platform availability - **Penalty** — what the customer gets if you miss (credits, refunds, exec engagement) ## SLA tiers Common pattern is to tier by customer plan: - Starter — 24-hour first response, no resolution SLA - Professional — 8-hour first response, 2-day resolution - Enterprise — 1-hour first response, custom resolution, 99.9% uptime ## Why SLAs matter For enterprise procurement, SLAs are non-negotiable. For SMB, they're a trust signal. Miss them too often and renewals get harder. ## How BlueHill helps SLA timers attach to tickets automatically based on customer tier. Breaches escalate to managers. Reports show SLA-attainment rates by team, category, and customer cohort. Related: [Tickets](/glossary/tickets) · [Escalations](/glossary/escalations) --- # Success Plan A **success plan** is a written document — typically 1–3 pages — outlining a customer's goals with your product, the metrics that define success, the joint workplan to get there, and the cadence for reviewing progress. ## Components - **Customer's business objective** — why they bought - **Success criteria** — 2–4 measurable outcomes - **Joint workplan** — milestones with owners and dates - **Risks and dependencies** — what could go wrong - **Cadence** — when you review (weekly during onboarding, monthly thereafter) - **Stakeholders** — exec sponsor, project owner, end users ## When to write one - During implementation kickoff - At first renewal (re-anchor) - After major usage expansion (new use case) ## Why success plans matter Without one, "value" is subjective. With one, every QBR has a clear scoreboard. Customers with a documented success plan churn at 30–50% lower rates than customers without one. ## How BlueHill helps Success plan templates live in BlueHill and reference the customer's tasks, milestones, and time-tracking data — so the plan is grounded in real activity, not just a Google Doc that nobody opens. Related: [Kickoff](/glossary/kickoff) · [QBR](/glossary/qbr) · [Customer journey](/glossary/customer-journey) --- # Tickets A **ticket** is the unit of work in a help desk or support system — a recorded customer issue, question, or request that an agent works through to resolution. Tickets are typically created via email, web form, in-product widget, or phone. ## Ticket states - **New / open** — created, unassigned - **Assigned** — has an owner - **In progress** — being worked - **Pending customer** — waiting on customer reply - **Resolved** — fix delivered, awaiting confirmation - **Closed** — confirmed resolved ## Ticket properties - Priority (low / normal / high / urgent) - Category (bug, feature request, billing, general) - SLA target (e.g. first response in 4 hours) - Owner - Customer record (linked) ## Ticket vs. task A ticket is customer-originated; a task is internal-originated. BlueHill treats both as work items linked to customers but maintains the distinction for reporting. ## How BlueHill helps Tickets live alongside tasks, notes, emails, and time entries on the customer record. SLA timers run automatically. Internal notes let agents collaborate without polluting customer-facing replies. Related: [SLA](/glossary/sla) · [Escalations](/glossary/escalations) · [Knowledge base](/glossary/knowledge-base) --- # Time to Value (TTV) **Time to Value (TTV)** is the elapsed time between a customer signing up (or signing a contract) and realizing their first measurable outcome from your product. ## Two flavors - **Time to first value (TTFV)** — quickest taste; e.g., first dashboard rendered, first invoice sent, first ticket resolved - **Time to full value** — entire intended workflow live; e.g., team fully onboarded and using core features daily ## Why TTV matters TTV is the strongest predictor of first-year churn. Customers who don't reach value quickly start to question the purchase and disengage. Best-in-class SaaS aims for TTFV under 14 days and time-to-full-value under 60 days for SMB; 30/120 days for mid-market. ## How to compress TTV - Pre-built templates (onboarding workflows, dashboards, integrations) - Concierge onboarding for high-value accounts - Async checklist + automated nudges for self-serve - Remove friction: fewer required fields, smarter defaults, in-product guidance ## How BlueHill helps with TTV Relative-date onboarding templates clone in one click and auto-schedule against the customer's start date. The customer portal eliminates a half-dozen "what's next" emails. Internal notes keep CSMs aligned without slowing the customer down. Related: [Onboarding](/glossary/onboarding) · [Kickoff](/glossary/kickoff) · [Customer health score](/glossary/customer-health-score) --- # Voice of Customer (VoC) **Voice of Customer (VoC)** is the systematic process of capturing customer feedback — quantitative scores, qualitative comments, feature requests, complaints, ideas — and routing it to product, marketing, and CS teams to act on. ## VoC sources - Surveys (NPS, CSAT, CES, in-app, post-onboarding) - Support tickets and customer emails - Sales calls (won and lost) - CSM check-ins and QBRs - Community forums and social media - Product analytics - Win-back interviews from churned customers ## VoC outputs - Themed feedback reports (monthly) - Feature request roadmap - Risk early-warning system - Sales objection handling - Marketing message refinement ## Common pitfalls - VoC data collected but never synthesized - Synthesized but never shared with product - Shared with product but not prioritized - "We listened" → no visible action → trust erodes ## How BlueHill helps Survey responses, ticket sentiment, and CSM notes all land on the customer record. Tag-based filters surface themes ("billing", "performance", "integrations") so product can prioritize from real data. Related: [NPS](/glossary/nps) · [CSAT](/glossary/csat) · [Advocacy](/glossary/advocacy)