What this is. The guest list for the CineMe launch event, live. The first mailout is Wave 1 only: people who already have an address. Wave 1 priority names without an address sit in Wave 1 no email and stay off that send until an address is added. Wave 2 is the next group; move someone onto Wave 1 when they should join the mailout. Wave and Relationship stay editable on every row: change anyone from Wave 1 to Wave 2 (or the other way), and change who holds the relationship, at any time. Add a name, take one off, set who holds the relationship, and move anyone between Wave 1, Wave 1 no email, Wave 2 and Wave 3. Relationship on this list is who holds the person (Dan, Chris, Julia Stuart, Julia Jones, Michael). That value is stored on the CRM person as account holder. It is not the CRM Relationship field, which is warmth (Warm, Cold, Stale). The Email column shows the address on file. Empty means we do not hold one yet; type one in to add it. That write updates the CRM person already linked to this guest, not a second contact. Sent is whether we transmitted an invitation. Delivered is whether the provider confirmed it arrived. RSVP opened is whether they loaded the public RSVP page. It is not an email-open pixel. The RSVP column is their answer from that page: Yes, No, Platform only, or No reply. Download CSV opens in Excel or Google Sheets, with Relationship, Email, Sent, Delivered, RSVP opened and RSVP columns so you can filter by owner, address and reply. Use the notes on each row to agree who makes the approach.

Nothing here sends anything. Storing an address does not send mail. There is no send button and no send endpoint. Follow-up copy is prepared on Follow-up drafts. Invitations and follow-ups go out only after a test to an address Dan controls, and only then on a written instruction from him that explicitly permits it. Open tracking stays off. RSVP answers already land here when a guest clicks the public page.