Real-World Example
Jane misses a step after receiving a campaign message. The portal creates a scheduled follow-up. The scheduled communication command runs every 15 minutes to check whether a follow-up is still valid and allowed. It dispatches due messages or stops follow-ups whose conditions are resolved.Visual Flow
Automated Lifecycle Messages
Automated templates can notify consumers about new offers, counteroffers, pending responses, scheduled settlements, payment plans, failed payments, gift payments, and new EcoMailbox messages. Payment-plan and scheduled-settlement reminders may be sent 3 days and 1 day before the current due date. If the payment date changes, future reminders must use the updated schedule. Every automated message must follow the consumer’s Communication Profile, channel permissions, and opt-out state.SMS STOP and START
Reply STOP to block consumer SMS to that number. The block applies to the number even if more than one consumer uses it or a creditor imports another account later. Scheduled email and personal communication preferences remain in effect. Reply START to lift the number’s STOP block. A personal opt-out or a paused text preference still applies. An eligible email can still be sent while SMS is blocked.Card Expiry Reminders
Communication 6.8 covers active installment plans and scheduled settlements when an outstanding payment using the card falls after the last day of its expiry month. It starts 60 calendar days before that date and repeats every 7 days, using the creditor company calendar. Temporarily held plans are excluded. A daily discovery task identifies eligible accounts. Multiple affected payments are grouped into one reminder per account and weekly cycle for each permitted channel. An account already inside the reminder window receives its first reminder when discovered; missed weekly reminders are not sent in a burst. The reminder stops when the attached card expiry is updated beyond the reminder window, all affected payments move to a suitable replacement method, or no eligible obligations remain. Adding another card without assigning it to those payments does not stop the reminder. Partial reassignment leaves the remaining affected payments eligible. Unresolved reminders may continue after expiry. The system rechecks payment assignments before delivery, including immediately before queued email transport. Each weekly cycle is protected against duplicate dispatches. If an email transport attempt has an uncertain outcome, the same cycle is not automatically resubmitted; the failure is recorded for investigation. The reminder links to the authenticated Bill Pay Wallet, where the consumer can update the card or change the payment method for selected scheduled payments.How It Should Work
- It should send scheduled follow-ups only while the triggering condition still applies.
- It should use the latest payment or settlement schedule when calculating reminders.
- It should stop follow-ups for deactivated, expired, resolved, or opted-out consumers.
- It should increment send counts and calculate the next send time consistently.
How It Should Not Work
- It should not keep messaging consumers after the account condition is resolved.
- It should not ignore unsubscribe or communication permissions.
- It should not repeatedly send follow-ups beyond the configured expiration rules.

