AI Assistant and Agent Tools

This concept brings AI to EventfullyManaged event data in two ways. The first screen places an Assistant panel beside an attendee profile, where it answers questions using the record the organizer is already looking at. The second is an AI Agents page that connects an organizer's own AI client to the workspace through the Model Context Protocol (MCP), exposing event tools, read-only resources and guided workflows.

Event teams answer the same questions all day: what did this attendee buy, are they checked in, how many seats are left in a session, which sponsor is behind on leads. Finding each answer usually means opening several screens or exporting a list. Teams that already work in an AI client also want it to act on their event data without copying records into a chat window or granting it broader access than they hold themselves.

In the assistant illustration, the profile shows an attendee's name, email, company and role, a Registrations list with status pills such as Confirmed and Checked in, and a Messages thread with the organizer. The Assistant panel carries a context chip naming the attendee in view, so a question as short as "What has she registered for?" returns a plain-language summary of both registrations, their amounts and their status. The question box invites questions about this attendee, a status strip notes that event-domain grounding is in progress, and a counter shows how many assistant credits remain.

The agent tools illustration sits under Settings. A connection card shows the server, its transport, the signed-in user and a Connected badge, with a Copy client config button for setting up an AI client. Counters summarize tools, resources and guided workflows, and a Tool groups table lists each area of the product, from events, agendas, venues and ticketing to registration, check-in, sponsorship and networking, with its tool count, whether it can write, and whether confirmation is required. An amber banner flags delete operations as destructive tools that the design intends to put behind confirmation. Two guided workflows cover event setup, from the event and venue through agenda, tickets and opening registration, and event operations, from KPIs and check-in to leads, networking and communications, while read-only resources expose the schema, dashboard, events and venues.

Both surfaces follow the principle stated on the agents page: every call uses the permissions of the person who connects. The assistant and the agent tools reach the same records as registration, check-in and analytics, so AI works on the one event record rather than on a copy.