Workspace
Run many congresses with guided setup, per-congress settings, team permissions and a reusable operations library.
ONE PERSON · ONE RECORD
Registration, room, flight, transfer, payments, and documents stay on the same person record without retyping.
The problem today
CURRENT STATE
Registration, rooming, flights, transfers and finance sit in separate sheets or tools.
Names, dates and invoice details are copied between teams and systems.
Operators reconcile replies, attachments and updates by hand.
Gaps between travel plans, booked nights and transfer runs are easy to miss.
How it works
Every change is written to the same person record, so registration, rooming, transfer, flight, payment, and badge updates stay connected without retyping.
SAME PERSON RECORD
Invited or registers
Fills form
Room assigned
Flight ticketed
Transfer planned
Pays
Badge printed
Checked in
Module overview
Scan the full operational surface in one pass, then open the complete catalog when you need module-level detail.
Run many congresses with guided setup, per-congress settings, team permissions and a reusable operations library.
Keep details, stays, flights, accounts, documents, warnings and change history on one person card.
Collect participation, nights, courses, gala choices, transfers and payment through a phone-friendly Turkish and English flow.
Send scoped invitations and collect acceptance, travel plans, dates, ticket names, identity documents and companions through a personal link.
Create conditional forms without code and give each attendee one page for plans, payments, documents and approved changes.
Manage allotments, night-by-night rooming, issued tickets, individual transfers and shared shuttle runs.
Coordinate sessions, halls, speakers, committees, multi-currency accounts, payments, refunds, invoices, sponsors and contracts.
Design QR badges, track attendance and publish a congress website with ready content blocks.
[SCREENSHOT: attendee page]
Attendee experience
Every attendee sees one clear page for updates and documents, while change requests stay controlled and only move forward after operator approval.
Days, accommodation, flights, payments and documents stay together.
Change requests go to one operator inbox for review.
The operator decides what changes before the record is updated.
AI assistant
Ask plain-language operational questions and receive prepared actions the operator can review before anything proceeds.
Nothing changes until the operator approves.
Coming soon — not available yet
These items are planned and are not part of the currently available module set.
Planned with delivery status.
Planned for future availability.
Primary action
See how one attendee record can keep registration, rooming, flights, transfers, payments, and documents connected without retyping across teams.
Tell us about your team and event. We will follow up with a relevant walkthrough.
Editor note: configure the recipient and submission endpoint in Email settings before publishing.