# Buyer versus ticket-holder recipient test card (English)

Use controlled test records in the platform that issues your event tickets. Record counts and decisions, not names, email addresses, ticket codes or private requests.

| Message decision | Record |
| --- | --- |
| Event edition and message purpose | ____ |
| Person who must act | [ ] Order buyer  [ ] Current ticket holder  [ ] Both, with distinct versions |
| Sender's selected audience and filter | ____ |
| Staff owner and approved support fallback | ____ |

| Test order | Buyer included? | Holder included? | Unexpected duplicate or exclusion? | Route if holder cannot be reached |
| --- | --- | --- | --- | --- |
| Buyer is also holder | ____ | ____ | ____ | ____ |
| One buyer, several holders | ____ | ____ | ____ | ____ |
| Transfer accepted / claimed | ____ | ____ | ____ | ____ |
| Holder email absent | ____ | ____ | ____ | ____ |
| Cancelled or changed order | ____ | ____ | ____ | ____ |

Before the live send, compare the actual eligible-recipient preview or sample to these expected records. Check the message's date, links and language with a test message where available. After sending, record the platform's delivery status, replies and any support cases. A test sent to yourself may validate the copy without validating the audience rule.