Conference chatbot FAQ examples for attendee support

Start from the questions your desk already gets

Read last year’s emails and the questions your volunteers repeated. Group them into registration, programme, venue, practical and technical. Write each answer in one or two sentences and link to the page that holds the detail.

Examples by topic

Use these as a starting list and replace the details with your own.

• Registration: “Can I change the name on my badge?” Answer with the deadline and how to do it.
• Registration: “Where can I download my invoice?” Point to the participant area.
• Programme: “When is the keynote?” Answer with date, time and room from the current programme.
• Programme: “Is there a session on [topic]?” List the sessions and their times.
• Venue: “How do I get from the station to the venue?” Give the route and travel time.
• Practical: “Is there wifi?” Give the network name and how to log in.
• Practical: “Where can I leave my luggage?” Give the location and opening times.
• Poster: “Where is my poster board?” Give the number, and when to hang it.
• Accessibility: “Is the venue step-free?” Answer plainly and give a contact for special needs.

Answers that work in a chat

Write the way you would speak at the desk. Start with the answer, then add one detail. Avoid long paragraphs and jargon, and always give the date or the place rather than “see the programme”.

Decide what must go to a person

Some questions should not be guessed: changes to the scientific programme, refunds, special needs and any complaint. Make the chatbot say so and offer live chat with the info desk. The same principle applies when programme details change: a human confirms them.

A sample answer library

These entries show the length and style that work in a chat window. Each starts with the answer, adds one detail and, where useful, points to a page. Replace the bracketed parts with your own facts, and keep one owner for each answer.

Q: When does registration open on the first day? A: The registration desk opens at [08:00] in [the foyer]. Bring the confirmation email or the QR code from your registration. Q: How long is a talk? A: Oral presentations are [12] minutes plus [3] minutes for questions. Chairs will stop overruns, so please keep to time. Q: Where do I hang my poster? A: Your board number is in your acceptance email and on the programme. Hang posters on [Monday, 08:00–10:00] in [Hall B]. Pins are provided. Q: Can I get an invoice? A: Yes. You can download your invoice from the participant area after payment: [link]. For changes, contact [address]. Q: Is there a quiet room? A: Yes, [Room 2.14] on the second floor is open during all sessions. Q: I have a question about the science of a talk. A: I cannot answer that, but you can ask the speaker after the session, or I can connect you to the info desk.

Organise questions by topic and expect many phrasings

People ask the same thing in many ways: “wifi”, “internet password”, “how do I connect”. Group answers by topic, such as registration, programme, venue, practical, technical and accessibility, and give each answer several example phrasings when the tool allows it. Write the answers once and reuse them on the website, so that a change happens everywhere. Keep a list of the twenty most common questions from previous years and check that each has an answer before you launch.

Fallback and handover messages

The moments when a chatbot cannot answer are the moments that decide whether attendees trust it. Write the fallback message with care. It should admit the limit, offer a next step and never invent an answer.

Fallback I am not sure about that. You can ask the info desk in [the foyer] or write to [address]. Would you like me to connect you to a person now? Handover I am connecting you to the info desk team. They are online from [08:00] to [18:00]. If nobody replies within [5] minutes, please call [phone]. Outside hours The info desk is closed at the moment and will reply from [08:00]. In an urgent case, please call [phone].

What not to automate

Automation suits questions with stable, factual answers. It suits badly anything that needs judgement, changes quickly or carries risk.

• Programme changes made on the day: a person must confirm them before the chatbot repeats them.
• Refunds, fee waivers and exceptions to rules.
• Medical, safety or security matters: give the emergency number and hand over to a person.
• Complaints and conduct reports: acknowledge and hand over.
• Anything that requires reading a person’s registration record unless the tool is set up to do it safely.

Testing before the meeting

Prepare thirty real questions, including misspelled ones, and ask three colleagues to put them to the chatbot. Mark each answer as correct, partly correct or wrong, and count the results. Fix the wrong ones first, then the partly correct ones. Repeat with the questions that colleagues invent themselves, since they show what you did not think of. Test the handover to the info desk end to end, from the chatbot to the person who must reply, and make sure that person knows what to do. Do this a week before the meeting, and again the day before.

Read the logs and improve every day

The conversation log is the best source of insight on what attendees need. Each evening, read the questions that the chatbot could not answer or answered poorly, and add or improve an answer. Note the questions that were asked most often, because they may point to something the website or programme should make clearer. Keep the improvements small and frequent rather than saving them for a big revision, since the meeting is short and the value of a fix is highest while people are still there.

Several languages

If attendees come from several countries, write the answers in each language you promise to support, and check the translations with native speakers. Do not translate automatically without a check, since a mistranslated room number or time causes real problems. If you cannot support a language fully, say so in the welcome message, so that attendees know what to expect, and point them to a person who can help.

Privacy of conversations

Chat messages may contain personal data, for example names and email addresses. Tell attendees at the start what is recorded and who can see it, keep the log only as long as you need it, and restrict access to the people who work with it. Ask attendees not to send sensitive information in the chat. If you use a third-party messaging platform, check its terms and make sure they are compatible with your privacy notice.

Keep the answers in sync

The chatbot must give the same answer as the website. Review the FAQ whenever the programme or the practical details change, test it with ten questions the day before the meeting and read the conversation logs each evening to spot gaps.