Keep the source record beside the draft
This original fictional event is Paper Prototype Clinic, October 23, 2026, 2:00-3:00 p.m. America/New_York, Room B at the illustrative address 14 Example Lane. The address is demonstration data, not a verified real venue. Organizer contact remains [TO CONFIRM].
As of October 13, the fictional records are DEMO-R01 Alex confirmed, DEMO-R02 Jordan waitlisted, and DEMO-R03 Taylor received/pending approval. No actual attendee, email address, payment, or access code is represented. None of these demonstration drafts has been sent or is ready for a real send without confirmed event and contact details.
The Swoogo registration-email descriptions distinguish registration outcomes and practical confirmation details. The three complete messages below are independently written for this supplied record set.
Confirm only the record that has a confirmed seat
Illustrative draft — not sent. Source: DEMO-R01.
Subject: Your Paper Prototype Clinic registration is confirmed — October 23
Hi Alex,
Your registration for Paper Prototype Clinic is confirmed in the supplied record as of October 13.
Date: October 23, 2026
Time: 2:00-3:00 p.m. America/New_York
Location: Room B, 14 Example Lane — illustrative venue for this draft
Registration reference: DEMO-R01
Please check these details before attending. If you need help with your registration, contact [ORGANIZER CONTACT TO CONFIRM].
Paper Prototype Clinic organizing team
Do not add payment received, a calendar link, transfer instructions, or a QR code unless the actual authorized record supplies those facts and destinations.
Tell the waitlisted attendee that a seat is not confirmed
Illustrative draft — not sent. Source: DEMO-R02.
Subject: Your Paper Prototype Clinic request is on the waitlist
Hi Jordan,
Your request for Paper Prototype Clinic is on the waitlist as of October 13. You do not have a confirmed seat for this event.
The clinic is planned for October 23, 2026, 2:00-3:00 p.m. America/New_York. No date for a change in your waitlist status has been confirmed. Please wait for a separate confirmed-seat message before treating this request as an accepted registration.
Request reference: DEMO-R02
For questions about your request, contact [ORGANIZER CONTACT TO CONFIRM].
Paper Prototype Clinic organizing team
This version states status without inventing a promotion date or promising that a place will become available. Add the organization's actual waitlist process only when supplied.
Acknowledge a pending request without confirming registration
Illustrative draft — not sent. Source: DEMO-R03.
Subject: We received your Paper Prototype Clinic registration request
Hi Taylor,
We received your registration request for Paper Prototype Clinic. It is pending approval as of October 13; your registration is not yet confirmed.
The clinic is planned for October 23, 2026, 2:00-3:00 p.m. America/New_York. The record does not yet provide an approval decision or decision date. Please use the request reference below if you contact the organizer.
Request reference: DEMO-R03
Organizer contact: [TO CONFIRM]
Paper Prototype Clinic organizing team
Received, pending, waitlisted, and confirmed are different source states. The pending message must not inherit confirmed wording because all three requests concern the same event.
Check real-send readiness before using the copy
Confirm the current status, event date/time zone, venue, organizer contact, and any required instructions in the actual event system. A status changing after the draft date requires the corresponding message to change. Keep missing facts in a preparation list; do not send placeholder contact details as if they were usable.
Copy a status-message prompt
Create one complete, self-contained US-English HTML companion for “Paper Prototype Clinic · Registration Drafts”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for Alex · confirmed DEMO-R01; Jordan · waitlisted DEMO-R02; Taylor · received / pending DEMO-R03; Reset fictional drafts; Select draft text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Draft original post-registration email messages in US English. Selected record IDs,names,statuses and status-as-of date: [inputs]
Confirmed event name,date,time,time zone and venue: [inputs]
Organizer contact and actual status-process instructions: [inputs or unknown]
Required email/event-system format: [format]
Write complete subject/body for each supplied confirmed,waitlisted or received-pending record. Confirm a seat only from a confirmed record. Waitlist states no confirmed seat and no promotion date unless supplied; pending acknowledges receipt without approval. Preserve the selected reference and current status. Include only supported arrival/contact details and keep real-send readiness separate from draft completion. Do not invent seats,decision dates,emails,access/QR codes,payment proof,calendar/transfer links,deliveries or performance claims. Label fictional examples and mark gaps [NEEDED: input]. Optional HTML review compares source/status/draft only, with no send/register controls or email-client compatibility claim. Return copy for the organization's actual email/event workflow.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Event Registration Email Template: Match the Message to the Actual Status
A “You're confirmed” subject line is wrong when the registration record only says the request was received. Start with the record status, then write the subject and body around what the attendee can rely on. A waitlist position and a pending request each need a different message from a confirmed seat.
## Keep the source record beside the draft
This original fictional event is **Paper Prototype Clinic**, October 23, 2026, 2:00-3:00 p.m. America/New_York, Room B at the illustrative address 14 Example Lane. The address is demonstration data, not a verified real venue. Organizer contact remains [TO CONFIRM].
As of October 13, the fictional records are DEMO-R01 Alex confirmed, DEMO-R02 Jordan waitlisted, and DEMO-R03 Taylor received/pending approval. No actual attendee, email address, payment, or access code is represented. None of these demonstration drafts has been sent or is ready for a real send without confirmed event and contact details.
The [Swoogo registration-email descriptions](https://swoogo.events/blog/event-registration-email-templates/) distinguish registration outcomes and practical confirmation details. The three complete messages below are independently written for this supplied record set.
## Confirm only the record that has a confirmed seat
**Illustrative draft — not sent. Source: DEMO-R01.**
**Subject:** Your Paper Prototype Clinic registration is confirmed — October 23
Hi Alex,
Your registration for Paper Prototype Clinic is confirmed in the supplied record as of October 13.
Date: October 23, 2026
Time: 2:00-3:00 p.m. America/New_York
Location: Room B, 14 Example Lane — illustrative venue for this draft
Registration reference: DEMO-R01
Please check these details before attending. If you need help with your registration, contact [ORGANIZER CONTACT TO CONFIRM].
Paper Prototype Clinic organizing team
Do not add payment received, a calendar link, transfer instructions, or a QR code unless the actual authorized record supplies those facts and destinations.
## Tell the waitlisted attendee that a seat is not confirmed
**Illustrative draft — not sent. Source: DEMO-R02.**
**Subject:** Your Paper Prototype Clinic request is on the waitlist
Hi Jordan,
Your request for Paper Prototype Clinic is on the waitlist as of October 13. You do not have a confirmed seat for this event.
The clinic is planned for October 23, 2026, 2:00-3:00 p.m. America/New_York. No date for a change in your waitlist status has been confirmed. Please wait for a separate confirmed-seat message before treating this request as an accepted registration.
Request reference: DEMO-R02
For questions about your request, contact [ORGANIZER CONTACT TO CONFIRM].
Paper Prototype Clinic organizing team
This version states status without inventing a promotion date or promising that a place will become available. Add the organization's actual waitlist process only when supplied.
## Acknowledge a pending request without confirming registration
**Illustrative draft — not sent. Source: DEMO-R03.**
**Subject:** We received your Paper Prototype Clinic registration request
Hi Taylor,
We received your registration request for Paper Prototype Clinic. It is pending approval as of October 13; your registration is not yet confirmed.
The clinic is planned for October 23, 2026, 2:00-3:00 p.m. America/New_York. The record does not yet provide an approval decision or decision date. Please use the request reference below if you contact the organizer.
Request reference: DEMO-R03
Organizer contact: [TO CONFIRM]
Paper Prototype Clinic organizing team
Received, pending, waitlisted, and confirmed are different source states. The pending message must not inherit confirmed wording because all three requests concern the same event.
## Check real-send readiness before using the copy
Confirm the current status, event date/time zone, venue, organizer contact, and any required instructions in the actual event system. A status changing after the draft date requires the corresponding message to change. Keep missing facts in a preparation list; do not send placeholder contact details as if they were usable.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Recheck the selected registration record immediately before the real message is prepared in the event/email system. Resolve the contact and venue details, then use the subject and body that match the current status rather than the most reassuring wording.
Optional: compare the fictional drafts
Use the HTML companion to inspect status-to-wording correspondence; retain actual registration records and sending in the authorized event/email system.