# Event campaign reply-route test card (English)

Use one card per campaign version. Record team-controlled test information only; keep attendee messages and personal details in the approved support system.

| Campaign / event edition | Planned send window + time zone | Recipient group | Message owner |
|---|---|---|---|
|  |  |  |  |

## Route decision

| Check | Record |
|---|---|
| Email service and campaign/version ID |  |
| Chosen model: team mailbox / platform inbox / named organizer |  |
| Visible From name and address |  |
| Reply-To or platform-managed reply route as delivered |  |
| Public support address, if different |  |
| Primary reader and coverage window |  |
| Backup reader and access verified |  |
| Escalation owner for registration or ticket-record questions |  |
| Escalation owner for program or venue facts |  |

## Test the delivered path

Use an authorized team-controlled recipient. If your provider's test mode routes replies differently from a live campaign, mark that limitation and follow the provider's documented verification path.

| Test | Expected | Observed / evidence location | Owner / result |
|---|---|---|---|
| Delivered message shows intended From and Reply-To |  |  |  |
| Reply lands in the chosen mailbox or platform inbox |  |  |  |
| Primary reader can find and assign the thread |  |  |  |
| Backup reader can find the same thread |  |  |  |
| Team reply displays the intended public sender |  |  |  |
| Human question remains visible among automatic replies |  |  |  |
| Unresolved thread can be handed to ongoing event support |  |  |  |

## Decision and handoff

- **Decision:** GO / HOLD / CONDITIONAL (name the unresolved check):
- **Setting or address to change:**
- **Retest evidence and reviewer:**
- **First-send monitoring owner and window:**
- **Open threads handed to:**
- **Continuing public contact route:**

A successful test proves only the path observed for that message and configuration. Recheck after a route, campaign, audience, or owner change.