Everything an event needs, working on its own or together

Eighteen parts of an event platform: event pages, registration, ticketing, check-in, badges, exhibitors, leads, meetings, programme, surveys, certificates and reports.

العربية

Plan

Before anyone arrives.

Event pagesA drag-and-drop page builder that produces your public event site — hero, agenda, speakers, sponsors, registration — on its own subdomain, in Arabic or English, with no build step and nobody to book.Registration formsDrag fields into place, add conditional logic, and get one attendee record that carries all the way to the badge, the door scan and the exhibitor’s lead card — with the same validation running on the server as in the browser.Tickets & paymentsTicket types, tiers, capacity and promo codes wired straight into your registration form — card payment or manual bank transfer with proof upload, refunds through the same adapter as the charge, and gateway credentials encrypted at rest.InvitationsPersonal invitations over WhatsApp and email with their own registration link, tracked from sent to opened to registered — so a VIP list is a working list rather than a spreadsheet somebody colours in by hand.Exhibitor applicationsA public application form, an approval queue, packages that decide entitlements, and a portal each exhibitor opens by magic link — so booth requirements stop living in a WhatsApp thread with forty companies in it.Floor planHalls, aisles and a booth grid at real dimensions, with companies dragged onto booths and colour following the package — and the same plan published to visitors so nobody maintains two versions of the floor.

Run

On the day itself.

Check-inScan a QR code from any phone and it resolves in under a second on the desk. When the network drops the queue is held on the device and syncs the moment the signal returns — because an exhibition hall is where wifi goes to die.Badges & print kioskA badge designer where every attendee type has its own template, so a speaker and a visitor print differently without anyone editing a file at midnight — and a kiosk that keeps printing when the network stutters.Lead captureBooth staff scan an attendee badge and the card opens already carrying the answers that attendee gave at registration — with your qualifier questions on every card, so what comes back is one comparable file rather than forty different ones.1:1 meetingsAttendees and exhibitor booths keep one diary each, slots are derived from real availability windows, and a meeting booked during registration is confirmed before anyone arrives — with one summary email rather than one per meeting.WhatsApp campaignsCampaigns on your own WhatsApp number with approved templates and its own dispatcher — scheduled in the venue’s clock, and built so a retried or overlapping run cannot message the same person twice.SeatingAssign seats and tables against real attendee records, let guests look up their own seat, and change a plan on the afternoon of the dinner without reprinting anything that matters.

Repeat

What you take to the next one.

Programme & sessionsSessions, speakers and tracks with attendee agendas, live polls and Q&A — and attendance recorded per session rather than per event, which is what makes every report after it worth reading.SurveysPost-event and per-session surveys sent only to the attendees who turned up, over WhatsApp and email, in the venue’s clock — so the response rate is worth something and the answers mean what they appear to mean.CertificatesAttendance-gated certificates issued from real per-session records — so the certificate you hand out means the person was in the room, and the accreditation body asking how you know has an answer.ReportsRegistration, attendance, order and lead reports read in the venue’s own clock — so the numbers you take to a sponsor or a board are the numbers the event actually produced, whoever opens the chart.Data exportCSV export of attendees, orders, leads, attendance and survey responses — plus per-person export and erasure for data requests, so the answer to "can we have the list" is a download rather than a project.Attendee historyOne tenant, many events, and an attendee record that carries what happened last time — so the third year of a conference starts from a real audience rather than an empty registration form.Webhooks & APIPoint evenclo at a URL you control and every registration, check-in, lead and survey answer is posted to it as it happens — signed, so your endpoint can prove it came from us.

Book a demo Thirty minutes, screen shared, in Arabic or English.