Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jointoevent.io/llms.txt

Use this file to discover all available pages before exploring further.

The AI Assistant — powered by Event Architect — lets you configure event settings without navigating menus manually. You type a plain-language description of the changes you want, the assistant parses your request into a structured plan, and you review every proposed change before anything is written to your event.
The AI Assistant is in Beta. Results are generally accurate, but always review the plan preview before applying changes. Complex prompts may take up to a few minutes to process.

​
How to access the AI Assistant

Navigate to your event in JTE Panel, then select AI Assistant (Beta) from the left sidebar under your event’s management section.

​
The parse → review → apply workflow

Every change goes through three explicit stages so you stay in control at all times.
1

Describe your changes

Type a plain-language description of what you want to change in the text area. You can reference capacity limits, tickets, registration form fields, the landing page, webhooks, and email templates in a single prompt.The prompt field accepts up to 25,000 characters. Use the Generate email templates checkbox if you also want the assistant to draft transactional email content — note that this extends processing time.Enable Start from scratch if you want the assistant to replace the current configuration entirely rather than build on top of it.
2

Analyze

Click Analyze. Event Architect sends your prompt to the AI gateway, which reads the current event state from the database and produces a structured change plan. A progress indicator appears while the request is in flight.Your session is preserved server-side. If you close and reopen the page, the last parsed plan is automatically restored.
3

Review the plan preview

Once analysis completes, a collapsible Change preview panel appears. Expand each section — capacity, tickets, form fields, landing page, email templates, webhook — to inspect every proposed change before committing.If the plan is not what you intended, update your prompt and click Analyze again. The new plan replaces the previous draft.
4

Apply changes

Click Apply changes to write the plan to your event. The assistant displays a summary showing tickets created, updated, or deleted; form fields saved; capacity and landing page messages; and webhook status.After applying, the session is cleared automatically. You can start a new prompt immediately.

​
Resetting a draft

If you want to discard a parsed plan without applying it, click Clear session. This deletes the server-side session and clears the local prompt and preview. Nothing is written to your event.

​
Example prompts

The following prompts illustrate the range of changes you can describe in a single request.
Be specific about names, prices, and limits. The more detail you provide, the more accurate the generated plan will be.
Tickets and capacity 
Set the capacity limit to 300. Add a paid ticket called "Standard" for 149 PLN
and a free ticket called "Student" with a limit of 50 uses.
Registration form 
Add three form fields: Company (text), Job title (text), and T-shirt size
(single choice: S, M, L, XL). Make T-shirt size visible only when the
attendee selects the Standard ticket.
Landing page 
Set the event description to "Annual product summit for engineering teams."
Add two speakers: Anna Kowalska (CTO, Acme Corp) and Jan Nowak (Lead Engineer, Beta Ltd).
Show the agenda and speakers sections.
Combined changes 
Set capacity to 500. Add an Early Bird ticket for 99 PLN available until
2026-06-30, and a Regular ticket for 149 PLN. Add form fields for company
and job title. Set the landing page tagline to "The region's largest tech event."
Email templates Enable the Generate email templates checkbox, then write: 
Generate a welcome email for the Standard ticket. The subject should be
"Your registration is confirmed" and the body should thank the attendee
and include the event date and venue.

​
What the plan covers

SectionWhat you can configure
CapacityAttendance limit on/off, numeric limit
TicketsName, price, free flag, per-ticket use limit, availability dates
Form fieldsLabel, field type, dropdown options, conditional visibility rules
Landing pageTitle, description, layout, hero image, speakers, agenda items, location, section toggles
Email templatesSubject and HTML body for welcome, payment confirmation, bank transfer, and invited-attendee emails
WebhookTarget URL, secret, subscribed event types

​
Session behavior

Your draft plan is stored server-side and scoped to your user account and the specific event. Opening the same event in multiple browser tabs shares one session and one current plan. The session expires after 120 minutes of inactivity; any activity (loading or updating the plan) resets the timer.
If the session timer expires between parsing and applying, you will need to re-run the analysis before you can apply changes.