Twilx for Guests
Twilx keeps event information in one place. A guest can open a public page, check the date and venue, go to ticket purchase, sign in by phone, see events connected to them, open a ticket or invitation, send a question to the team, and receive messages from the organizer.
The available capabilities depend on the event. One event can use only a public page; another can also include invitations, mobile access, requests, messages, and notifications.
How a guest gets to Twilx
A guest usually opens Twilx:
- through a public event link;
- through an invitation link;
- from SMS, Telegram, or another organizer message;
- after buying a ticket;
- through mobile sign-in when the event uses this access.
If the link points to a specific event, Twilx keeps that direction. After phone confirmation, the guest returns to the same event, ticket, invitation, or request when that personal context is found.
What is available without sign-in
Without sign-in, the public part of the event usually opens. It can include:
- event title;
- date, time, city, and venue;
- description;
- program;
- participants or lineup;
- ticket purchase link;
- participation options visible to guests;
- question or request form;
- team contacts;
- legal documents and consents.
If a block is missing, the organizer has not added it for this event or has disabled its display. Read more: event page.
Why phone sign-in is needed
Sign-in is required for personal data: ticket, invitation, closed access, request history, messages, and events connected to the guest. Twilx does not show this data to a random page visitor.
The flow usually works like this:
- The guest opens a link.
- Enters a phone number.
- Receives a one-time code.
- Confirms the code.
- Returns to the event or personal screen.
The phone number connects the guest to an invitation, purchase, request, or imported list. If the ticket or invitation was created for another number, the event may not appear after sign-in.
What can be available after sign-in
After sign-in, the guest can see:
- a list of events connected to them;
- ticket or invitation;
- participation status;
- organizer messages;
- request replies;
- notifications;
- consent settings;
- mobile event access.
The exact set of screens depends on event settings and data that the organizer has passed to Twilx.
Questions, requests, and messages
The event page can contain actions for contacting the team: a question, table request, special area, menu, booking, or another participation option. After submission, Twilx connects the request with the event, guest phone, and selected action.
The organizer can send event messages: reminders, program changes, logistics, links, or replies to a request. The delivery channel depends on event settings, consents, phone number, device, and browser permissions.
Mobile access
Mobile access helps a guest return to an event from a phone. It can open as a mobile web page or as a Telegram flow when the organizer uses that channel.
Mobile access can include guest events, ticket, messages, requests, notifications, and consent settings. Read more: guest mobile access.
Common situations
If the event does not appear after sign-in, check the phone number. It must match the number used for purchase, invitation, or request.
If the code does not arrive, check the number, wait for retry, and request the code again. If the attempt limit is reached or the number cannot receive SMS, use the organizer contact.
If a link asks for sign-in, this is expected for personal data. After phone confirmation, Twilx should return the guest to the original event or invitation when a link is found.
If the ticket is not ready, the organizer may still be importing a list, confirming invitations, or synchronizing data from an external service. Check the event later or contact the event team.
Security
Do not forward personal links, ticket screens, confirmation codes, or invitations to people who should not have access to your ticket or request history. If a link was sent to another person by mistake, notify the organizer.