Communications and Coupons

Use This Dashboard Area Safely

Use this guide when event setup, attendee operations, staff work, payment-adjacent tasks, public pages, or closeout records need a controlled path. In this guide, Communications and Coupons narrows that work to communications audience selection, preview, markdown-ext email body, send safeguards, attendee coupons, and affiliates tracking. Because this is a surfaces page, read it as part of the Event Management learning path rather than as an isolated checklist.

Event records become real-world instructions: what attendees see, what staff do, what money or inventory must reconcile, and what future organizers inherit. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What The Screen Controls

This page explains a specific surface. Treat every button, field, filter, and table as a way to view or change real records, not just as a visual layout. The intended readers are Communications staff, Event leads, and Finance staff. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/communications?id=:eventId, /rego/events/manage/attendee-coupons?id=:eventId, and /rego/events/manage/affiliates-tracking?id=:eventId.
• Records or contracts involved: Communications, Coupons, and Affiliate records.
• Main care point: Watch for changing one part of the event without checking attendees, staff, finance, communications, public information, and closeout records.
• Proof worth keeping: event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the Event Management situation, the owner, and the exact item involved in Communications and Coupons.
2. Read the current state before changing it: Use /rego/events/manage/communications?id=:eventId, /rego/events/manage/attendee-coupons?id=:eventId, and /rego/events/manage/affiliates-tracking?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the smallest action that matches the task: Keep Communications, Coupons, and Affiliate records in view so the work stays tied to the records or contracts it can affect.
4. Check the list, detail view, history, or public page afterward: Before handing off, save proof such as event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff so the next operator can see what changed and why it was safe to continue.

Before You Leave The Screen

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on attendees, staff, money, public pages, communications, and post-event records.
3. Proof is findable: The handoff points to evidence that the next operator can see what changed and why it was safe to continue.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Anchor the work to one event. Open Communications or Attendee Coupons for the correct event. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Choose the audience first, then write or edit the message or coupon details. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Change only the intended event setting or record. Preview markdown-ext content and check links, dates, prices, coupon limits, and expiry rules. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Ask another operator to review audience and copy before sending or enabling a coupon. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Send, save, or activate only when recipient scope and content are correct. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. Afterward, verify send status, coupon redemption state, and any attendee support issues. This leaves a handoff trail another operator can understand.

Purpose

Communications sends event updates to selected attendee audiences. Coupons and affiliates can affect balances, tracking, and event reporting.

Markdown-ext email body

Use markdown-ext for clear structure:

• Short headings.
• Bullet lists.
• Links.
• Tables only when necessary.

Do not use formatting to hide unclear instructions.

Common mistakes

• Sending payment instructions to already-paid attendees.
• Forgetting that overlapping audiences may deduplicate.
• Creating coupons without finance approval.
• Tracking affiliates inconsistently.

Verification

• Audience preview matches intent.
• Body preview renders correctly.
• Send safeguards are visible.
• Coupon effects are explainable.