Skip to content

Cookies and tracking

No third party is contacted until you choose. We do keep our own count of pages opened and forms started, which sets no cookie and keeps no name, address or account — just enough to tell two visits apart on one day, and meaningless the next. That is why it is not one of the switches below. Everything that would hand data to somebody else is. You can change your answer at any time from the link in our privacy notice.

Choose what to allow

Loads Google Analytics, which sets its own cookies and tells Google the address of the pages you open here. It is how we see which pages people actually read.

Loads advertising tags from Google Ads, Meta and LinkedIn. They set their own cookies in your browser and receive the address of the pages you open here, which is how we tell which advertisement brought you.

Conclaveby ZEBIQ TECHNOLOGY LLP

On-ground support

Registration run for you, not just software to run it with.

Conclave is the platform. For events that need a crew as well as a login, the Zebiq team takes on the registration operation itself — the set-up beforehand, the desk and the door on the day, and the reporting afterwards.

On the ground

The software, and people who show up.

Six things we take off the committee’s plate. Any of them on its own, or all of them together.

  • Registration desk and check-in

    Our people at the desk on the day — scanning passes, handling the queue, and dealing with the delegate who is not on the list, so the door is somebody’s job rather than the committee’s.

  • Passes and badges on site

    Printing at the desk, including the reprint for the delegate who arrives without theirs, and the walk-in who is approved on the spot.

  • Pre-event set-up

    We build the registration form, import your list, configure approvals and templates, and have the event ready before the first invitation goes out.

  • Email and WhatsApp campaigns

    Invitations, confirmations and the reminder series written, scheduled and monitored for you, with the WhatsApp sender set up with Meta.

  • Devices at the venue

    Tablets and scanners brought, configured and tested against the venue network before the doors open.

  • After the event

    Attendance and delivery reports, the exports your finance and membership teams ask for, and the audit log handed over.

How an engagement works

Before, on the day, and after.

  1. 01 · Before

    You brief us; we set the event up

    The form, the list, the approval rules, the email and WhatsApp templates and the reminder schedule, built and tested against your event before anything goes out.

  2. 02 · On the day

    We run the desk

    Our people scan passes, manage the queue, print the reprints and decide the edge cases, while you watch arrivals live on the command centre.

  3. 03 · After

    You get the record

    Attendance and delivery reports, the exports your finance and membership teams ask for, and the audit log of who did what.

Software only is also fine: the platform is self-serve, the demo is public, and the how it works page is the manual.

Next step

Tell us the city, the dates and the size

We reply from a person, not a sequence, and we will say plainly whether this fits. Useful things to include:

  • Roughly when it happens, and roughly how many people.
  • Whether registration is open to anyone or invitation only.
  • Whether you want us at the venue on the day.
  • Whether it has to run on your own infrastructure, and in which country.

Send us the details

Only your email is required — everything else just saves us a round trip.

Only the email address is required. We use what you send to reply to you; it is not passed to anyone else.