Skip to main content
Airdun does not run the same fixed sequence for everyone. On Renewals and Free trials, it decides what to do next on each case as it unfolds (which message, on which channel, and when), and adapts as the customer reacts and as Stripe retries the payment. New customers follows a fixed sequence instead: one email, then one text if the invoice is still unpaid, within the day the payment failed. See Autopilot.

​
What the messages say

What Airdun sends depends on the use case’s Messages page:
  • Sequence: your own templates, sent as written; only the AI variables you add are filled in for the case.
  • AI writer: Airdun writes each email for the case, as one of your voices, grounded in your business context.
Either way, every message is in the customer’s language and carries the Stripe link to update the card and pay.

​
Respectful by design

  • Messages go out during daytime hours in the customer’s time zone, and only on workdays if you set it.
  • Airdun limits how often a customer is contacted, and never sends the same customer a flood of messages.
  • Messages are timed around Stripe’s own retries, so the customer has a chance to act before the next attempt.

​
When Airdun stops

  • The payment succeeds: the case is recovered and every scheduled message is canceled.
  • The invoice is written off in Stripe: voided, marked uncollectible, or the subscription is canceled.
  • The case is escalated: it matched one of your escalation rules, and your team takes over.
  • You pause or turn off the use case and choose to stop the cases in progress.
You do not build the strategy step by step. Your levers are the use case’s messages, its channels, its sending rules and consequences, and its escalation rules. See Use Case Settings.