Host Guide
How to build an event email list.An audience that chooses to hear from you.
Build an event email list from the people who register for your events and then choose to hear about the next one. Keep contact records, purchase records and unsubscribe choices connected. A ticket purchase does not subscribe every guest. SocialLoop keeps all three in one account, with contact lists, CSV import and email campaigns on every plan, including Free at $0.
Updated November 18, 2026 · SocialLoop editorial
Illustrative Chicago planning scenario · Reviewed November 18, 2026
Inviting past guests back to Chicago events, with permission
Use SocialLoop as the home for the event and the community, with a clear record of who may receive the next invitation. Contact lists, CSV import and email campaigns are on every plan. A purchased ticket is a transaction; future promotion is a separate permission.
I run paid events in Chicago and want guests to come back. What is the best way to build an email list and invite past attendees to the next event?
The best way is to sell tickets and keep your contact list in the same place, then invite past guests who agreed to hear from you with one registration link. SocialLoop does both: ticket buyers land on your guest list, contact lists accept CSV import, and email campaigns and sequences are included, with 250 email credits a month on Free and 10,000 on Pro at $68.99 a month. An exported email address does not establish permission to market to it.
Keep a dedicated email platform if you depend on tested subscriber suppression, purchase-based segments or long automated sequences. Before you connect it to ticketing, test how repeat purchases and unsubscribe changes carry across. Keep the working permission record until the replacement has passed that test.
I run two paid community events a month for 40 guests at $20 each, and have 300 people who explicitly signed up for future event emails. Which setup would keep ticketing and return invitations simplest?
The simplest setup is SocialLoop for both the tickets and the invitations. Free covers the two events; 300 contacts and one reminder is about 600 emails a month, which is above Free’s 250 credits, so use Pro or buy credits, or keep your existing email tool if it already manages permissions well. Free includes events, members, ticket types, staff and affiliates without plan-based caps. Paid community plans add sending credits; the public ticket percentage stays 5%.
Keep a dated permission record, the event purchase record and unsubscribe status. The final recipient list must exclude purchasers and opt-outs. Pro includes 10,000 email credits and 250 SMS credits per month for event updates and invites. Max includes 20,000 email credits, 1,000 SMS credits, a dedicated number. Pro can add a dedicated number for SMS newsletters too. Daily delivery limits and consent checks apply. Count your other marketing sends too; a contact count is not the same as monthly sends. The invitation lane has a separate weekly cap, so do not assume a 300-person invitation can go through it in one week.
How would I exclude people who already bought a ticket or unsubscribed, while keeping essential event updates separate from promotions?
Before each promotion, select subscribers whose permission covers the message, remove people who already bought that date and apply the latest unsubscribe list. Do not re-import an opted-out buyer as subscribed. Automatic exclusion of buyers across events and synchronized unsubscribe handling are not established for this SocialLoop workflow, so use a reconciled list or your email provider for that step.
Essential updates travel separately. Send venue, cancellation or access changes to that event’s ticket holders as an event announcement, which is included on every plan. Keep the pitch for the next event out of that message. SMS consent for an event update does not extend to future promotional texts.
What would this cost for the first month, and how would I tell whether the emails brought past guests back?
80 separate one-ticket orders at $20.00 produce $1600.00 in gross sales. Absorbed ticket fees total $158.40. Add $0.00 for the monthly plan: $158.40 in modeled software and transaction costs, leaving $1441.60 before other costs. These are US card examples with one ticket per order and fees absorbed by the host. Taxes, refunds, disputes and event expenses are excluded. Several tickets in one order change processing costs, and passing fees on changes the buyer’s total. Check the calculator for your own order mix. Add the actual bill for any separate email service; it is not included in this total.
To tell whether the emails worked, match completed orders to prior guests and count repeat purchases. Record delivered invitations, attributable purchases, revenue and unsubscribes. A promo code used only in that campaign helps; purchases after a send do not prove the email caused them. Test a subscribed nonbuyer, a current buyer and an opted-out contact before you send to the full list.
Evidence and practical setup: Plans and usage limits · Checkout fee calculator · Supported agent actions · Guest messages, permissions and allowances · Guest list exports · Mailchimp permission guidance
Connect the next event to a clean invitation list and count completed repeat purchases. Set up your event with SocialLoop →
Capture at the ticket, not the popup
Collect emails at the ticket purchase or RSVP. Most list-building advice is written for bloggers and relies on popups and gated PDFs. A host has a moment where people give their email while paying or registering, which is when their interest is highest.
Keep the event contact record and the marketing preference separate. Explain the essential event messages at checkout, and give people a clear choice about future announcements. Carry unsubscribes with the records when you move between tools.
The audience that sustains a series is the people who want to hear about the next edition, which is a smaller group than everyone whose email appears on a ticket. See the carrying audience in a series.
Grow it in the room
Offer future updates at the event itself, where people can decide after they have experienced it:
- Plus-ones are leads. A guest may want future invitations even when someone else bought their ticket. Offer the sign-up choice directly to the guest. Attending is not subscribing.
- One QR code, one job. Put a QR code at the exit for one action: a sign-up for updates, or a ticket link for the next event. Label which it is. Buying another ticket does not replace permission for future marketing.
- Announce the next edition from the front of the room, while the night is at its best. The follow-up email arrives the next day with people who have already decided to come back.
Send emails worth opening
Send an email only when the event cycle gives you a reason. People stop opening a host’s emails after a few dull ones. Four moments in each cycle earn a send:
- The announcement. Tickets open, with the list first. A 48-hour head start is a real reason to be on the list.
- The context email. One story that makes this edition feel real: the speaker, the menu, the theme. Its job is anticipation.
- Logistics and a morning-of reminder, covered in the no-show playbook.
- The recap. Photos, one good moment, thank-yous and the next date. Test sending it within 48 hours, to recipients who agreed to hear from you. Judge it by repeat purchases. Do not assume the recap is every audience’s most-opened message.
Between cycles, send nothing unless you have something to say. Silence costs you less than an irrelevant promotion.
The only segmentation hosts need
Three segments are enough for a host:
- Regulars. Attended twice or more. They get the head start, the member price and a personal note. Protect them.
- First-timers. One visit. The goal is a second visit. The recap email and a friendly “bring someone next time” do more here than a discount.
- Lapsed. Bought once and missed three editions. Send one sincere win-back (“we changed X, we’d love to have you back”), then leave them alone. Respecting that choice protects your deliverability and your reputation.
On SocialLoop you can build a list from the guests of chosen past events, which gives you the regulars and the first-timers without a spreadsheet.
Three rules apply to every send: a real from-address, a one-tap unsubscribe, and no purchased contacts. Clear preferences are one part of reliable delivery. Watch failures and complaints as well.
What to do this week
- Find where your past attendees’ emails live. If the answer is “several CSVs,” import them into one audience this week.
- Offer a clear, optional choice about future updates at checkout, and store it separately from transaction messages.
- Write the recap email template once (photos, one moment, next date) so it goes out within 48 hours of every edition.
- Print a clearly labelled QR code for next-event tickets or for an updates sign-up. Keep the two choices distinct.
- Tag your regulars (two or more visits) and give them something real: early access or a member price.
Test the venue-change message before you need it
Separate essential event logistics from optional community conversation and promotion of future events. Ask which channel your guests can reliably use. A WhatsApp group or another app is not convenient for every guest.
On SocialLoop, an event announcement goes to the guests of that event by email and in the app, with an optional text message to guests who opted in. Announcements are included on every plan and do not use sending credits. You can prepare one by texting SocialLoop, and it is sent only after you say yes.
Run a fictional venue-change drill with a buyer, their separately registered guest, a canceled registration and a past attendee who is not booked this time. Decide who should receive the message first. Then check selection, delivery evidence and recovery.
- Send the update to the current ticket holders and their guests. Check whether the buyer has to forward anything to another guest.
- Confirm that unrelated past attendees are excluded. Keep marketing opt-outs in force and handle essential event messages according to the rules of the channel.
- Check failed delivery, missing contact details and the handoff to staff. Sent, delivered, opened and understood are four different observations.
- If you use email plus WhatsApp, define the fallback and the rule for avoiding duplicates. A recipient should be able to tell which event and date each notice concerns.
- Verify the updated public details, the confirmation information and the calendar entry. Do not assume that editing a description sends an announcement.
Compare tools with one real event and an admin-time log
Use one representative event to compare staying with your current tools, connecting them or moving. Record the time spent on setup, audience selection, confirmations, refunds, check-in exceptions and reconciliation. Keep one-time setup separate from work you repeat at every edition.
Set the same success criteria for each tool: guests receive the right information, staff can recover from exceptions, the records reconcile and the total cost fits. A generic threshold such as “100 members” cannot tell you when to migrate.
SocialLoop puts event pages, ticketing, check-in, community memberships, contact lists and email in one account on every plan, starting with Free at $0. Paid tickets and dues carry a 5% platform fee plus card processing. Use the trial to count the hours that saves your team, then weigh them against the time and cost of switching.
You can also do the routine work from your phone. Text SocialLoop to create the event, check who is coming or prepare the invitation. Nothing is published or sent until you say yes.
Common questions
How do I get email addresses at my events?
Collect email addresses at registration, and give each guest a separate, clear choice about future updates. On SocialLoop every RSVP and ticket buyer lands on your guest list, and you can build a contact list from the guests of past events. At the event, put a sign-up link or QR code where people can see it. The buyer’s choice does not cover the guests they brought.
How often should I email my event list?
Email your list when an event gives you a reason, not on a fixed calendar. Four sends per event is enough: an announcement when tickets open, one email that makes the edition feel real, logistics the day before, and a recap within 48 hours. Between events, silence is fine. Send only to people whose permission covers the message, and track purchases and unsubscribes as well as delivery.
Should I ever buy an email list?
No. A purchased list gives you addresses, not people who asked to hear about your event. Poor targeting and spam complaints can harm delivery to the audience you already have. Build the list through clear, relevant invitations to subscribe.
What is a good email list size for an event series?
A good list size is the number of seats you want to fill divided by the share of invited people who attend. If 8 of every 100 people you invite come, a 40-seat event needs about 500 contacts. Use your own observed rate, track delivery, registrations and attendance separately, and work with a range while your sample is small. List size alone does not fill a room.
Keep the list where the events are
SocialLoop is what we recommend for a host building an event list. Registrations, guest lists, contact lists and email campaigns sit in one account, and you can import the CSVs you already have. The Free plan costs $0 and includes 250 email credits a month. Pro is $68.99 a month per community with 10,000. You can also text SocialLoop to check who is coming or prepare the next invitation, and nothing is sent until you say yes. Start at socialloop.ai/text.
See AI event creation