Skip to content

Winglark

How it works

One event, walked end to end.

A private view for four hundred people — invented for this page, and run below exactly as the product runs it. Nine stations, three minutes, no jargon.

Everything on this page is the demo event. Nothing is sent anywhere.

  1. Create
  2. Import
  3. Clean
  4. Design
  5. Send
  6. Respond
  7. Update
  8. Arrive
  9. Collect
  10. Report
01

Create

Start with the kind of event it is.

Pick a type and the form follows — a private view asks about the artist and the press list; a conference asks about tracks and rooms. Date, venue and capacity are entered once and every later step reads them from here.

Go deeperEvent types and the questions each one asks

The event record

Private view

An evening with the collection

Thursday 14 November · 19:00
Depo, Hall 2 · Istanbul
Reply by 7 November

What you were sent

  • Marta Ruiz, marta.ruiz@atlas.example
  • deniz aydın — deniz@aydin.example
  • Jonas Weber; j.weber@nord.example; +1
  • MARTA.RUIZ@atlas.example
  • Tom Kelleher tom@kelleher.exmple
02

Import

Bring the list you already have.

Paste rows from a spreadsheet, upload a CSV or Excel file, or type names in. Nothing is judged yet — this step just gets what you were sent into one place, exactly as it arrived.

Go deeperThe list check in detail

03

Clean

ListGuard

See what is wrong before anything goes out.

The import is read and every finding is reported with the original kept beside it — duplicates, undeliverable addresses, people who asked not to be written to. You decide; nothing is dropped quietly.

Go deeperThe list check in detail

Addresses are checked for a deliverable domain, not confirmed as real mailboxes. Winglark will not tell you an address is good; it will tell you when one cannot possibly be.

The list as it arrivedWhat the import found
An imported guest list, with what the import found
Marta Ruizmarta.ruiz@atlas.example
deniz aydındeniz@aydin.examplea name in one field
Jonas Weberj.weber@nord.example
Marta RuizMARTA.RUIZ@atlas.examplethe same person twice
Priya Ramanpriya@meridian.example
Tom Kellehertom@kelleher.exmplean address that cannot be delivered to
Sofia Lindqvistsofia@lindqvist.example
Aziz Karimaziz@karim.examplesomeone 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

04

Design

TemplateForge

Compose the invitation, publish a version.

The event’s real date, venue and deadline flow into the composition — they cannot be contradicted by a draft. Publishing cuts a version, and guests keep the version they were sent until you say otherwise.

Go deeperInvitation design in detail

Assisted compositionnot switched on yet

Drafts copy against the event’s real date, venue and deadline, and rejects anything that contradicts them.

What you start with
  • Private view, Thursday 14 November, 19:00
  • Depo, Hall 2 — Istanbul
  • Warm, quiet, not corporate. Reply by the 7th.
Private view

An evening with the collection

Thursday 14 November · 19:00Depo, Hall 2 · Istanbul
Reply by 7 November

Last pass: the title tightens and the rule lengthens. Small decisions, and the reason a person is still holding the file.

05

Send

MailFlow

Send it, and watch what actually happens.

Every message carries its own record: queued, accepted, delivered, opened — and held, with the reason. Email runs on your own verified address; SMS and WhatsApp go through your own account the same way.

Go deeperSending and delivery in detail

  1. queued24
  2. accepted24
  3. delivered22
  4. opened14
held2
  • 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.
Channels
  • Emailfrom your verified domain
  • SMSthrough your own account
  • WhatsAppthrough your own account

Sending runs on your own account and your own verified domain, so what leaves is under your name and your reputation.

06

Respond

Replies land on the same record.

Each guest opens a personal link to their own name and answers the questions this event actually asks. Answers can change until you close them, and silence is never quietly counted as a no.

  • Are you coming?
  • Bringing anyone?
  • Anything we should know?
  1. Marta Ruiz+1 · vegetariancoming
  2. Jonas Webercoming
  3. Priya Ramanupdatedcoming
  4. Sofia Lindqvist+1coming
  5. Rachel Oseideclined
  6. Elif Demirno nutscoming
invited
412
replied
338
expected, with plus-ones
396
no reply yet
74
07

Update

InvitePulse

Six more names, four days out.

A late list is compared with what the event already holds. Matches are left untouched — reply, plus-one and code intact — and only the genuinely new are prepared. Nobody is written to twice.

Go deeperAdding late guests in detail

437 already handled+3 genuinely newOnly these three receive the new invitation.
Already invitednot touched
  • Marta Ruizsame address
  • Jonas Webersame number
  • Priya Ramansame address
  • Sofia Lindqvistsame name, same company
  • Elif Demirsame address

437 people already on this event

Genuinely new
  • 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.

08

Arrive

GatePass

The door, on any phone.

The list is on the device before doors, so scanning works with no signal and syncs after. A second scan of the same code is flagged, never waved through — try it here.

Go deeperThe door in detail

At the door

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.

No rented terminals. The phone your team already has is the scanner.

Main door
20:14

Ready to scan

Point the camera at a guest’s code.

A working model of the door screen. Nothing here is sent anywhere.

09

Collect

TicketFlowactivated with our team

When a place is paid for, not invited to.

A paid order issues an entry code on the same guest record, and the same door admits it. Ticketing is switched on for a workspace with our team, so this station shows the shape of the flow rather than a live checkout.

Go deeperPaid attendance in detail

  1. 01A place is paid for at the checkout
  2. 02A credential is issued — a guest record like any other
  3. 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.

10

Report

What was promised, against what happened.

Because the list, the replies and the door are one record, the report is not a reconstruction — invited, replied, expected and actually arrived, with the gaps named and every figure of the demo event accounted for.

Reporting

invited412
said yes338
expected, with plus-ones396
actually came301
58said yes, never arrived
21came without replying
One event. Every figure measured against the same 412 invitations.
Invitations, replies, expected guests and real attendance for one event
invited412
said yes338
expected, with plus-ones396
actually came301
said yes, never arrived58
came without replying21

Now run a real one.

Your first event is free — fifty guests, real invitations, real replies, the same loop you just walked.

No card required. The Winglark mark stays on free invitations.

How event guest management works, end to end · Winglark