Follow-ups

Chase the RSVP nobody's answered yet

The date is close and half the guest list has not answered. Beemy works out who is missing. It drafts a friendly nudge in your voice to those guests only.

4 min read

PersonalFollow-ups
GmailCalendar

When the guest list is half-answered

The party is a couple of weeks away. Some replies are in and some are not. Chasing stragglers one by one means re-reading the whole invite thread to remember who is who.

The example

What it looks like when this runs.

Illustrative

Illustrative example, built with mock data.

In Gmail · personal

What arrived

Party invite thread

Sarah's birthday: 12 replies, 8 still missing

Half the guest list has not answered Sarah's party invite. The date is close enough that chasing them matters now.

Beemy's draft

Quick one: Sarah's birthday on Saturday

A friendly nudge for the eight guests who have not replied, each worded the way you would write to that person. Everyone who already answered, including a firm no, is left alone.

You approve the batch, and only the missing guests hear from you.

How Beemy handles it

3 steps, approval-first the whole way.

  1. 01

    Checks who has replied

    Beemy reads the invite thread and the calendar responses. It works out who has answered and who has not, with no manual list-checking.

  2. 02

    Drafts a nudge to only the missing guests

    The reminder is friendly and short. It goes only to people who still need to answer. Nobody who has already replied gets a repeat message.

  3. 03

    Waits for your approval before sending

    You see who Beemy is about to nudge and what the message says. Nothing goes out before that.

What you still decide

  • Each nudge waits for your approval, guest by guest, until you promote this category yourself.
  • You choose the tone: a light joke for a close friend, a plainer note for someone you know less well.
  • If a guest replies with a real question about the event, the reply goes to you. That guest does not get a second nudge.

The honest scope

What it reads. What it can do. What it never does.

Reads

  • The invite thread and calendar responses, so Beemy knows who has answered
  • Your past messages to each guest, so each nudge sounds like you

Can do

  • Drafts a nudge to whoever has not answered and holds it for your approval
  • Re-checks responses before the next nudge, so nobody gets chased twice

Never

  • Never sends a nudge without your approval until you promote the category yourself
  • Never lets this personal guest list inform a work draft, or the reverse
  • Never nudges a guest who has already declined, because a decline counts as an answer

The hard part: nudging only the right guests

A mass reminder to the whole list annoys the people who already answered. One missed name looks like you forgot that person. Beemy works out who is still missing. It then writes to each of them as someone who knows them. That makes the nudge feel personal, not automated.

Questions

Fair questions, straight answers.

Will it nudge people who already said no?

No, a decline counts as an answer, so Beemy leaves that guest alone.

Does it send the same message to everyone?

No, Beemy drafts each nudge for one guest, in the tone you would use with that person. Each one still waits for your approval.

Can it handle a work event guest list the same way?

Yes, the same job works for a work invite. That thread stays in your work silo, and a personal guest list never informs a work draft.

Get your time back.

Beemy is in private beta. We send invites in rolling batches. We cannot promise a date. When your invite arrives, connect Gmail. Beemy sorts your inbox in that first session.

We use your email only to write to you.

Talk to us

Last updated