event67 for organizers
For the person running the event, event67 is a console and an app that share one attendee list. You build the programme, invite your list, moderate what attendees post, publish changes when the day moves, and watch arrivals and engagement while there is still time to act on them.
Your day with event67
Six weeks out
The programme goes in
Sessions, tracks, rooms, speakers and sponsors, entered once in the console. Speakers are records rather than text on a session, so a bio written once appears everywhere that speaker does.
Four weeks out
The theme, and the contrast conversation
Logo, colours and typography, previewed live. The contrast check tells you when a brand pair falls below WCAG AA and asks you to confirm. Frequently this is the moment the brand team learns their light grey is unreadable at arm's length.
Three weeks out
Invites go out and the meter starts
CSV import, invites sent, delivery tracked per recipient. Invites are unlimited and free. The bill starts moving only when someone claims an invite and opens the app, and you can watch that number climb in the console rather than learn it afterwards.
The day before
You brief the volunteers
Per-event moderator roles for the people on the approvals queue, so nobody who is here for two days is holding access to your attendee list or your billing.
08:30 on day one
The door
Any phone with a camera and a login is a scanner. Arrivals run against the invited list live, which is how you decide whether to hold the keynote for ten minutes or start on time.
11:00, when it changes
You move a room and tell everyone
Edit the session and every attendee's view updates, including the pinned copy in their own agenda. Then send an announcement, because a silent update is one nobody notices.
Lunchtime
You read the funnel, not the total
Invited, activated, engaged. Each step is a different problem: a low activation rate the afternoon of day one is fixed by an email that evening, and it works.
48 hours after
The bill arrives, after the amount does
Charging runs two days after the event ends, and the amount is emailed before any card is touched. Nothing about the invoice should be new information by then.
What you control
- Who on your team has what
- Platform staff, organisation super-admin, organisation admin and per-event moderator. A volunteer gets one event and the moderation work in it, and scope is the real control, because moderation actions are not attributed to a person.
- Which features exist for this event
- Photos, Q&A, polls, chat, the directory and connections are per-event switches. A board offsite and a user conference are the same product with different answers.
- What reaches the room
- Nothing appears on a stage screen or in the album without a moderator approving it, if you have set moderation that way. A reported photo hides immediately and waits for a person.
- When things are said
- Announcements publish now or on a schedule, and the queue is editable until it fires.
- What it costs
- The meter is visible from the day the event is published. Activation, not registration, not invitation, is what bills.
What you never have to do
- Reconcile two attendee lists. Email campaigns send to the event's list, not to an export of it.
- Wait for a build. Content and theme are served from the backend, so a change at eleven at night is live at eleven at night.
- Guess the bill. Activation is both the engagement metric and the billing meter, and the amount is emailed before a card is charged.
- Approve four hundred photos personally, if you have volunteers and the sense to give them a moderator role.
- Pay for invites. They are unlimited and free, and someone who never opens the app never costs anything.
What you still need other tools for
event67 runs the attendee experience and the organiser's side of it. It is not an event management suite and a demo that implies otherwise wastes your afternoon.
- Registration and ticketing. No sales, no payments, no ticket types. Keep the registration platform you have and import from it.
- Badge printing and onsite walk-up registration.
- Budgets, contracts, supplier and venue management.
- Call for papers, abstract review and speaker portals.
- Continuing-education credit tracking and certificates.
- Streaming, hybrid sessions and on-demand video.
- Exhibitor lead retrieval, floor plans and wayfinding.
- Integrations. There is no public API and no webhook catalogue.
If three of those are on your requirements list, event67 is the wrong shortlist entry and finding that out here saves everybody a call.
The team this assumes
The console is built for a small team where most people are not power users. The producer is in it daily. The communications person sends four emails. Two volunteers work the approvals queue for two days a year and were briefed for ten minutes. The finance contact opens Billing twice.
That mix is why the live pages are responsive and glanceable rather than dense: they are used standing up, at the back of a hall, by somebody who is also dealing with something else.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
What exactly are we billed for?
Activated attendees: people who claimed their invite and opened the app. Not imports, not invitations, not registrations, and not people who were scanned at the door but never opened anything. The first 50 on an event are free, each one after is $5, and one event never exceeds $4,750.
Can we change the schedule mid-event?
Yes, and it is the main reason to have the schedule in an app. Editing a session updates every attendee's view including the copy pinned in their own agenda. For a same-day change, send an announcement as well, because a silent update goes unnoticed.
How do we give volunteers access without giving them everything?
Per-event moderator roles. Scoped to one event and to the moderation work, with no reach into the attendee list, billing or your other events. Admin chat and billing write an audit record; moderation and check-in do not, so agree the rules with your volunteers rather than relying on a log.
Does event67 replace our registration system?
No. There is no registration, ticketing or payment anywhere in the product. Your registration platform stays and you import the resulting list by CSV.
When are we charged?
48 hours after the event ends, never before, and the amount is emailed before any card is charged. A live meter runs in the console from the day the event is published, so the number should not be a surprise.
Keep reading
What you run it from
Event types organizers run most
Run one and see
The first 50 attendees on an event are free, so a first event under that costs nothing at all.