Plandalf
Browse Product guides

Save offers

A save offer is the offer shown when a subscriber is about to cancel. The goal is not to block cancellation. The goal is to show one relevant alternative before the customer leaves: a discount, a different plan, a pause, or a time-bound return path.

Warning. Do not make cancellation hostile Keep the cancel path clear. A save offer should be one useful detour, not a maze.

The path

  1. Choose the cancellation moment

    Place the save offer at the point where the customer has already shown cancel intent, such as a cancel button or account-management flow.

  2. Segment the offer

    Use context such as plan, tenure, product, coupon eligibility, or customer state so every subscriber does not see the same rescue offer.

  3. Offer one next step

    Present a discount, pause, plan switch, or deadline-bound coupon. Avoid stacking multiple unrelated choices on the same screen.

  4. Route the outcome

    If they accept, continue the subscription path. If they decline, let the cancellation complete and send the right backend event or automation.

Save patterns

These are workflow patterns, not automatic actions performed by present(). Configure and verify the actual provider-side discount, plan change, pause, or cancellation. Closing or declining a checkout does not by itself cancel a subscription. Keep the existing authenticated cancellation handler until the replacement workflow is proven.

Discount

Offer a coupon when price is the clear objection. Use expiry, usage limits, and frequency caps when the discount should not be permanent.

Plan switch

Move the subscriber to a cheaper or better-fitting plan when the current package is too much.

Pause

Hold access or billing for a defined period when the problem is timing rather than value.

Deadline-bound return

Pair the offer with a timer or expiring coupon when the customer should decide before the rescue path closes.

What to configure

Save offer inputs

  • Trigger (cancel intent): The action that opens the save path, such as a cancel subscription button.

  • Audience (segment): Who should see the offer. Common segments include plan, tenure, coupon history, product, or account state.

  • Offer (discount | plan switch | pause | promo): The single alternative shown before cancellation continues.

  • Decline behavior (cancel_subscription): What happens when the subscriber rejects the save offer. Keep this path direct and predictable.

Decision rules

  • Price objection — Try a discount, lower tier, or different billing cadence.

  • Not using it now — Try a pause or time-boxed return path.

  • Missing outcome — Offer a related product, setup path, or success resource.

  • Still leaving — Let the cancellation complete and route the event to follow-up systems.

Tip. Tie discounts to real coupon controls If the save offer uses a coupon, pair it with the same controls you use elsewhere: product eligibility, expiry, usage limit, frequency, and minimum order rules.

  • Coupons — Use promo and coupon rules when the save path includes a discount.

  • Pricing models — Model plan switches, subscriptions, trials, and package changes.

  • Webhooks — Send accepted or declined save-offer context into your backend workflow.

Feature detail