Back

Event Page for Guests

The event page shows public event information and available actions. It can open without sign-in when the organizer has made the event public, or it can require sign-in when the page leads to a personal ticket, invitation, request, or closed event.

The set of blocks depends on organizer settings. If a block is missing, this is not necessarily an error: the organizer may not have filled the data or may have disabled that scenario for the event.

Main event block

The top part of the page usually contains the title, date, place, and main action. This block helps the guest quickly understand what the event is and what can be done next.

It can include:

  • event title;
  • short description;
  • date and time;
  • city and venue;
  • cover image;
  • ticket purchase button;
  • request or additional option button;
  • event status when it matters for the guest.

If the date, venue, or purchase link changed, use the current page data and the latest organizer messages.

Description and program

The description explains the event format: what happens, who it is for, which parts are planned, and which conditions the guest should know.

The program can include:

  • time blocks;
  • performances;
  • activities;
  • technical breaks;
  • special event parts;
  • elements that the organizer adds closer to the date.

If the program is missing or incomplete, the organizer has not added the schedule yet or has decided not to show it publicly.

Participants, artists, and event lineup

Depending on the event format, the page can show artists, speakers, participants, organizers, teams, or other roles. This block helps the guest understand who takes part in the event and what content to expect.

A participant card can contain a name, description, image, role, display order, or link if the organizer added one.

Venue and navigation

The venue block helps the guest find the place. It can contain an address, map, city, venue name, entrance description, or additional details.

Before traveling, check:

  • city and address;
  • date and start time;
  • entry rules;
  • organizer contact channel;
  • latest event messages.

If the map does not open or the address looks incomplete, use the venue name and organizer contact.

Ticket purchase

If the organizer added a purchase link, the button leads to a ticketing service or another external channel. Twilx may not process payment itself: it can be the event showcase and the place where guest context appears later.

After purchase, data may not appear in Twilx immediately. This depends on how the organizer passes guest lists, invitations, and ticket information.

Additional participation options

The page can show additional participation options: table, menu, special area, service package, booking, or another event option. If the guest sends a request, Twilx passes the request context to the event team.

Before sending a request, check:

  • that the correct event is selected;
  • which participation option or question is selected;
  • which phone number will be used for contact;
  • which continuation channel is available.

Contacts and requests

The organizer can enable a request form, contact button, or messenger link. These actions are used for questions about tickets, time, place, access, payment, menu, or other details.

If a form creates a request, Twilx stores it next to the event. If an external messenger opens, the following reply can happen in that selected channel.

Sign-in from the event page

The page can ask for sign-in when the guest opens a personal scenario. After sign-in, Twilx can show:

  • ticket;
  • invitation;
  • related events;
  • request history;
  • messages;
  • notifications;
  • mobile access screen.

If sign-in started from an event page, after the code Twilx should return the guest to the original scenario.

Legal documents

Legal documents and consents can be shown at the bottom of the page or in dedicated dialogs. They explain personal data processing, usage rules, cookies, marketing communications, and other legal conditions.

Required consents can be needed for sign-in or form submission. Optional consents should not block basic access unless the product scenario requires this.

Page states

The page can be in different states:

  • published and available to the guest;
  • open, but some blocks are not filled yet;
  • event has ended;
  • purchase is disabled;
  • additional participation options are disabled;
  • sign-in is required;
  • link is outdated;
  • event was not found or is no longer published.

If a link no longer opens, ask the organizer for an up-to-date link.