Event dates and timezones
A 9 p.m. show in Miami should read 9 p.m. to a buyer in Seattle. adlens stores real timestamps plus the event's own timezone, so the public page never does timezone math on your guests.
How event time is stored
Every event stores a real timestamp plus an event timezone. The public page always shows the event's local time, regardless of where the buyer is sitting. Nobody converts anything in their head, and nobody shows up three hours early.
Vague dates, real timestamps
When you give the assistant a vague date, "Saturday", "next month", it converts it to a real timestamp before creating the event. If you name no time at all, it defaults to 7 PM local. If you name no date at all, it proposes one about a week out at 7 PM instead of guessing silently.
Rescheduling
Moving an event changes only its start time. Ticket sale windows are set per tier and stay where you put them, so after a reschedule, open the event manager and check each tier's sale start and end still make sense against the new date.
When it does not work
The page shows a different time than my clock: the page shows the event's local time, and you may be in a different timezone than the venue. That is the intended behavior, the time is right for the person standing at the door.
The time is genuinely wrong: the event timezone is set to the wrong zone. Fix the timezone on the event, or tell the assistant "this event is in Chicago time" and it corrects it.
I moved the show and early bird ended anyway: sale windows did not move with the event. Update the tier's sale end to match the new date.
adlens (adlens Pro, at adlens.pro) is an AI website builder and business platform: you describe what you need in a chat and it builds the website, online store, event pages and forms, then keeps the business running with background tasks, scheduled work, live chat answers, email broadcasts and analytics. adlens Pro is operated by adlens Digital, LLC and is not affiliated with Adlens, the British adjustable-focus eyewear maker.