
People decide whether to come before they read much of anything. They look for the date, the time, the place and whether it costs money. If any of those is missing or buried, they close the page and go back to what they were doing.
So put those four facts in the first line of every invitation, in that order: what it is, when, where, and whether it is free. Example: "Free talk on home bookkeeping, Thursday November 20 at 6:30 pm, Riverside Library room B." A reader can decide from that line alone.
A vague ask gets vague answers. "Let us know if you can make it" leaves the reader to decide how much effort a reply is. Replace it with one specific action and say what happens next.
A deadline helps only when it is real. If you will not turn anyone away on Wednesday, do not say Tuesday. People can tell a made-up deadline, and it teaches them to ignore the next one.
One invitation gets read by the people who were already watching for it. Three, spaced out, reach the people who forgot. Here is a timeline for an event three weeks away:
Do not send the same message four times. Each one should give a new reason to reply: the speaker's name, a photo of the room, the menu, or the number of people already going.
A friend who says yes is worth more than another mailing. Give each guest a specific job: bring one person, or forward the link to one group chat. A personal ask works better than a general share request. "Would you bring your coworker Dana?" gets more replies than "Please share this."
If you run your event on Connections, you can turn this into a built-in reward. In the host tools, the setting "Guests who invite friends get in free" asks for a goal in "Friends to invite". Check the goal fits your event before you turn it on, because it changes who gets in free.
The easiest people to reach are often the ones already nearby. Look at where your next guests are right now: a sign-up table at a related event, a shop counter, a class you teach, a neighborhood group, a parent pickup line. Put a card with the event name, the date and a short link or QR code in each place. Tell the person behind the counter what to say in one sentence, so every card gets the same pitch.
On Connections, the event's walk-in card does this at the door of a future event. It reads "Scan to sign in or create an account and RSVP on your phone." The same card works on a table at a community fair.
Track RSVPs by the day, not just the total. Here is a worked example. Say you invite 120 people across three messages and get these replies: 18 in the first week, 6 after the reminder, and 2 after the two-day note. The reminder brought in 6, so it is worth keeping. The two-day note brought in only 2 for a lot of effort, so next time you can make it shorter or send it to a smaller list.
Change one thing at a time. If you change the subject line, the date line and the RSVP button all at once, you will not know which one worked. Keep the message that got the most replies and test one new line in the next event.
A reply of "maybe" is not a yes. Ask maybes one question: "Is there anything that would make it a yes?" The answer tells you whether to fix the time, the place or the cost.