How big the gap is
Free events lose more people than paid ones. PheedLoop, an event-software company, looked at check-in data from over 1,070 live events and found a median no-show rate of about 20%: about 28% for free events and 17% for paid ones. Small events of 10 to 49 people did worst, at about 32%. That is the vendor's own platform data, not a peer-reviewed study, and it counts cancellations as no-shows, but it is the best measured figure there is.
If you run a free monthly meetup for 30 people, that is roughly a third of the room. If you order pizza for the RSVP list, you already know this.
What the reminder research says
The strongest evidence on reminders comes from healthcare, where missed appointments are counted carefully.
- A reminder works. A Cochrane review of randomised trials found that text reminders raised attendance at healthcare appointments from 67.8% with no reminder to 78.6% with one, across 7 trials and 5,841 people.
- What it says matters. In two NHS trials with about 10,000 outpatients each, a reminder that named the specific cost of missing ("Not attending costs NHS £160 approx.") cut missed appointments from 11.1% to 8.4%, at no extra cost.
A meetup is not a hospital appointment, and nobody should guilt-trip a book club. The lesson that carries over is simpler: reach people on the day, and say something specific.
The playbook
1. Keep your invite
Luma and Partiful handle the event page, the RSVPs and their own reminders. Keep them. LFG Alarm adds the part they are not built for, a real alarm at the moment people need to move. See how LFG Alarm adds to Luma and to Partiful.
2. Make the alarm from the link
- On Alarms, tap Got a link?.
- Paste the Luma or Partiful invite and tap Open it. Rocco reads the event's name, picture and start time.
- Under Goes off, pick At start, 30 min, 1 hr or 2 hr. One hour is the default.
- Choose who it is for: public, so anyone with the link can ride it, or friends, for a members-only club.
- Tap Create alarm. The alarm's page opens with its link ready.
3. Pick the right moment
| Event | Ring | Why |
|---|---|---|
| Evening meetup after work | 1 hr | Time to leave the office and get across town |
| Saturday morning class | 2 hr | Time to wake, eat and travel |
| Run club or park clean-up | 30 min | People live close; they need shoes on, not a commute |
| Online workshop or AMA | At start | Everyone joins at once |
| Conference side event | 1 hr | Between sessions, people need a nudge to walk over |
Ringing at the start time of an in-person event only tells people they are late.
4. Post one link where people already are
Put lfg.gm/a/<alarm-code> in the event description, the last update you send, the group chat and the club newsletter. Say what it is in one line: "Tap to get an alarm an hour before doors, so you leave on time." Joining is free.
5. Read the headcount
Tapping going takes a second. Joining an alarm takes intent. You can see who is riding the alarm, so that list is a better number for chairs, food and the room booking than the RSVP count. Plan for the riders, then add a margin for walk-ins.
6. Put the details in the note and the link
Every alarm carries a creator's note and a link. The note answers the questions people ask at the door: "Doors at 6:30, enter on Elm Street, second floor, ask for the robotics club." The link opens when people answer the alarm: the Luma page, a map pin, the video call link. You can change the note any time, even after people have joined, so a room change still reaches everyone.
7. Talk before the event
Friends and public alarms have comments and hearts. People can ask "is there parking?" or "can I bring a friend?" on the alarm while it waits, and the answer is there for everyone. A busy comments section also shows the event is happening.
8. Reward the first to answer
When it rings, everyone taps I'm up, and the wake board shows who answered first. Promise them something small: first pick of the snacks, the front row, the aux at the after-drinks. It turns the reminder into a little game instead of a nag.
For recurring clubs
A weekly class or club does not need a new event link every week. Make a repeating time alarm for the same slot, share it once, and members ride it for as long as the club runs. If members are in different time zones for an online session, keep Same time zone for everyone so the alarm rings everyone at the same moment.
If you use an AI assistant with the LFG Alarm connector, it can set the weekly alarm and give you the link:
Have your AI agent make it.
Paste this into ChatGPT, Claude, Grok or any AI agent that can add a connector, not into the LFG Alarm app. The setup steps come with it: get the LFG Alarm app, connect it to your agent once, and your agent makes the alarm in your account.
Use LFG Alarm to set a public alarm for 6:00pm every Thursday called Thursday code club, with "DOORS 6:30, 2ND FLOOR" written on the wallpaper, and give me the link to post in our group.
Already have the LFG Alarm app and connected it to your AI agent?
Why it works. A repeating time alarm covers every week from one link, and the words on the wallpaper answer the first question at the door.
Event alarms from a Luma or Partiful link are made in the app or on lfg.gm.
Common mistakes
- Counting RSVPs as attendance. Plan for the people riding the alarm.
- One reminder, days early. The day-before email is fine; the alarm is for the hour people need to move.
- A vague note. "See you there!" helps nobody. Name the door, the floor and what to bring.
- Posting the link once. Put it in the event page and again in the last update.
- Making it feel like a chore. Pick a fun sound, let Rocco roast a snooze on a mild chaos level, and reward the first one up.
Sources and further reading
- PheedLoop, Event Data Lab Report #05: no-show rates across 1,070+ events
- Gurol-Urganci et al., Cochrane review: mobile phone text messaging reminders for attendance at healthcare appointments, 2013
- UK Government, A zero-cost way to reduce missed hospital appointments
LFG Alarm is not affiliated with Luma, Partiful or PheedLoop.
