Net Promoter Score tells you one number. What it does not tell you, on its own, is which moment in the customer journey produced that number. That is the gap transactional NPS closes.

If you have ever looked at a healthy quarterly NPS and still watched churn creep up, or seen a support ticket resolution rate hit target while customers quietly stopped recommending you, the problem is usually measurement granularity, not customer sentiment. This guide covers everything you need to run a transactional NPS program end to end: the definition, the formula, worked calculation examples, the full comparison against relational NPS, every common survey type, benefits, limitations, and a concrete rollout plan you can act on this week.

What is transactional NPS?

Transactional NPS (tNPS) is a variant of the standard Net Promoter Score that measures customer loyalty immediately after a specific interaction or transaction, rather than customer sentiment toward the brand as a whole. Instead of asking customers how likely they are to recommend the company in general, a tNPS survey asks how likely they are to recommend the company based on the purchase, support call, delivery, onboarding session, or other touchpoint they just experienced.

Net Promoter Score itself was developed by Fred Reichheld with Bain & Company and Satmetrix in 2003, built around a single question: “How likely is it that you would recommend [Organization X] to a friend or colleague?” Bain’s own research found that companies with industry-leading NPS scores grow more than twice as fast as competitors, which is why the metric spread so widely. Transactional NPS takes that same question and anchors it to a moment in time instead of a general impression.

The key distinguishing features of tNPS are:

• Trigger-based timing. The survey fires automatically off an event (order placed, ticket closed, shipment delivered), not on a calendar.
• Touchpoint-specific wording. The question references the transaction directly (“based on your recent purchase” or “based on today’s support interaction”) instead of the brand in the abstract.
• High actionability. Because the feedback is tied to one interaction, the team that owns that interaction can act on it directly, often within hours.
• Identifiable respondents. Unlike anonymous brand-tracking surveys, tNPS responses are usually tied to a customer record, so a low score can trigger a same-day follow-up call.

How to calculate transactional NPS

The tNPS formula is identical to standard NPS. Only the timing and framing of the question change.

Step 1: Ask the question. “Based on your recent [purchase/support call/delivery/onboarding], how likely are you to recommend [Company] to a friend or colleague?” on a 0 to 10 scale.

Step 2: Sort responses into three buckets.

Step 3: Apply the formula.

tNPS = % of Promoters − % of Detractors

Passive responses count toward your total respondent base but are excluded from the subtraction itself. The result always falls between -100 and +100.

Worked example: Say 200 customers respond to a post-purchase tNPS survey. 100 score you 9 or 10 (50% promoters), 50 score you 7 or 8 (25% passives), and 50 score you 6 or below (25% detractors).

tNPS = 50% − 25% = 25

A tNPS of 25 for that specific transaction is a positive score, but the real value is comparing it against your relational NPS and against tNPS scores for other touchpoints. If your overall brand NPS is 45 but your post-purchase tNPS is 25, you have found a specific leak in the funnel worth investigating before it drags down brand-level loyalty.

Transactional NPS vs relational NPS

This is the comparison most people searching for tNPS actually want answered, so here it is in full.

Relational NPS (also called brand NPS, or simply “NPS”) measures a customer’s overall sentiment toward your company as a whole, independent of any single interaction. It is collected at regular intervals, typically quarterly or annually, and sent to a broad, often randomized sample of your customer base regardless of what they have recently done.

Transactional NPS measures satisfaction with one specific, recent interaction. It is collected immediately after that interaction occurs, sent only to customers who actually went through that touchpoint, and scoped narrowly to that experience.

Side-by-side comparison

The core distinction in one sentence

Relational NPS tells you if customers are loyal. Transactional NPS tells you why, by pinpointing which touchpoint is helping or hurting that loyalty.

Neither metric is objectively better than the other; they answer different questions. Relational NPS gives you a defensible, board-level number you can benchmark year over year. Transactional NPS gives you the granular, fast-moving signal your operational teams need to fix things this week. Most mature CX programs treat this as a pairing, not a choice.

When to use tNPS, rNPS, or both

Use relational NPS when you need to:

1. Report a single, company-wide loyalty number to leadership or the board.
2. Benchmark your performance against competitors or industry standards.
3. Track long-term trends in brand perception across quarters or years.
4. Make strategic, resource-allocation-level decisions that affect the whole business.

Use transactional NPS when you need to:

1. Diagnose which specific touchpoint is dragging down (or lifting) your overall score.
2. Give a frontline team (support, delivery, onboarding) a metric they can act on directly.
3. Catch and resolve an unhappy customer’s issue before it becomes churn or a public complaint.
4. Measure the impact of a specific process change, feature launch, or team training initiative.

Use both together if you want the full picture. A common and effective sequencing:

1. Start with relational NPS to establish a baseline and understand overall brand sentiment.
2. Layer in transactional NPS at your two or three highest-impact touchpoints (usually purchase and support).
3. Use the transactional data to explain movements in your relational score over time.
4. Expand transactional coverage to additional touchpoints only once the first ones are generating consistent, actionable volume.

Types of transactional NPS surveys

Any customer touchpoint can technically carry a tNPS survey, but these are the most common and highest-value applications.

Post-purchase surveys

Sent immediately after checkout completes, whether online or in-store. These capture friction in navigation, checkout flow, payment options, and delivery expectations. A clunky checkout process is one of the most common causes of cart abandonment and a depressed transactional score, so this is usually the first touchpoint teams instrument.

Customer support / ticket close surveys

Sent the moment a support ticket, live chat, or call is resolved. This is arguably the highest-signal touchpoint for tNPS because support interactions are emotionally charged: a fast, empathetic resolution can create a promoter out of a frustrated customer, while a slow or robotic one can turn a minor issue into a detractor.

Post-delivery / fulfillment surveys

Sent after a product ships or arrives. Useful for retail, e-commerce, and logistics-heavy businesses where the gap between “order placed” and “product in hand” is itself a major satisfaction driver.

Onboarding surveys

Sent at the end of a new customer’s onboarding flow or first-use period. Onboarding sets the tone for the entire relationship, and a tNPS survey here surfaces friction in setup, documentation gaps, or unclear next steps before the customer has fully committed to the product.

Post-product-update / feature-release surveys

Sent to customers who have used a new feature or update for a set period, usually a week or more. Waiting is deliberate: sending this survey the moment a feature ships, before anyone has actually used it, produces noise instead of signal.

In-store / in-person experience surveys

Sent immediately after a customer’s physical visit, via SMS, QR code, or tablet at checkout. Captures staff interaction quality, layout, and product availability while the visit is still fresh.

Website and digital experience surveys

Triggered by specific on-site actions like completing a form, finishing a self-service task, or exiting after a redesign. Particularly valuable around website relaunches, where you want a before-and-after read on user sentiment.

Follow-up and event-triggered surveys

Any survey fired automatically off a defined event in your CRM or product analytics, such as a subscription renewal, a downgrade, or a specific in-app action. These extend tNPS beyond the “classic” touchpoints listed above to whatever moments matter most in your specific customer journey.

Benefits of transactional NPS

Real-time signal, not stale sentiment. Feedback captured minutes or hours after an interaction reflects what actually happened, not a reconstructed memory from weeks earlier. This matters because customer memory of an experience degrades and gets rewritten by subsequent events surprisingly fast.

Pinpoint accountability. Because the score is tied to a specific touchpoint, you can route it directly to the team that owns that touchpoint. A support tNPS dip is a support team problem. A checkout tNPS dip is a product or engineering problem. This precision is something relational NPS structurally cannot give you.

Faster close-the-loop cycles. A detractor identified two hours after a bad support call can be called back the same day. A detractor identified in a quarterly relational survey may have already churned by the time anyone reads the response.

Clearer driver analysis. Pairing the 0–10 score with a follow-up “why” question at the transactional level produces cleaner, less confounded qualitative data than asking someone to explain months of accumulated brand sentiment in one open text box.

Better resource allocation. Comparing tNPS scores across touchpoints tells you exactly where to invest, fix budget, training time, or process redesign effort, instead of guessing.

A leading indicator for relational NPS. Sustained low tNPS at a high-traffic touchpoint (support, checkout) is one of the earliest warning signs that your relational NPS is about to decline. Catching this early, before it shows up in the quarterly number, is one of the strongest arguments for running tNPS at all.

10 Examples of transactional NPS questions

Use these as starting templates. Keep the core NPS question first and unchanged in scale; adapt the framing and follow-ups to the touchpoint.

1. On a scale of 0–10, how likely are you to recommend [Company] based on your recent [purchase/support interaction/delivery]?
2. What is the primary reason for your score?
3. Were you satisfied with the [product/service] you received today?
4. How would you rate the ease of [purchasing/using/getting support] from [Company] today?
5. Did our [product/service/support] meet your expectations? Why or why not?
6. How likely are you to purchase from us again or use our services in the future?
7. Did you run into any issues during your recent interaction with [Company]? If so, please describe them.
8. How would you rate the professionalism and helpfulness of the [sales/support/service] team you worked with?
9. Is there anything we could have done differently to improve this experience?
10. Is there anything else you would like to share about your recent experience with us?

Keep the total survey under 3–4 questions wherever possible. Transactional surveys live or die on response rate, and length is the single biggest lever you control.

How to build a transactional NPS program in 7 steps

Step 1: Map your customer journey and list every touchpoint. Write down every meaningful interaction a customer has with your business, from first purchase through renewal or repeat purchase. Include payment, delivery, support, onboarding, in-app milestones, and any physical or in-person moments.

Step 2: Prioritize two or three touchpoints to start. Pick the highest-volume, highest-impact touchpoints first, usually purchase and support. Do not try to instrument every touchpoint on day one; this is the fastest route to survey fatigue and diluted response quality.

Step 3: Choose your delivery channel and trigger. Decide whether the survey fires by email, SMS, in-app modal, or on-device tablet, and connect it to the event that should trigger it (order confirmation webhook, ticket-closed status change, delivery confirmation). Automating this through your CRM or helpdesk integration is what makes tNPS “real-time” rather than manually batched.

Step 4: Write a short, touchpoint-specific survey. One NPS question, one open-ended “why,” and at most one or two targeted follow-ups. Reference the specific transaction in the question wording so respondents know exactly what they are rating.

Step 5: Set a closed-loop response protocol before you launch. Decide in advance who owns follow-up for detractors (score 0–6), what the response SLA is (same-day is standard for high-value accounts), and what the escalation path looks like for scores of 0–3.

Step 6: Route scores to the owning team automatically. A support tNPS score should land with support leadership, not sit in a shared CX dashboard nobody checks. Automated routing by touchpoint is what keeps the program actionable rather than decorative.

Step 7: Review trends monthly and compare against relational NPS. Track each touchpoint’s tNPS over time, watch for divergence between touchpoints, and check whether transactional movements are showing up in your quarterly relational score a few months later. This is also when you decide whether to expand coverage to additional touchpoints.

Common mistakes to avoid

• Surveying every touchpoint at once. Start narrow, prove the loop closes, then expand.
• Sending the survey too early. For product and onboarding touchpoints especially, sending immediately after signup instead of after real usage produces shallow, premature feedback.
• Treating tNPS and rNPS as interchangeable. Reporting a touchpoint’s tNPS as if it were your company-wide NPS misleads stakeholders and invites bad strategic decisions.
• Collecting scores without a follow-up plan. If detractor responses do not trigger a human follow-up, you are training unhappy customers to stop bothering to tell you anything.
• Ignoring the qualitative “why.” The 0–10 number tells you something changed; the open-text comment tells you what to fix. Programs that only track the score and skip the comment analysis leave most of the value on the table.
• Comparing raw scores across touchpoints with very different baselines. A support tNPS and a checkout tNPS are not directly comparable in absolute terms; track each touchpoint’s trend over time rather than treating all scores as one universal scale.

FAQ

What is transactional NPS in simple terms?

Transactional NPS is a Net Promoter Score collected right after a specific customer interaction, like a purchase or support call, instead of at a scheduled interval about the brand overall. It tells you how that one moment landed with the customer.

What is a good transactional NPS score?

There is no universal “good” number because tNPS baselines vary widely by industry and touchpoint. The more useful benchmark is your own trend over time and the comparison between touchpoints, not a single external target. As a general reference, positive scores (above 0) indicate more promoters than detractors, and scores above 50 are typically considered strong in most B2C contexts.

How often should you send transactional NPS surveys?

Immediately, or as close to immediately as possible, after the triggering event. For post-purchase and support touchpoints, this typically means within minutes to hours. For product-usage touchpoints, waiting a week or more after the triggering event gives customers enough time to form a real opinion.

Can a business use both transactional and relational NPS?

Yes, and most mature CX programs do. Relational NPS provides the strategic, board-level number and long-term trend line; transactional NPS provides the tactical, touchpoint-level diagnostics that explain what is driving that trend.

Is transactional NPS the same as CSAT?

No. CSAT (Customer Satisfaction Score) typically asks about satisfaction with a specific interaction on a 1–5 scale and measures short-term contentment. Transactional NPS uses the 0–10 recommend-to-a-friend framing and measures loyalty, not just satisfaction, at the transactional level. The two metrics often correlate but answer slightly different questions and are commonly used together.

Who should own transactional NPS data inside a company?

Ownership should sit with whichever team owns the touchpoint being measured. Support tNPS belongs with support leadership; checkout tNPS belongs with product or e-commerce; onboarding tNPS belongs with the onboarding or customer success team. A central CX or insights function typically owns the tooling and reporting layer, while action ownership stays distributed.