# How do I get speakers and attendees posting about an event? Invite speakers, attendees and partners by email, let each of them write in their own words, and publish the posts on one schedule around the event. Source: https://launchgenius.app/use-cases/event-show Last updated: 2026-08-27 You are the person running the event, the show, the festival, the meetup. The job is one sentence: get the speakers, the people in the room, and the partners who put their name on it posting about it when it is actually happening, not the week after in a recap nobody asked for. LaunchGenius does not have an events product. An event with a start time is a launch. The people change; the coordination does not. ## Who you invite Three groups, on purpose, because they post for different reasons and at different times: - **Speakers.** They have a slot, a slide, a reason to tell their own audience to come, or to say they are on stage. Treat them as collaborators or guests. Collaborators usually post 10 minutes to 1 hour after T-0; guests 15 minutes to 2 hours after T-0. - **Attendees.** The people who bought a ticket or accepted the invite. They are customers or advocates, and their usual wave is 30 minutes to 3 hours after T-0. - **Partners.** The venue, the sponsor, the other show on the bill. They are partners, 2–6 hours after T-0. A speaker you already know well can be invited by email on their own, with no cohort set up first. A room of attendees is a link you put in the confirmation mail, or a list you pull from contacts. ## How the run of show works Write the event's own announcement first. That is the launch post: doors, the lineup, the link to tickets or the stream. Everything else attaches to it. A speaker's quote sits on top of it; an attendee's reply lands under it. Doors, or the moment the stream goes live, is the launch moment, which the product calls T-0. Speakers post around it. Attendees post once they are in the room or on the stream. Partners post when they are ready, which is later, and that is fine: twenty posts in one minute reads as a campaign, and an event is supposed to look like people showing up. Set the destination as the ticket page, the stream, or the event site. Every post carries a tracked link of its own. ## What they receive The invite is an email, or a link. An email address is the whole requirement. No password, no paid account, nothing to connect unless they want to. What you attach is what they will actually use: - **A still, a clip, a poster**, up to four, from the media library. They arrive with the invite and sit beside the composer. Download is there for anyone posting from a phone in a hallway. - **A line they can quote**: the billing, a time, a sentence from their own talk. Never pre-filled. - **A note** that says what you are asking and when. It stays on their page, so a speaker who opens the link on the day still sees it. For a keynote you already trust, skip review. For a room of attendees, keep it on. ## What they do, and what you do They write in their own words, pick a time, and submit. You approve, ask for changes, or suggest an edit they accept or decline. You cannot rewrite their post. That is the reason a speaker's post sounds like the speaker. Connected accounts publish at the time they picked. Anyone who does not connect gets a message at that time with the text, the file, and a link that opens the platform's own composer. They post it and press "I posted it". The reminder exists because a person backstage will not remember. ## What already works Invite by email. They write. You approve. One schedule, across 11 networks: X, LinkedIn, Instagram, TikTok, YouTube, Threads, Facebook, Slack, Discord, Telegram and Bluesky. Automatic where the network allows it; handed back at the scheduled time where it does not. Rehearsal is the default. Run the day against nobody before you run it against a room. The report shows who posted, when, and how many people followed their link. That is the list you take into the next date. The click-by-click of building any launch is in the [organizer how-to](/help/organizer-guide). A book, a product, or an episode uses the same mechanism; each has its own [use-case page](/use-cases).