Answering attendee questions is an inevitable part of event planning. That said, with all the other balls your juggling, it can be hard to take the time to answer the same questions over, and over, and over…and over again.
That’s where an FAQ, or « frequently asked questions, » page comes in handy. Here are some thoughts on writing your FAQ page in a way that’ll effectively keep attendees in-the-know:
Put yourself in their shoes. What would YOU want to know if you were attending your event? Think about the attendee experience from registration to the days following the event and jot down any questions that could come up along the way. (Tip: This could be a fun brainstorm meeting with your team!)
Write it early and point to it often. Start by building out the basics – date, location, time, etc. – and add to it when other details come up. You could even use an updated FAQ as an excuse to stay top of mind and send regular communications to registrants. (Without being annoying, of course.) A few other places that make sense for linking your FAQ: The registration confirmation page, social media, and in your event app.
Don’t be afraid to dumb it down a little. Being so close to the planning process means that the details are going to be much more obvious to you. If something funky or complicated comes up in the planning process, chances are your registrants will struggle with it significantly more – so it’s ok to hold their hand a little.
Look at the FAQs of events you admire. Imitation is the sincerest form of flattery, right? Take a look at what questions similar events are answering on their FAQ and – if it applies to yours – answer it! If anything, this exercise may spark ideas for answering questions you hadn’t considered yet.
Anticipating attendee questions means your attendees can put the more trivial (although important!) details aside, and really focus on your event’s content. That’s key to paving the way to an engaged group! To really supercharge your attendee engagement, take a look at the tips in our free guide.
Text and image by Eply