How to prepare EVA to support your attendees with control

Before putting AI in front of your attendees, you need to decide what it may say, what it may do and who intervenes when a conversation needs help.

With EVA, organisers control the agent’s knowledge, can intervene in conversations and can find unanswered questions to answer personally. Available information and actions are limited according to the user.

These capabilities help address the risks of AI attendee support. Their value also depends on how you prepare the event and who takes responsibility while it is running.

Start with a task that has clear limits

One approach to rollout is to start with practical event information: approved timings, locations and access conditions.

Before expanding the scope, agree which topics the agent will cover, which commitments it cannot make and which questions should reach the team. Explaining a cancellation policy, for example, does not imply authorisation to grant an exception.

This is the process we propose for preparing attendee support with EVA. It does not assume that every integration or action you might imagine is available.

Decide what knowledge the agent will have

Organisers control the information available to EVA. This lets you prepare the service with the current programme, confirmed conditions and details you want to communicate.

The important decision is what you will treat as valid information. If two documents disagree, resolve that before making them available to the agent. More documents do not necessarily mean a clearer answer.

When a fact is missing, you need a way to discover the gap. EVA detects unanswered questions and lets the team find and answer them. Those questions also help identify information your event needs.

Limit each user’s information and actions

A registered attendee should not receive another person’s personal information or perform an action they are not permitted to take.

EVA’s approach is to give the agent the personal context belonging to that user and the specific actions permitted for them. Protection is established by limiting what it receives and what it can execute; it is not left solely to an instruction in the prompt.

When preparing the event, review real situations: different ticket access, private activities or actions requiring authorisation. If an action requires an integration, confirm its availability and permissions for that case.

This separation reduces exposure. You still need to check the configuration and test relevant cases.

Keep the team involved in the conversation

You can intervene in conversations with EVA. Unanswered questions can be found and answered personally.

To make use of that control, assign someone to review them and decide how they will be resolved during the event. Being able to intervene does not mean someone is automatically monitoring every conversation.

Imagine a question about a transfer whose timetable has not yet been confirmed. The team can resolve it, answer the attendee and update the information once confirmation exists. The question also helps improve available knowledge.

Update information when the event changes

Organisers can update EVA’s information in real time. You do not need to wait until the event ends to correct a time or location.

If EVA is connected to your event management software, such as Eventscase, or to EVA Brain, data can synchronise automatically depending on the configured integration. Changes in the connected source can then feed into the agent’s knowledge without having to enter them again in EVA.

After an important change, check what the agent answers. Also consider whether people who already received the previous information need an additional message. Updating knowledge and correcting an earlier communication are different tasks.

What to test before getting started

A useful demonstration should include more than questions the agent can answer. Try a question without an answer, a request without permission, an information change and a conversation you want to handle personally.

Check the complete result: what the attendee receives, what the team can find and how information is updated afterwards.

You can explore EVA and request a demo. Bring a case from your event that concerns you: a sensitive question, private access or a last-minute change. The useful part is seeing how that case is handled and what your team needs to maintain control.