Klaviyo customer issue → Cursor PR → three-day ship (vendor case)

Source and standing. Linear’s customer case study with Klaviyo product-ops director Christina Valente, accessed September 30, 2026. First-party vendor interview/case account, not a public ticket, code review or independent audit; the article shows Klaviyo switched in January 2026 but no explicit publication date.

One described chain. A Klaviyo customer reported an issue to support; the Linear–Zendesk integration routed it to a team; a PM reviewed it and delegated the work to Cursor inside Linear. Cursor drafted a PR for engineering review, and the case says Klaviyo shipped a fix in three business days. Separately, Valente says updates formerly taking her 30–45 minutes take ~5 minutes with Linear context and an agent; this is self-reported status-writing time, not time saved on the described customer issue.

Rights and missing terminal state. Agent drafts; PM chooses to delegate; engineer reviews. No issue/PR link, baseline comparison, test or acceptance revision, time for PM and engineering, customer confirmation, ticket closure, reopen, later usage or repair. The article’s claim that the change ‘improved the customer experience’ is not accompanied by a customer outcome measure. This is a genuine one-firm support-to-ship account, but it stops before verified requester closure. Unlike Linear’s own composite workflow, it describes a specific anonymous customer issue; do not splice the two into one trace.

What to ask next. Did CX contact the reporter and confirm it solved their original issue? Was the feature released to that customer? Did the customer reopen? What did PM/engineer review cost? Was the fix stable after 30 days? Relates to agent-owned closure, feature trace, and role boundaries.