The platform
Your event does not live in an inbox. It lives in here.
Most agencies license event software and pass on the cost. We built ours, because the failures are almost always integration seams — a registration list that disagrees with the door, a rooming file the hotel cannot read, leads that arrive a fortnight late in the wrong shape.
Your own workspace, not a monthly status call
Progress, approvals and money in one place, with what is waiting on you at the top. An approval that is blocked behind an earlier one is not listed, because a queue full of things you cannot action is a queue people stop opening.
- Approvals, budget position and open requests, live
- Aggregate delegate status — 41 of 60 visas approved, never whose passport expires in March
- Raise a question, a change or a problem and get it priced in writing
- Gated behind a signed NDA before anything is shown
| Waiting on you | Status |
|---|---|
| Approve gala venue — Hall B | Today |
| Sign off delegate categories | In 2 days |
| Change request CR-014 — 40 extra rooms | Quoted |
| Production design v3 | Approved |
Committed against approved budgetUSD 612,400 / 690,000 | |
Same record, different view
Everybody works in the same place. Nobody sees the same thing.
A closed internal conference and a trade show are the same software and almost nothing else. Picking the event format switches on the modules that apply — visas and rooming for one, stands and hosted buyers for the other — and the switches then belong to the event rather than to the product.
Rules that are not negotiable
Six decisions we will not revisit.
These are the constraints the platform is built on. Each of them makes something slightly less convenient for us and considerably safer for you, which is generally how that trade should go.
Access is a credential, not a link
Every portal user gets a login ID and a key. The key is generated, hashed and handed straight to the mailer — we never see it and there is deliberately no way to reveal it, so "send again" mints a new one. One sign-in page routes each credential to the right portal, which means a six-hundred-person mailing carries one link and one instruction.
A module that is off refuses the request
Not hidden — refused. If an event does not run visas, the visa endpoint returns nothing at all. That also means somebody probing the system cannot map which modules a client runs.
Aggregate, never itemise, other people’s data
The client sees 41 of 60 visas approved. They never see whose passport expires in March. That distinction lives in the software rather than in whoever assembles the report — the response shape is the access policy.
Derived values are computed on write
Totals, margins, head counts, QR payloads and readiness scores are never taken from a request body, and one pricing function serves the proposal, the budget and the P&L — so the three cannot disagree with each other.
Identity documents are encrypted by us
Passports and visas are encrypted before they reach storage, not merely sitting on an encrypted disk. Every read is logged against a person, documents carry a retention date, and without the key upload is refused rather than falling back to storing the file in the clear.
Concurrency handled where it actually bites
Ticket tiers, session capacity, check-in re-scans and coach manifests. A badge scanned twice is not a second person, and a coach cannot be over-allocated because two people assigned at once.
The operating views
Each desk gets a shape, not a list.
Your own workspace, not a monthly status call
Progress, approvals and money in one place, with what is waiting on you at the top. An approval that is blocked behind an earlier one is not listed, because a queue full of things you cannot action is a queue people stop opening.
Six hundred delegates are eleven group fares, not one booking
The travel desk groups people by departure city, because that is how the money and the risk actually behave. Ticketed, held and unassigned are separate states, and arrival waves drive the transfer plan.
Which of these people would not board today?
The visa desk ranks by risk, not by status count. Passport validity, missing documents and no appointment are the three things that stop a delegate at the gate, so they sit at the top of the list as a call sheet.
Hard rules never traded, soft rules scored, the rest left for a human
Rooming is where automation usually embarrasses everybody. Ours shows its reasoning, refuses to break a hard rule to improve a score, and leaves genuinely unmatched people unmatched rather than guessing.
Exhibitors do not buy a stand, they buy conversations
Floorplan, stand allocation, exhibitor manual and a matchmaking engine that fills toward each hosted buyer’s quota rather than maximising a total score — and reports who is short, because that list is a set of phone calls.
Alerts first, counters second
On show days the board answers one question — where is everybody right now. Check-in is idempotent, so a re-scan is not a second person. The close-out report that follows includes the incidents and the budget variance on purpose.
Honest limits
What it does not do yet.
Every platform page on the internet lists features. Here is the other half, because you will find out anyway and it is better you hear it now.
Read more
The standards behind it.
Access is a credential, not a link
A login ID and a key that we never see — generated, hashed and handed to the mailer. There is deliberately no way to reveal it, so "send again" mints a new one.
Aggregate, never itemise, other people’s data
The client sees that 41 of 60 visas are approved. They do not see whose passport expires in March. The response shape is the access policy, not a template decision.
A module that is off refuses the request
Not merely hidden. If an event does not run visas, the visa endpoint returns nothing at all — so a probe cannot map what a client runs either.
Identity documents are encrypted by us
Passports and visas are encrypted before they reach storage, every read is logged against a person, and they are purged on a retention date. Without the key, upload is refused rather than stored in the clear.
One working day · hello@voyacircle.com
Want to see it with your event in it? Send the brief.
We will configure a sandbox event with your formats, categories and approval rules so you can walk the client view and the delegate view before deciding anything.