Sequence playbook

Deadline expired save offer

When a timer or promotion expires, route the buyer into a coupon, save-offer, or follow-up path without changing the live checkout manually.

Triggers

deadline.expired
promo.expired

Actions

apply_save_offer Apply Save Offer
send_deadline_followup Send Deadline Followup
suppress_expired_redirect Suppress Expired Redirect

Implementation

How this sequence should be wired.

A named sequence is useful only when the trigger, commercial context, and downstream handoff are all explicit across checkout, integrations, webhooks, and fulfillment.

Trigger

Choose the event that starts the work.

deadline.expired, promo.expired should fire from a real Plandalf checkout, payment, invoice, subscription, deadline, or affiliate event, not from a front-end success page alone.

Automations Sequences Webhooks

Context

Carry the commercial state with the event.

The sequence should know the offer, product, price, buyer, payment state, coupon, invoice, and integration context before it touches another tool.

Offers Products Prices Invoices

Handoff

Route each action to the right product or platform.

apply_save_offer, send_deadline_followup, suppress_expired_redirect should land in the connected tools that actually fulfill, notify, reconcile, or update the customer record.

Integrations Purchase automations ActiveCampaign Klaviyo Zapier

Product surfaces

Where the operator checks the work.

These are real Plandalf app surfaces tied to the products, features, integrations, invoices, payment settings, API docs, and sequences this playbook depends on.

The Numi coupon discount settings panel. — Coupons can become part of the sequence when a deadline, save offer, or recovery path changes the buyer state.

The Numi coupon expiration settings panel. — Coupon expiry makes deadline follow-up enforceable after the timer or promo expires.

The Numi sequences screen showing automated workflow configuration. — Sequences turn checkout, payment, invoice, subscription, and deadline events into follow-up work.

The Numi offer editor automation tab showing sequence controls beside the checkout canvas. — Purchase automations start from the offer, product, buyer, payment, and invoice context Plandalf already knows.

The Numi automation integrations screen showing connected tools. — Integrations decide where the event lands after Plandalf records the checkout state.

The Numi offer invoices screen showing invoice records. — Invoices preserve the commercial record after checkout so support and reporting are not guessing.

Reference links

Everything this playbook touches.

Use these links when a builder needs to move from the sequence concept into the exact product, feature, integration, platform, workflow, stack, or documentation page.

Product

Offers

The checkout surface where your customers actually decide.

Product

Timers

Deadlines that actually change the price.

Product

Automations

The work that happens after a customer buys.

Feature

Deadline campaigns

Urgency