What makes a great event invitation

If you've spent any time hosting things, you know the gap between the invite list and the people who actually walk through the door. It's almost always larger than you expect. The single biggest factor isn't who you invited or when you sent it. It's how clear and inviting the actual invitation was.

This is the most asked question we get from PopIn hosts: how do I write an event invitation that converts? Here's what we've noticed looking at the events created on PopIn in our early weeks and seeing which ones consistently get strong RSVPs.

1. Lead with the social proof, not the logistics

The first sentence of your invitation is doing one job: making the person reading it think "I want to be there." It's not telling them the address. It's not listing the schedule. It's giving them a sense of who's going to be in the room and what the energy will be.

"It's been ages since the whole crew was in the same room" beats "Saturday night drinks at 7pm." "Helena's leaving for Berlin, this is the last chance to send her off properly" beats "Helena's farewell party." Tell people what they're showing up for emotionally before you tell them when and where.

2. One sentence, not a paragraph, of explanation

The most common mistake first-time hosts make is writing too much in the event description. They worry that they need to "sell" the event, so they pile on context: how the event came about, what they're hoping to achieve, a long list of what to expect. This usually has the opposite effect. People skim. The more text, the more skimming, the less actually retained.

One short sentence about what it is. One short sentence about why now. One short sentence about who it's for if that's not obvious. That's plenty. Save the detail for the address line and the bring-list. People will ask if they need to know more.

3. Pick a cover photo that hints at the vibe

The PopIn cover photo is the first thing people see when they open your event page. If it's blank, they default to whatever the gradient placeholder is, which is fine but generic. If you pick something specific, even something low-effort like a phone-camera shot of the venue or a screenshot from a music video that matches the energy, it dramatically changes the read of the event.

This is the same rule as Instagram: the visual sets expectations. A cover photo of a dimly-lit bar tells people "this is a chill drinks night." A cover photo of a beach tells people "wear something you can sit in." A cover photo of just the venue's logo says "this is a professional event, dress appropriately." Pick deliberately.

4. State the bring-list as relief, not demands

If your event needs people to bring something (a dish, a bottle, cash for the venue, an item for white-elephant), the way you phrase the ask matters more than you'd think. "Please bring a $20 contribution for the food" reads as a chore. "We're chipping in $20 each for the catering, Venmo @username easiest if you can do it ahead of time" reads as helpful clarity.

The difference is whether the language signals "I expect this from you" or "here's the info you'll need so you're not caught out." The actual ask is identical. The framing changes how people feel reading it.

5. Make the RSVP feel low-stakes

The verb people most associate with RSVPing is commit, which is high-stakes. Especially for casual events, this is bad. You want people to feel like saying "Going" is the lightweight default, and changing to "Maybe" or "Can't make it" later is fine.

The way you signal this in the invitation is by being explicit about it. "Tap whatever feels right, you can change it any time" in the event description telegraphs that you're not going to be hurt if they say Maybe and end up not coming. People are much more likely to commit when they feel they have an out.

6. Don't end with "let me know if you're coming!"

This sounds friendly. It's not. It's actually adding work for the recipient: they now need to remember to message you back outside of the actual RSVP flow. Either they do (annoying), they forget (you don't get a real headcount), or they feel guilty about not replying (also bad).

If you're using PopIn, the RSVP is in the invitation itself. They tap a button, you get notified. You don't need them to do anything extra. End the invitation with anticipation, not assignment. "Looking forward to seeing you" works. "Let me know if you're coming" creates an unnecessary task.

7. Send the invitation when people are likely to actually read it

This is unglamorous and very effective. Invitations sent at 11pm on a Wednesday get read by the same number of people as invitations sent at 9am on a Sunday, but the RSVP rates diverge by 30-40% in our data. People who read an invitation when they're tired, distracted, or about to put their phone down for the night are less likely to actually act on it.

The sweet spots are weekday mornings (8-10am, before people fully start their day), weekday lunchtimes (12-1pm), and Sunday late morning (around 11am). Avoid late nights, peak work hours, and the dead zone of Saturday afternoon. The actual lift from timing this right is bigger than almost any other thing on this list.

Putting it together

Here's an example combining all of the above:

Subject line: Saturday drinks at The Eight Bells

Cover photo: dimly-lit pub interior

Description: It's been months since the whole crew was in one room. Properly catching up at The Eight Bells from 7pm, staying till they kick us out. Tom's making a playlist. Tap whatever feels right on the RSVP, you can change it any time. Looking forward to seeing you.

Time to write: under a minute. Information: clear. Tone: warm. Stakes: low. Decision for the recipient: easy. That's the whole job.