Spaces

First-reply checklist for event organisers answering attendees

This checklist lists what a good first reply to an attendee contains, from the event date to a clear next step. It is for event organisers who want every attendee to feel looked after from the first message.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Attendees write when they are excited, rushed or a little worried. Someone asking what time doors open on Saturday is often already planning their evening. A slow or vague first reply makes them hunt through the ticket page, or give up and ask a friend instead.

Tick through the list below as you read it, and note which points your team already does and which it forgets. Then turn the gaps into one short written rule that your team, or your AI agent, can follow every time someone writes in about your event.

Tick each one as you go. 0 of 9 done.

[ ] Name the event and the date in your first line.
[ ] Answer the actual question before anything else.
[ ] Give the time in plain words, like 6pm, with the doors and start time kept apart.
[ ] Say where to go, including which gate or entrance to use.
[ ] Link to the page that holds the full details.
[ ] Ask for the name on the booking only when you truly need it.
[ ] Say which questions a person on your team will answer, such as refunds.
[ ] Mention access help if the question touches on mobility or other needs.
[ ] End with one clear next step.

What a good first reply looks like

Say an attendee writes, "Can I bring a bag?" A strong first reply gives the rule, the size limit if there is one, and where the bag check happens. It takes four short lines and it answers the question they will ask next.

Keep the tone of your event. A food festival can sound relaxed. A conference should sound calm and clear. Either way, short sentences beat long ones, because most attendees read on their phone while walking.

Mistakes that cost you goodwill

These slip in when the inbox is busy, so check for them every week.

  • Copying a long policy into the chat instead of the one line that matters.
  • Using internal words like load-in or hold, which attendees do not know.
  • Forgetting to say which day or session you mean.
  • Promising a refund or an upgrade before your team has agreed.

FAQ

How fast should the first reply be before a big event?

As fast as you can manage, since questions pile up in the last few days. An AI agent can answer the common ones straight away while your team handles the rest.

Should the first reply include a greeting?

Yes, but keep it to a few words. A quick hello and the event name, then straight to the answer, feels friendly without making them wait.

What if the attendee asks about a refund in their first message?

Say you have passed it to the team, ask for the booking name, and tell them when to expect an answer. Refunds should always go to a person.

More free tools for event organisers

Read the guide: Answer attendees' questions with an AI agent.