# Event registration abandonment reminder: trigger and stop test matrix (English)

Copy for one event edition and one provider setup. This sheet is a planning and test record, not a sending tool. Keep real contact details and payment information in the authorized system; use fictional or controlled case references here.

Event / edition: ____   Provider / feature: ____   Flow version: ____
Source of truth for registration status: ____   Ticket availability owner: ____
Approved contact route / reviewer: ____   Test method confirmed with provider: ____

## State gate

| Gate | Exact record or provider event used | Expected result | Verified by / when |
|---|---|---|---|
| Start: identifiable unfinished attempt | ____ | Enter candidate queue, not “ticket issued” | ____ |
| Contact eligibility | ____ | Only approved reachable records continue | ____ |
| Completion / valid order | ____ | Stop queued reminder | ____ |
| Payment pending or failed | ____ | Route to status-specific handling; no false completion claim | ____ |
| Ticket/date availability | ____ | Stop or revise if original choice no longer offered | ____ |
| Registration close | ____ | Stop reminder if no registration path remains | ____ |
| Return to form / new activity | ____ | Provider-confirmed reset or no reset | ____ |
| Re-entry / repeat attempts | ____ | Provider-confirmed limit | ____ |

## Controlled transition cases

| Case | Setup and action | Expected send or suppression | Actual provider event / message ID | PASS / FAIL / UNVERIFIED | Exception owner |
|---|---|---|---|---|---|
| A | Identified eligible attempt left unfinished | ____ | ____ | ____ | ____ |
| B | Same attempt completes before delay | Suppress | ____ | ____ | ____ |
| C | Person returns to form without completing | ____ | ____ | ____ | ____ |
| D | Relevant ticket sells out during delay | Suppress original-choice reminder | ____ | ____ | ____ |
| E | Event registration closes during delay | Suppress | ____ | ____ | ____ |
| F | Payment pending; no confirmed ticket | Status-specific handling | ____ | ____ | ____ |
| G | Contact or permission route cannot be verified | Do not send | ____ | ____ | ____ |
| H | Event date or registration link changes | Retest current facts and destination | ____ | ____ | ____ |

Do not infer a working stop rule from a preview mode that never triggers the message. Ask the provider or operator how the actual flow can be tested safely.

## Release record

Current event date/time zone and approved registration URL: ____
Message truth check: no completed registration or ticket is promised for an unconfirmed attempt: ____
Unresolved cases: ____   Decision: GO / HOLD
Decision owner and time zone: ____   Observation owner after activation: ____
Change that requires a retest: ____