ONE PERSON · ONE RECORD

One platform for all congress operations.

Registration, room, flight, transfer, payments, and documents stay on the same person record without retyping.

The problem today

Fragmented congress operations slow every handoff.

CURRENT STATE

  1. One person, several files

    Registration, rooming, flights, transfers and finance sit in separate sheets or tools.

  2. The same detail gets typed again

    Names, dates and invoice details are copied between teams and systems.

  3. Changes travel through email

    Operators reconcile replies, attachments and updates by hand.

  4. Warnings arrive too late

    Gaps between travel plans, booked nights and transfer runs are easy to miss.

How it works

Follow one attendee across the congress

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

  1. Invited or registers

  2. Fills form

  3. Room assigned

  4. Flight ticketed

  5. Transfer planned

  6. Pays

  7. Badge printed

  8. Checked in

Module overview

Operations stay connected

Scan the full operational surface in one pass, then open the complete catalog when you need module-level detail.

  1. Workspace

    Run many congresses with guided setup, per-congress settings, team permissions and a reusable operations library.

  2. People

    Keep details, stays, flights, accounts, documents, warnings and change history on one person card.

  3. Registration

    Collect participation, nights, courses, gala choices, transfers and payment through a phone-friendly Turkish and English flow.

  4. Guests and speakers

    Send scoped invitations and collect acceptance, travel plans, dates, ticket names, identity documents and companions through a personal link.

  5. Forms and attendee page

    Create conditional forms without code and give each attendee one page for plans, payments, documents and approved changes.

  6. Accommodation, flights and transfers

    Manage allotments, night-by-night rooming, issued tickets, individual transfers and shared shuttle runs.

  7. Program and finance

    Coordinate sessions, halls, speakers, committees, multi-currency accounts, payments, refunds, invoices, sponsors and contracts.

  8. Badges and congress website

    Design QR badges, track attendance and publish a congress website with ready content blocks.

[SCREENSHOT: attendee page]

Attendee experience

One page for every attendee.

Every attendee sees one clear page for updates and documents, while change requests stay controlled and only move forward after operator approval.

  1. See the full plan

    Days, accommodation, flights, payments and documents stay together.

  2. Request a change

    Change requests go to one operator inbox for review.

  3. Wait for approval

    The operator decides what changes before the record is updated.

AI assistant

Ask the congress. Review the action.

Ask plain-language operational questions and receive prepared actions the operator can review before anything proceeds.

  • Who has no return flight yet?
  • Which guests still have missing information?
  • Where do booked nights and flight dates not match?

Nothing changes until the operator approves.

Coming soon — not available yet

Planned capabilities, clearly separated

These items are planned and are not part of the currently available module set.

Automated invitation emails and reminders

Planned with delivery status.

WhatsApp notifications

Planned for future availability.

Primary action

Request a demo for your next congress operation

See how one attendee record can keep registration, rooming, flights, transfers, payments, and documents connected without retyping across teams.

  • Built for PCOs, MICE agencies, and association secretariats.
  • Grounded in operational workflows: allotment, rooming, shuttle run, and badge production.
See how it works

Tell us about your team and event. We will follow up with a relevant walkthrough.

Use a valid work email format, for example [email protected].

Your demo request was received. Our team will review the details and contact you.

Editor note: configure the recipient and submission endpoint in Email settings before publishing.