Automate Post-Purchase NPS Surveys: Klaviyo + Gorgias 2026

Key Takeaways

• Post-purchase NPS surveys sent via Klaviyo within 5–7 days of delivery capture feedback when the experience is fresh — response rates drop sharply after 14 days.

• Routing low NPS scores (0–6) automatically to Gorgias support tickets turns a passive signal into an active recovery opportunity before the customer leaves a public review.

• The full workflow — order fulfilled → Klaviyo survey → score captured → conditional routing → Gorgias ticket or Klaviyo promoter flow — can be built in 2–3 days with existing tools.

• High NPS scores (9–10) are equally actionable: automated promoter flows that ask for reviews and referrals convert satisfied customers into growth levers.

• DTC brands that close the NPS feedback loop (survey → response → resolution) see meaningfully higher repeat purchase rates than brands that collect feedback but don't act on it.

Automating post-purchase NPS surveys means that when an order is delivered, a Klaviyo flow triggers a Net Promoter Score survey email automatically, the customer's score response fires a webhook, and the score is routed — low scores to Gorgias support tickets, high scores to a review request flow — without any manual intervention from your customer success team.

TL;DR: Build once, run on every order. A low NPS score creates a Gorgias ticket and routes it to the right agent. A high NPS score triggers a review request sequence. Your team sees every signal in real time without reading every survey response manually.

Why NPS Automation Is Now Table Stakes for DTC

Manual NPS programs fail for a predictable reason: someone has to read the survey responses, triage the low scores, and decide who to contact and when. In a DTC brand shipping 200–2,000 orders per month, that triage becomes a full-time job — or, more commonly, it doesn't happen at all and the survey data sits in a spreadsheet no one reviews.

Cart abandonment rates remain extremely high in ecommerce — the majority of shoppers who add items to a cart don't complete a purchase, according to the Baymard Institute 2025 abandonment study. The post-purchase phase is where DTC brands have the best opportunity to convert a one-time buyer into a loyal customer — but that opportunity closes quickly if a bad experience goes unaddressed.

NPS automation closes the gap: the signal is captured, triaged, and acted on at machine speed, without relying on a team member to monitor a dashboard.

Who This Is For

This workflow recipe is designed for:

• DTC and ecommerce brands shipping 100+ orders per month on Shopify or Shopify Plus

• Brands already using or planning to use Klaviyo for email marketing and Gorgias for customer support

• Customer experience and retention teams that want to act on NPS data, not just collect it

• Operators who are tired of manually reviewing survey responses and routing tickets

Red flags: Skip this if you're shipping fewer than 50 orders per month — at that volume, manual review of NPS responses takes under 30 minutes and automation overhead doesn't pay back. Also skip if you don't have Gorgias (or a comparable support ticketing system with an API) — the escalation half of this workflow requires a real support platform, not just an email inbox.

The Workflow Recipe: Step-by-Step

This is the complete NPS automation chain. Each step describes what triggers it, what system handles it, and what the output is.

1. Trigger: order delivered. When Shopify marks an order as "Delivered" (or after a configured delay from fulfillment, typically 5–7 days), Klaviyo fires the NPS survey flow. Use the "Fulfilled Order" event in Klaviyo with a 5-day delay — this gives the package time to arrive before the survey lands.

2. Send the NPS survey email. The Klaviyo email contains a single-question NPS prompt: "How likely are you to recommend [Brand] to a friend? (0–10)." Each number is a clickable link containing a URL parameter with the score value. No external survey tool is required — the links do the work.

3. Capture the score via URL parameter. When the customer clicks a number (e.g., 7), they land on a confirmation page at your site (or a Typeform one-question page). The URL contains ?nps_score=7&order_id=12345. A Klaviyo webhook or JavaScript snippet fires to record the score against the customer profile.

4. Update the Klaviyo customer profile. The NPS score is written to a custom property on the Klaviyo customer profile (NPS Score: 7, NPS Date: 2026-06-01). This makes the data available for segmentation, filtering, and future flow logic.

5. Branch by NPS segment. Klaviyo's flow builder supports conditional splits. After the score is recorded, the flow branches into three paths:

   • Detractors (0–6): Route to recovery workflow

   • Passives (7–8): Route to a lightweight engagement email ("Tell us how we can do better")

   • Promoters (9–10): Route to review request + referral flow

6. Create a Gorgias ticket for detractors. Using a Klaviyo webhook (or Zapier/Make bridge), fire a POST request to the Gorgias API when a score of 0–6 is recorded. The ticket body includes: customer name, order number, NPS score, and the survey date. Tag the ticket with "NPS-Detractor" and assign it to the appropriate support queue.

7. Assign and prioritize the ticket. Configure Gorgias automation rules to assign NPS-Detractor tickets to a dedicated retention-trained agent or team. Set priority to "High" for scores of 0–3 and "Normal" for 4–6. This ensures the worst experiences get the fastest human response.

8. Send the detractor outreach email. The assigned Gorgias agent receives the ticket and sends a personalized recovery email within 4 business hours. The email acknowledges the experience, offers a resolution (replacement, refund, or discount), and invites the customer to reply directly to explain what went wrong.

9. Send the promoter review request. For scores of 9–10, the Klaviyo flow sends a review request email 24 hours after the NPS confirmation: "We're so glad you love [Brand]! Would you take 2 minutes to share your experience?" Include direct links to Google, Trustpilot, and your most-used review platform.

10. Send the promoter referral offer. Seven days after the review request, if the customer clicked the review link (tracked via Klaviyo click data), a second email offers a referral reward: "Share your code with a friend and get 15% off your next order."

11. Log outcomes in your analytics dashboard. Configure Klaviyo metrics to track NPS survey send rate, response rate, score distribution, and Gorgias ticket creation rate. Review these weekly to monitor trends and flag product or shipping issues that drive detractor spikes.

12. Close the loop with a follow-up survey. Ninety days after a detractor recovery, automatically send a 1-question follow-up: "Has your experience with [Brand] improved?" Scoring this cohort over time tells you whether your recovery process actually works.

Tool Comparison: Delighted vs. Klaviyo vs. Gorgias vs. US Tech Automations

Where Delighted genuinely wins: If you want a best-in-class standalone NPS dashboard with response analytics, trend charts, and team digest reports, Delighted ($224/month and up) is purpose-built for that job. It integrates with Slack, Salesforce, and Segment natively. The trade-off is that you're adding another tool and another monthly fee on top of Klaviyo and Gorgias — and you still need an integration layer to route low scores to Gorgias tickets.

Where Klaviyo wins: If you're already paying for Klaviyo and want to avoid adding Delighted, Klaviyo's URL-parameter NPS method (described in step 3 above) captures scores at no additional cost and keeps everything in your existing platform. The analytics aren't as rich as Delighted, but the data is actionable.

When NOT to use US Tech Automations: If your support volume is low enough that a Gorgias agent manually checks for low NPS scores each morning and creates their own tickets, that manual process may be fine at 20–30 orders/day. US Tech Automations is most valuable at higher order volumes (100+ orders/day) where manual triage at scale is clearly impossible.

Benchmarks: What Good NPS Automation Looks Like

US ecommerce retail sales are growing year over year, according to eMarketer's 2025 forecast, with DTC brands capturing an increasing share of that growth. The brands winning in this environment are those that turn post-purchase data into retention action, not just reporting.

Survey Timing: When to Fire the NPS Email

Timing is the single biggest lever on NPS response rate. Surveys that land within a week of delivery consistently outperform those sent later, according to email engagement benchmarks across DTC senders.

Response rates can fall by more than 50% once a survey is sent beyond the 14-day window, according to Klaviyo's 2024 email engagement benchmark report, which is why the recipe above anchors the trigger to a 5-day post-delivery delay. Roughly 65% of DTC support escalations that start as low NPS scores are resolvable with a single agent reply, according to the Gorgias 2024 customer experience benchmark, reinforcing the value of routing detractors to a ticket rather than a dead-end survey field.

Klaviyo Flow Architecture: What the Branching Looks Like

The Klaviyo flow for NPS automation has this structure:

Trigger: Fulfilled Order + 5-day delay
  ↓
Send: NPS Survey Email
  ↓
Wait: Up to 7 days for click
  ↓
Conditional Split: Did customer click a score?
  → YES: Score captured (0-10)
      ↓
      Conditional Split: Score value
        → 0-6 (Detractor): Fire webhook → Gorgias ticket
        → 7-8 (Passive): Send "Help us improve" email
        → 9-10 (Promoter): Send review request → 7-day delay → referral offer
  → NO: End flow (no survey response)

This architecture means the majority of customers who don't respond simply exit the flow — you don't pester non-responders with follow-ups that erode email deliverability.

The Passive Segment: Often Ignored, Highly Actionable

Most brands focus their NPS automation on detractors (who need rescue) and promoters (who can drive growth). Passives — the 7–8 scorers — are frequently ignored. That's a mistake.

Passives are your most convertible segment for NPS improvement. They had an acceptable experience but weren't delighted. A targeted email asking one specific question — "What would have made your order experience a 10?" — generates qualitative feedback that is extraordinarily useful for product and logistics improvements.

Shopify Plus merchants investing in retention and loyalty programs show meaningful GMV growth year over year, according to the Shopify Plus 2024 Merchant Report. The passive NPS segment, when properly engaged, often converts to promoters in subsequent purchase cycles — making them a compounding retention asset.

Common Mistakes in DTC NPS Automation

Sending the survey before the package arrives. Triggering off "Order Fulfilled" (when it ships) rather than "Order Delivered" (when it arrives) means customers get the NPS email before they've experienced the product. Response rates are lower and scores are meaningless. Use delivery event triggers or a 7–10 day delay from fulfillment.

Routing all low scores to the same queue. A score of 1 from a customer whose order was lost in transit needs a different response than a score of 5 from someone who wanted a different color. Segment by score range (0–3 = urgent, 4–6 = moderate) and by issue type if your support tool supports tagging by first response category.

Not closing the ticket loop. Many brands create Gorgias tickets for detractors but never record the resolution outcome. Without tracking resolution rate and post-resolution satisfaction, you can't improve your recovery process. Add a mandatory "Resolution" tag in Gorgias when a detractor ticket is closed.

Over-segmenting the promoter flow. Some brands build elaborate promoter nurture sequences with five emails over 30 days. Response rates drop sharply after the first two touchpoints. A two-email promoter flow (review request + referral offer) captures 80% of the available value with 20% of the complexity.

Ignoring the data trend. An NPS automation that collects scores without weekly trend review is just generating noise. Set up a Gorgias report or Klaviyo metric that shows NPS distribution by week, with alerts for any week where the detractor rate increases by more than 5 percentage points.

FAQs

Do I need a third-party NPS tool like Delighted or Typeform?

No — Klaviyo can run NPS surveys natively using URL parameters (each score = a unique link). The trade-off is that Klaviyo's NPS analytics aren't as visual as Delighted. If you want a polished NPS dashboard with trend charts, Delighted is worth the cost. If you primarily care about acting on scores rather than analyzing them in depth, Klaviyo alone works.

How do I handle customers who respond to NPS but don't explain why?

The survey flow should ask a follow-up question on the landing page: "Thank you for your score! What's the main reason for your score?" This open-text field captures the qualitative context that makes the quantitative score actionable. Even a single sentence ("my package arrived damaged") tells your Gorgias agent exactly what to address.

What NPS score threshold should trigger a Gorgias ticket?

The standard practice is to ticket all scores of 0–6 (detractors). Some brands extend this to 7s (low passives). The key variable is your support team capacity — ticketing every score below 8 is valuable data but requires more agent time. Start with 0–6 and expand to 7 once your recovery process is running smoothly.

Can I use this workflow with a Shopify store that isn't on Shopify Plus?

Yes. Klaviyo and Gorgias both work with standard Shopify plans. The integration between Klaviyo and Shopify fires on the same fulfillment events regardless of Shopify plan tier. Shopify Plus gives you access to additional checkout customization and script capabilities, but none of those are required for this NPS workflow.

How often should I review NPS data?

Weekly trend review is the minimum recommended cadence. Look at: NPS survey response rate (are open rates dropping?), score distribution (are detractors increasing?), Gorgias ticket resolution rate (are recoveries actually happening?), and promoter review conversion. Monthly, do a deeper dive into the qualitative feedback to identify product, shipping, or service patterns.

What if a customer submits multiple NPS scores (e.g., multiple orders)?

Configure your Klaviyo flow to check whether the customer has completed an NPS survey in the last 90 days before enrolling them in the flow. This prevents survey fatigue for frequent buyers and keeps your score data from being skewed by the same customer's repeated responses.

Build Your NPS Recovery Loop Today

If your brand ships more than 100 orders per month and you're not systematically capturing and acting on NPS data, you're leaving retention revenue on the table with every order.

US Tech Automations builds the full NPS automation stack: Klaviyo flow architecture, Gorgias API integration, scoring logic, and analytics configuration — done for you, maintained by us. Visit our pricing page to see what a complete NPS automation build costs, or explore the full platform at ustechautomations.com.

For related ecommerce automation reading, see our guides on how DTC brands recover 25% of failed payments, building VIP customer segments in Shopify, and how DTC brands cut support tickets by 30%. For broader operations automation, our guide on saving 15 hours weekly on DTC ops covers complementary workflows in the same stack.