The start time with no finish
People turn down events they could have attended because they cannot tell whether they will be free for a four o'clock call. Always give the end time, even an approximate one.
Let’s write an email!
Type a few lines about what you need to say, or paste your notes. Replying to someone? Open Details above and paste their email.
People decide whether to accept an invitation by checking it against the rest of their week. They need the date, the start and end time, the place or the link, and whether there is anything to bring, pay or prepare. An invitation that makes them dig for any of these, or leaves one out, gets a slower answer or a question in place of an answer.
The other thing that moves replies is a reason. An email that says why this particular person or team is being invited reads as an invitation; one that could have gone to anyone reads as a notice. One sentence is enough: you handle most refund escalations, so this session is built around your cases.
Put the event details, the audience, the reply-by date and anything practical in your brief. Our email writer drafts the invitation and offers a main subject with two others to compare. Pick Friendly for colleagues and social events, Professional for clients and partners, Formal for ceremonies. It will not add details you did not give, so a missing end time stays missing until you supply it.
The name of the event and what it is, the date, start and end time, the venue or joining link, who is hosting, and why the reader is invited. Add cost, dress code, food and access details where they apply. Finish with how to reply, to whom, and a reply-by date, and say what happens next, such as a calendar invite or ticket.
A real run of the Email Writer with the Invitation purpose, printed unedited.
Invite the twelve members of the customer success team to a half-day workshop on handling refund requests, Thursday 9 October, 13:00 to 17:00, in the Rowan meeting room, lunch provided at 12:30. Ask them to reply by Friday 3 October and to mention any dietary needs. Led by Amira from Support.
Purpose Invitation, tone Friendly, standard length. No recipient or sender name was given in Details, so the greeting and sign-off are the tool's defaults.
Hello,
You’re invited to a half‑day workshop for the Customer Success team on handling refund requests. It will take place on Thursday, 9 October, from 13:00 to 17:00 in the Rowan meeting room, with lunch provided at 12:30. Amira from Support will lead the session.
Please reply by Friday, 3 October, and let us know of any dietary requirements you may have.
We look forward to seeing you there and strengthening our approach to refunds.
Best regards
Generated by the Email Writer on 18 September 2026 and printed here unedited. Every date, name and number came from the brief; a draft is meant to be read and edited before it is sent.
Put logistics on their own lines, in a fixed order, after a one-sentence invitation. Readers scan for these facts, and a block of labelled lines is quicker to check than the same information in a paragraph.
| Line | How to write it | Why it matters |
|---|---|---|
| When | Thursday 9 October, 13:00 to 17:00 (lunch from 12:30) | Day name plus date avoids mix-ups; the end time lets people plan the rest of the day |
| Where | Rowan meeting room, 2nd floor | Add the floor, the building entrance, or a map link for visitors |
| Online | Joining link, plus the time zone if anyone is abroad | A link without a time zone produces people arriving an hour out |
| Host | Led by Amira, Support team | Tells people who to ask and what kind of session it is |
| Bring or prepare | Two recent refund cases you found difficult | Saves a follow-up email and makes the session better |
| Reply | To me by Friday 3 October, with any dietary needs | Numbers for catering and room size |
Set the reply-by date by working back from what depends on the numbers. Catering orders, room bookings, venue deposits and printed name badges each have their own deadline; the reply-by date needs to fall before the earliest of them, with a few days to chase people who have not answered. For an external event with travel, two to three weeks before is a comfortable margin; for an internal session, a week is usually plenty.
Send a short reminder to people who accepted, two or three days before, with the practical details repeated: time, room, link. Send a separate nudge to those who have not replied before the deadline passes. Do not send the whole invitation again to everyone.
A calendar invitation handles the mechanics well. In Google Calendar you add guests by name or email address, and they can reply Yes, No or Maybe from the invitation email; Google notes that guests do not need to use Google Calendar themselves. The organiser can then see who is coming in the event itself.
What a calendar invite does badly is persuade. Its description field is often skimmed or hidden. For anything people might decline, such as an optional workshop, a client event or a social evening, send an email that explains what it is and why they should come, then send the calendar invite to those who accept, or attach it to the email.
For a routine internal meeting, the calendar invite alone is normally fine; this generator has a separate purpose for meeting requests.
| Event | Tone | Send as |
|---|---|---|
| Team workshop or training | Friendly | Email with details, then calendar invite |
| Client launch or open day | Professional | Email with reply-by date; calendar or ticket on acceptance |
| Leaving drinks or team lunch | Friendly | Short email or a group message |
| Awards, ceremony or formal dinner | Formal | Email, sometimes with a printed invitation |
| Webinar | Professional | Email with registration link and time zone |
When you invite a list of external guests who do not know each other, put their addresses in Bcc rather than To or Cc. Showing everyone's email address to the whole list is discourteous, can breach data protection rules, and invites reply-all chains.
External guests also need practical information your colleagues do not: how to get in, whether there is parking or step-free access, who to call if they are late, and whether they need to bring ID. One extra line on each saves a flurry of individual emails the week before.
Say plainly whether the invitation can be passed on, whether a plus-one is welcome, and whether there is a cost. Guests prefer to know before they accept.
Not every gathering needs a formal invitation. A same-week team lunch works better as a two-line message in the team channel than as a structured email with an RSVP deadline. Match the weight of the invitation to the weight of the event; an over-formal invitation to something casual can make people wonder what they are missing.
People turn down events they could have attended because they cannot tell whether they will be free for a four o'clock call. Always give the end time, even an approximate one.
When the room number sits halfway through a sentence about the agenda, people ask again on the day. Give time, place and link their own lines.
Let us know if you can come produces late and partial answers. Give a date, a person to reply to, and what they should mention, such as dietary needs.
An online event at 3pm is a different time for a guest in another country. State the time zone, and for mixed audiences give the main two.
Allow enough time for people to plan and for you to confirm numbers. For an internal session, a week or two is usually enough. For external guests, client events or anything involving travel, three to four weeks or more is kinder. Set the reply-by date before your catering or venue deadline.
The event and the date, so recipients can check their calendar from the inbox: Invitation: product launch, Thursday 9 October. Add the place for in-person events if it fits. Avoid subjects that could be anything, such as Save the date or You're invited with no event named.
Use Bcc for external guests or anyone who does not already share contact details, so addresses are not exposed and people cannot reply to everyone. For a team that already emails each other, putting everyone in To is normal and lets people coordinate.
Choose Formal tone and give the full name of the event, the host organisation, date, time, venue and dress code. Name the person who takes replies and the date you need them by. Keep the wording plain; formality comes from completeness and courtesy rather than ornate phrasing.
Send one short, friendly reminder that repeats the event, date and reply-by date and asks for a yes or no. If numbers matter, a direct message or call to the few remaining people is often quicker than another email to the group.
Yes. Include the platform, the joining link or how it will be sent, the start and end time with a time zone, and anything attendees should do beforehand, such as registering or testing their audio. The generator will place these in the email as you give them.
Written and checked by the AI Writing Assistant team. Last reviewed . Sources: Google Calendar Help: Invite people to your event.
Each page opens the writer with that purpose already selected, shows a real draft the tool returned from a one-line brief, and explains what that kind of email has to do. The purpose menu above the brief covers all sixteen.