Capabilities
Eight problems, taken off your desk.
Every event breaks in the same places — the list, the invitation, the sending, the door, the numbers at the end. Winglark’s guest management covers each of them; every section below starts from one of those breaks and shows, working, what it does about it.
Each one also has a page of its own
Clean the list
ListGuardMy guest list is a mess
Paste it in as it is. See what is wrong before anyone else does.
The import reads what you were sent and reports what it found — the same person twice, addresses nothing can deliver to, people who asked to be left alone, rows with half a name. Every finding is a proposal with the original kept next to it; nothing is rewritten quietly and nothing is dropped without you seeing it.
What comes out is one list you can trust enough to send to.
| Marta Ruizmarta.ruiz@atlas.example | |
| deniz aydındeniz@aydin.example | a name in one field |
| Jonas Weberj.weber@nord.example | |
| Marta RuizMARTA.RUIZ@atlas.example | the same person twice |
| Priya Ramanpriya@meridian.example | |
| Tom Kellehertom@kelleher.exmple | an address that cannot be delivered to |
| Sofia Lindqvistsofia@lindqvist.example | |
| Aziz Karimaziz@karim.example | someone who asked not to be written to |
| Elif Demirelif.demir@atlas.example | |
| Rachel Oseir.osei@harbour.example |
7 will be invited3 wait for a person
Create the invitation
TemplateForgeI need an invitation, and it has to look right
From a brief to a finished invitation, version by version.
Start from the brief, arrange the composition, publish a version. An event points at the version you published, so a later edit never rewrites the invitation a guest is already holding — the change waits until you say so.
Drafts copy against the event’s real date, venue and deadline, and rejects anything that contradicts them.
- Private view, Thursday 14 November, 19:00
- Depo, Hall 2 — Istanbul
- Warm, quiet, not corporate. Reply by the 7th.
An evening with the collection
Last pass: the title tightens and the rule lengthens. Small decisions, and the reason a person is still holding the file.
Reach people
MailFlowI have to reach everyone, and know it worked
Every message keeps its own record.
What left, what the provider accepted, what arrived, what came back, and what was never attempted — with the reason held beside it. A permanently bounced address is not retried; a person who said no is not written to, and that answer does not expire.
- queued24
- accepted24
- delivered22
- opened14
- This address bounced permanently the last time — sending again would damage the domain.
- This person asked not to be written to. That answer does not expire.
- Emailfrom your verified domain
- SMSthrough your own account
- WhatsAppthrough your own account
Email runs on your own account and your own verified address, so what leaves is under your name. SMS and WhatsApp go through your own account in the same way, with consent and credits kept beside every message.
Handle late additions
InvitePulseNames keep arriving after the invitations went out
Only the genuinely new are prepared.
The new list is compared with what the event already holds. A match on address, on number, or on name and company is left exactly as it was — reply, plus-one, code and all. Only the rest are prepared for sending, and you see the split before anything moves.
- Marta Ruizsame address
- Jonas Webersame number
- Priya Ramansame address
- Sofia Lindqvistsame name, same company
- Elif Demirsame address
437 people already on this event
- Nils Bergström
- Amara Okoye
- Théo Marchand
Nobody is written to twice, no guest is duplicated, and nobody’s existing reply is disturbed. The people already handled stay handled.
Run the door
GatePassThe door is where it all falls apart
A phone, a code, a decision — with or without signal.
Every device downloads the list ahead of time and keeps admitting offline; when the connection returns, the server re-checks each queued scan rather than trusting the phone. A second scan of the same code is flagged, never waved through — refusal, re-entry or a recorded override, and each ends up in the report.
Door check-in is a paid upgrade on an event, or part of a Professional plan. It is not included in the free first event. Pricing
Try the second scan yourself:
No rented terminals. The phone your team already has is the scanner.
Ready to scan
—
Point the camera at a guest’s code.
A working model of the door screen. Nothing here is sent anywhere.
Collect before the door
TicketFlowactivated with our teamSome guests should be paying
A paid place that ends at the same door.
Ticket types live on the same event as the invited guests. A paid order becomes a guest record with an ordinary entry code, the same door admits it, and a refund revokes it. One list, paid and invited together, one report at the end.
- 01A place is paid for at the checkout
- 02A credential is issued — a guest record like any other
- 03The same door admits it, online or off
Switched on for a workspace with our team: currency, refund policy and payment set-up are configured with you before the first sale.
Understand what happened
I never find out who actually came
The distance between said-yes and showed-up.
Invitations, replies, expected guests and real scans are one record, so the report is not a reconstruction from three exports — it is what the list and the door already knew. Delivery against sending, attendance against every RSVP answer, plus-ones expected against plus-ones arrived.
| invited | 412 |
|---|---|
| said yes | 338 |
| expected, with plus-ones | 396 |
| actually came | 301 |
| said yes, never arrived | 58 |
| came without replying | 21 |
Run it for clients
I run this for clients — several at once
A workspace per client. A wall between them.
Each client is a workspace of its own: its own guest data, its own brand on every invitation and door screen, its own report to hand over at the end. Roles give each person the narrowest access that does their job, and the month rolls up to one invoice.
- Owner
- Producer
- Door staff
- Owner
- Producer
- Door staff
- Owner
- Producer
- Door staff
Separation is enforced on the server, not in the interface — door staff in one workspace cannot read another workspace’s list, whatever their screen does.
Your first event is free.
Fifty guests, real invitations, real replies. Not a tour of a demo — a small event, run properly, from the list to the report.
No card required. The Winglark mark stays on free invitations.
Questions
Is Winglark an event management platform?
It is the guest side of one: the list, the invitations, the replies, the door and the attendance report — and, where an event needs it, paid places through ticketing that is switched on with our team. It does not plan budgets or manage venues.
Do I need all six capabilities?
No. Each works on its own; they share one guest record, so using more of them means less re-entering. A first event with a list, invitations and replies is free.
Which one handles check-in?
GatePass: a QR code for each guest, any phone as the scanner, several doors, walk-ins and re-entry, and check-in that keeps working without signal.
Can guests be added after invitations have been sent?
Yes — that is InvitePulse. New names are matched against the event, and only the genuinely new ones are invited; nobody is written to twice.