# Welcome flow QA checklist

Record evidence for every item. Do not mark a test complete from memory.

## Permission and audience

- [ ] Signup promise and consent source are documented.
- [ ] Entry eligibility matches the signup context.
- [ ] Unsubscribed, bounced, complained, and ineligible contacts are suppressed.
- [ ] Re-entry behavior is intentional and tested.

## Content and claims

- [ ] Message 1 delivers the promised resource.
- [ ] Each message has one primary job and action.
- [ ] Product name, contents, format, price, support, and refund wording are current.
- [ ] Every material claim has a verification route.
- [ ] Fictional examples are labeled.
- [ ] No placeholders, internal comments, or draft notes remain.

## Automation

- [ ] Delays and local-time behavior match the specification.
- [ ] Missing personalization fields have natural fallbacks.
- [ ] Purchase, unsubscribe, bounce, and complaint exits work.
- [ ] Customer and non-customer branches work.
- [ ] Tracking-disabled subscribers still receive a coherent path.

## Links and rendering

- [ ] Every link resolves to the intended destination.
- [ ] Tracking parameters are valid and documented.
- [ ] Desktop and narrow-screen rendering are readable.
- [ ] Images-blocked rendering preserves meaning.
- [ ] Dark-mode behavior is acceptable where supported.
- [ ] Plain-text fallback is complete.
- [ ] Focus order and link text are understandable.

## Operations

- [ ] Sender identity, business address, and reply route are accurate.
- [ ] Preference and unsubscribe controls work.
- [ ] Metrics, owners, limitations, and review dates are recorded.
- [ ] Pause or rollback procedure is documented.
- [ ] A human completed the full journey as a test subscriber.

## Sign-off

- Tested by:
- Test date:
- Environment:
- Issues found:
- Fix verification:
- Final approver:
- Activation decision: