# See the whole pipeline, and tune it

Every stage from cancellation to win-back, on one canvas — what fired, what's waiting, what's off, and what each step is producing.

Canonical URL: https://whyleft.com/features/playbooks

## Benefits

### A visualization, not homework

The pipeline is code that already works. The canvas is there for you to inspect and tune it — you never have to assemble a workflow before the product does anything.

### Live numbers on every stage

How many cancellations entered, how many emails went out, how many replied, how many completed, how many came back. The funnel, in place, on the thing that produced it.

### Tune what matters

Delays, which segments get win-back offers, whether sends need your approval — adjustable per stage without touching the rest.

## Win-back, targeted by what they actually said

A generic "we miss you" email to everyone who ever cancelled is spam with a nicer subject line. The interesting version is narrower: email the customers who left over a specific thing, once you've shipped that specific thing.

Because every interview is tagged and the text is kept, WhyLeft knows which customers said what. When you fix the integration gap, the people who left over integrations are a list — not a guess.

You approve every send, or you let it run. Recovered revenue is attributed back to the interview it came from, so you can see whether the loop is actually paying for itself.

## In practice: Shipping the thing they left over

You finally build the export people kept asking for. Instead of announcing it to everyone and hoping, you email the eleven customers who explicitly named it as their reason for leaving — with a message that references what they told you.

## Related

- https://whyleft.com/features/insights
- https://whyleft.com/features/cancellation-capture
- https://whyleft.com/features/payment-recovery