Questions, answered in one place.

It runs an event through its guests: the list, the invitations and replies, the door, the evening on every guest’s phone with its programme, live questions, photos and sponsors, then the follow-up and the report. Paid places use ticketing switched on with our team. It does not plan budgets or manage venues.

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, and each plan says which products it includes.

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.

Yes — that is InvitePulse. New names are matched against the event, and only the genuinely new ones are invited; nobody is written to twice.

Their own page in the browser — Companion: the pass for the door, the programme, the map and live updates, in their language, with no app to install. Polls, photos and messages open from the same page.

Yes — real invitations, real replies, up to fifty guests, and the guest app on the evening. It is one free event per person, not per workspace, and what it does not include — the door, networking, sponsors and a team — is listed above before you sign up.

No. The guest app, live polls, the Event Control Room and the follow-ups afterwards are on every plan, the free event included. What grows with the plan is how much of them one event can use, and whether networking, sponsors and the venue code are part of it.

You are told where it happens — when you add the guest, the room or the sponsor that would pass it — together with the plan that has more. Nothing already running at the event stops, and nothing you collected is removed.

Not yet. Winglark is in early access and plans are opened by request. Ask for access to the plan you have in mind and we will email you when billing opens. The free event does not depend on any of this.

No. Early access opens the product, not a subscription. Nothing is charged until billing opens, and we will write to you before it does.

US dollars, for every plan and both intervals.

Both exist for every plan. The annual price is ten months, so a year costs two months less — and the interval only changes how often you pay, never what is included.

It stays in your account with its guest list, its photos and its report. Nothing expires and nothing is deleted unless you delete it.

At any time, on any plan including the free one — CSV and Excel for the rows, PDF for a summary you can hand over.

Client firms without a ceiling, each with its own events and records kept apart, the highest number on every line above, the largest sponsor programmes, and guest moments without Winglark’s line on the wall and the prints.

Seven: organisation owner, manager, marketing, guest manager, door staff, report viewer and partner staff — each with the access its job needs and no more. Door staff see the scanner and nothing else.

Yes. A role is assigned for one event or for the whole organisation, and door staff can be given limited, time-bound access for a device.

The Agency plan gives a workspace per client, with the data separated on the server. Partner staff see only the event and the door they are given.

Yes. Every privileged action is recorded with the name of the person who did it — including every admission at the door.

Yes. Each stand has a console of its own for its lead and staff. They see only their own sponsor’s visitors and the contacts guests agreed to share with that sponsor — never your guest list, other stands or your settings.

Yes. Invitations are sent under a verified sender on your own domain and designed from blocks with your logo. On the Agency plan the Winglark mark is removed from what guests see.

Tag them as segments on the list. Segments carry into the replies, the door screen and the report, and each door has its own assigned staff — the VIP entrance worked by somebody who knows the faces.

Seven roles. Door staff see only the scanner; a guest manager sees the list and the invitations but not billing; a report viewer reads and exports only; partner staff see only their assigned client.

A staff member with the right can add them at the door, and the record shows who did it. A doubtful case can be admitted with a supervisor’s approval, which is recorded with a name and a reason.

The security page states how data is protected and what is not in place yet. Every report exports to CSV, Excel or PDF at any time, on every plan.

It runs an event through its guests: the list, the invitations, the replies, the door, the evening on every guest’s phone — programme, live questions, photos, sponsors — the follow-up and the attendance report, with paid places through ticketing switched on with our team. It does not plan budgets or manage venues.

Invitation-only events of any size — corporate events, conferences, launches, galas, private views, weddings — where there is a guest list before there is anything else. Twenty-five event types, each with its own fields and reports.

No. A guest receives an invitation with their own link and, if the door is on, their own QR code. They reply in a browser and show the code on a phone or on paper.

Yes. Seven roles — owner, manager, marketing, guest manager, door staff, report viewer and partner staff — each with the access its job needs. An agency gets a workspace per client, with the data separated on the server.

The first event is free: fifty guests, real invitations, real replies, no card. Plans are opened by request while Winglark is in early access.

No. They scan with their phone camera, write their first name and email, tick one box and press one button.

Yes. It belongs to your organisation, not to an event, and keeps working until you regenerate it — which you would only do if a printed code was misused.

A person is on your list only after pressing the link we email them. It is the default because it proves the address is theirs. You can switch to single-step joining in settings.

Yes, as CSV, after confirming that these people agreed to hear from you. Anybody who previously left your audience stays left.

No — and that is the point. They can rejoin themselves from the link in any message they received, or by scanning and confirming again.

No. Winglark sends only what your organisation sends — confirmations, and the invitations you choose to send.

Not today. A person can tell you they would accept texts, and that preference is recorded, but nothing is sent by SMS from AudiencePass.

A code made for one event counts everyone who used it. A permanent code counts a scan only when exactly one of your in-person events was running at that moment. When it is not certain, nothing is attributed.

No. It checks the format, flags disposable and role addresses, and looks up whether the domain accepts mail. Whether a particular mailbox exists is only known when a message is delivered — and delivery is recorded for every message afterwards.

No. Proposed corrections sit beside the original value, and you accept them one by one or all the safe ones at once. Nothing is committed until you commit it.

One upload can be up to 6 MB and 10,000 rows. A larger list can be brought in several parts.

Before it is committed, an import can be discarded completely. After it is committed, guests can be archived and restored one at a time.

No. Invitations are composed from blocks so that they render reliably in mail programs. That is a deliberate limit rather than a missing feature.

Nothing. Published versions are fixed. Your edit becomes a new draft, and guests only see it once you publish it and assign it to the event.

Yes, on the Professional and Agency plans. It creates backgrounds and illustrations and drafts invitation copy; each draft is checked against the event’s date, time and venue, which you keep editing in the event itself. Access is part of the plan rather than a monthly credit balance, and Starter does not include it.

A test goes to you, writes nothing to your guest list or your statistics, and carries a test pass the door will not admit.

No. Winglark sends through its delivery provider. You can begin with the Winglark address, shown with your company’s name, and move to your own verified domain whenever you choose.

That the receiving mail server accepted the message, as reported by the delivery provider. Opens are recorded where the recipient’s mail program allows it, and are never guaranteed.

Yes, to one guest at a time, from their record. A new message is created, so the history of the first one is kept.

Email is the channel in use today. Consent and credits for other channels are already recorded, and those channels run through your own account when they are switched on.

Likely matches — a similar name at the same company, the same phone number — are marked for review rather than added, so the decision is yours.

No. Adding and sending are separate steps. New guests are prepared, and their invitations leave when you send them.

The event’s guest limit applies. Names beyond it are shown as blocked, with that reason, rather than silently dropped.

Yes — staff allowed to do so can add a walk-in at the door. This is for everyone you know about before then.

Coming, not coming, undecided and no answer. The last is kept deliberately: silence is data, and it is never counted as a refusal.

Yes. The latest reply counts and the earlier ones stay in the record, so you can see who changed their mind and when.

An allowance is set per guest. Each plus-one is named, counted, can answer the same questions, and gets a code of their own if the door is on — or the guest’s code carries the group and the door counts who arrived.

Each event type brings the questions it usually needs — meal choice, allergies, transfer, session, attendance mode — and a free note field for anything else.

They stay “no answer”, a reminder can go to them before the event, and if they turn up anyway the door records them among those who came without replying.

No. Ticketing is switched on for your workspace by the Winglark team after a short conversation about the event, the currency and the commercial model. Contact Sales from this page and we set it up with you.

Because the set-up is commercial as well as technical: currency, pricing, refund policy, commission and settlement have to be agreed before the first sale. Doing that with you, once, is faster than a form that guesses.

Yes. A paid ticket is fulfilled as an ordinary guest record with an ordinary entry code, so the door scans it like any invitation — online or offline. A refunded ticket is revoked, and the door refuses it.

Yes, two ways: a ticket type priced at zero goes through the sales page without a payment step, or the guest is simply invited and never sees a checkout. Both end on the same list.

At the checkout, on the event’s sales page, before the event. Their places are held for fifteen minutes while they pay; the confirmation and the entry code follow once the order is paid and fulfilled.

Full-order refunds, yes: the money is returned through the payment provider and the tickets are revoked once it has been. Partial refunds are not offered.

One currency per event, from those the payment provider supports — confirmed during activation. Cards are handled by the provider on its own hosted checkout; Winglark never sees card details.

Yes. Ticketing runs inside a client’s workspace with the same roles and the same separation as the rest of Winglark, and each client’s sales stay in that client’s workspace.

It is not a line on a plan. Availability and commercial terms — commission, settlement, the plans it runs alongside — are confirmed during activation.

No. They show the code from their invitation, on their phone or on paper.

It keeps scanning against the guest list it holds. When it reconnects, the server checks every admission again; the first admission to reach the server counts, and any conflict is shown to you.

Nothing about the guest. It carries an opaque token — no name, no email, no event.

No. Check-in at the door is part of the paid plans, or a paid upgrade on a single event.

No. They show the QR code from their invitation, on a phone or on paper, and a staff member’s phone is the scanner — nothing to rent, charge or install.

Yes. Each device holds the guest list and scans against it while offline; admissions are queued and sent when the connection returns, and a conflict between two devices is shown to you rather than resolved silently.

The screen says so, with the time, the door and the staff member of the first scan. Staff choose: refuse, record a re-entry, or admit with a supervisor’s approval — and each choice is recorded separately in the report.

Yes, if the staff member has the right to add guests at the door. The person is added there and then, marked as added at the door, and appears in the report among those who came without replying.

Yes. An event can have several doors, each with several devices, each tied to a named staff member. A code scanned at one door shows as scanned at the others in real time.

No. Companion is a web page. A guest taps the button on their invitation or scans a code in the room and it opens in the phone’s browser. There is nothing to install and no account to create.

The personal link belongs to one guest: it greets them by name, carries their entry pass while door check-in is active, and remembers their questions. The open link is the same for everybody in the room and is anonymous — it offers polls, questions, reactions and updates, but never a pass.

No. Updates appear on the page while it is open — a new announcement or poll arrives without reloading. Nothing is sent to the phone when the page is closed.

No. The Info tab shows only what the organiser wrote: the venue, the times, a note and their own questions and answers.

The page keeps showing what it last loaded, says when it was last updated, and reconnects by itself when the signal returns.

Yes, when the organiser has MomentFlow on for the event: the page links straight to the event’s photo and video upload.

No. The programme is in the event page they open from their invitation or from the QR code in the room. Their day is kept for that link or that phone.

Adding it is refused with “full”. A seat frees when someone removes the session from their day. There is no waitlist.

You see how many added it, how many hold a seat, and the headcount your team entered for the room. There is no turnstile per room.

Yes. Internal sessions stay in your programme and never reach a guest.

Guests’ phones pick up the change within seconds. A cancelled session disappears from everyone’s day.

No. A guest appears to others only after writing a profile and choosing to be visible. They can hide or leave at any time.

No. It counts what both people supplied — topics, goals, sessions, languages, free time — and shows the reasons. Nothing is inferred from behaviour.

No. Organisers see counts only. Notes are visible to the two guests involved.

No. Networking needs the guest’s own invitation link, so everyone you can meet was invited to the event.

It suggests a time, often a free window you share. The other guest accepts or declines; nothing is booked anywhere else.

No. They answer from Companion, the event’s page on their phone, opened from their invitation or from a QR code in the room.

No. Each phone can answer a poll once; a second tap keeps the first answer. Each phone can upvote a question once.

No — a poll takes one answer per phone. For a broader question, run two short polls one after the other.

Only the organising team. Nothing reaches the room’s list or the screen until somebody approves it.

A browser on the television, projector or laptop at the front. Open the screen link and choose full screen.

No. While the event runs, results are seen in the event’s live section and on the screen; the event report covers invitations, replies and arrivals.

No. They scan a QR code with their phone’s camera and send from the page that opens. There is nothing to install and nothing to sign up for.

No. Every moment waits in your media library until someone on your team approves it. Only approved moments can reach the Live Wall or a gallery.

Yes. Videos are accepted with a poster frame taken from each clip, and HEIC photos are converted in the guest’s browser before they are sent.

Two separate things. Keeping the moment in the event’s collection is required to send it. Promotional use is a second, optional choice that is unticked unless the guest ticks it. Both answers are stored with the moment.

Yes. Every guest receives a private receipt link listing what they sent, and can take any of it back from there.

No. MomentFlow has no automated moderation and no AI features. What is shown is decided by the people on your team.

In private object storage in the EU (Frankfurt). Links to files are signed and expire, and photos shown on the wall or in a gallery are re-rendered without location or camera data.

You choose: until the event ends, for up to seven days afterwards, until a date you set, or until you close it yourself.

Yes. You can export the original files as a ZIP — all of them, or just a selection or a collection.

No. They open their event page from the invitation or the QR code at the venue and leave a message in the browser.

Your team, with the right to see the event’s memories. Nobody else, unless the guest allowed it and you approved it.

No. You can type or correct a transcript next to each recording. Automatic transcripts are not switched on.

A voice note up to three minutes, a video up to ninety seconds, a text up to a thousand characters.

Yes, from their own phone, at any time. The recording is removed.

No. The code opens their event page in the browser and adds the place.

Each place counts once, scans are slowed when they come too fast, and a copied code can be replaced in one action. A visit always needs the code that hangs at the place.

No. The organiser sees totals by place and how many completed — not anyone’s route.

Winglark records who is eligible and gives them a code. Handing the reward over is the organiser’s.

Pause it: it leaves the journey, and nobody’s progress is lost.

Inside each event in the Winglark app, under the event’s Live section. It is for one event at a time.

From GatePass check-ins at the door, set against the guests who replied yes with their party sizes. Without door check-in for the event, the arrivals block is not shown.

No. Door staff keep their own door view. Owners and managers run the control room, guest managers can operate polls, questions and announcements, and marketing can view it.

Yes. It is a page in the browser and reflows for a tablet or a phone.

No. The event report covers invitations, replies and arrivals; poll and question results are seen live, in the event’s live section.

No. It suggests and drafts. A person approves each follow-up and chooses when it goes.

Then attendance is not known, and there is no “we missed you” audience. You can still thank everyone who replied yes.

Yes. Leave it empty for the template in each guest’s language, or write your own — it goes to everyone as written.

No. The check happens at the moment of sending, with the same rule as every other Winglark send.

No. Results show what was sent, delivered, bounced and answered — and the feedback guests gave.

Invitations (sent, delivered, opened), replies (coming, not coming, undecided, no answer), attendance (who checked in, by name) and the door itself: re-entries, repeated scans, supervisor approvals, and arrival times by door and staff member — and beyond the door: poll results, session attendance, visits per place on the venue route, and each sponsor’s report with the leads guests agreed to share.

The difference between who said they would come and who was actually scanned in — by name in both directions: those who promised and did not come, and those who came without replying.

Yes, on every plan including the free event: CSV for the raw rows, Excel with formatted sheets, PDF for a summary you can hand to a client.

Yes. An event stays in your account with its guest list and its report; nothing expires and nothing is deleted unless you delete it.

No. A door pass is for the door. A lead exists only when the participant shares from their own phone, with one named sponsor.

Name, email, company and job title. A guest on their own link sees what their invitation holds before agreeing and can correct the company and title; on the event’s open link they type it.

No. The organiser sees counts per sponsor. The leads and the booth’s notes belong to the sponsor.

No. It is counted as a visit for that sponsor and nothing more.

No. Winglark counts what happened at the stand. It does not know what a lead was worth, so it does not invent a figure.

No. Every lookup is made against the workspace that owns the record, so a record from another organisation behaves as if it does not exist. Agencies can also keep each client’s data apart, enforced on the server, and these boundaries are verified by automated tests before release.

Guest data is encrypted in transit and at rest and stored in the EU. Contact details are masked for team members without permission to see them, sensitive answers are limited to the roles that need them, and exports with personal data require a reason and are recorded. Invitation links and door codes carry no personal information.

Sign in with Google (OAuth 2.0 with PKCE) or with an email address and a password hashed with Argon2id. Multi-factor authentication and enterprise single sign-on such as SAML are not offered at this time.

Each member has a role with a defined set of permissions — from owner to reporter and door staff. Contact details and sensitive answers follow those permissions, and door staff only ever see the door screen.

Invitation links carry 256 bits of unguessable value and QR passes are generated with a server-side secret key. Both are stored only as keyed digests, checked on our servers, and a pass admits its guest once.

In the European Union: the application runs in Frankfurt and the production database is hosted in the EU. Some subprocessors, such as email delivery and AI Studio’s provider, may process data outside the EU; the subprocessors page lists each one.

No. AI Studio sends only event details and your own instructions to its provider, and only when you use it.

The people who built Winglark investigate directly: contain the issue, restore service and inform affected customers using the contact details on their workspace. We do not publish contractual response or recovery times.

Yes. Our database provider keeps a continuous history of the production database, and Winglark maintains a documented procedure for restoring from it.

Not at this time, and no independent penetration test has been commissioned yet. Our security controls are documented control by control against the code and tests that implement them, and we walk security teams through them during an assessment.

Yes. We answer security questionnaires and offer an architecture walkthrough with the people who built the system. Use the contact page and mention your assessment.

The guest fields, the RSVP questions and the reports. A conference asks about sessions and attendance mode; a wedding about meals, transfers and the table plan; a private view about the artist, the visit time and press.

Choose “Other”: the same guest list, invitations, door and reports, without the type-specific fields.

Yes. The plus-one allowance is set per guest — none, one, several or open — and each plus-one is counted, can answer the questions, and gets a code of their own if the door is on.

Yes. The latest reply counts and the earlier ones stay in the record. Silence is kept as its own state — “no answer” is never counted as “no”.

Yes, if you allow it. You set the allowance — none, one or several — for everyone or for the guests you choose, and every companion is counted in the expected headcount.

No. They open the invitation, answer, and can come back later to change their reply from the same link, unless you have closed changes.

Yes. Upload a picture, choose how it sits on the design, and see the result before anything is sent.

Yes. A children’s birthday asks how many children are coming and how many adults are staying, and its allergy question is required rather than optional.

The reply already asks how many children and how many adults are coming, so a separate companion allowance usually double-counts. You can still switch plus-ones on for everyone or for chosen guests.

Yes. It is suggested as optional, and you can make it required, reword it or remove it before sending, like every suggested question.

No. They open the invitation, answer and can come back to change the reply from the same link until you close changes.

Yes. The invitation email and the reply page appear in each guest’s language — English, Turkish, German, French or Spanish — while the words you wrote stay as you wrote them.

Yes. A birthday suggests one optional allergy question; a children’s birthday asks for children and adults separately and makes the allergy question required.

Yes. The suggested question asks how many seats they need, and you can also allow plus-ones so companions are named and counted.

Yes. You set the plus-one allowance — none, one or several — for everyone or for the guests you choose.

Add both to the running order with their own times and locations, and the guest page shows each part of the day.

No. They open the invitation, answer, and can change their reply later from the same link until you close changes.

Yes. The reply page asks which parts each guest is coming to — the ceremony, the reception or both — and every answer is in the reply export.

Each reply’s meal choice and allergies go into the reply export, a CSV or Excel file you can send straight to the kitchen.

Only the new guests receive the invitation. People who already have it are not sent a second copy.

Yes. The door keeps working offline and catches up once the connection returns.

Yes. The suggested question starts with meat, fish and vegetarian; you can add options, reword them or make the question required.

No. They open the invitation, answer, and can change their reply later from the same link until you close changes.

Yes. Save the guest list after the engagement and use it again when the wedding invitations go out.

Yes. Door check-in keeps working offline and catches up once the connection returns. It is a paid option, on the plans that include it or as an upgrade for a single event.

Yes. Guests reply to the organiser through their own link, and the parents-to-be receive nothing unless you add them to the list.

Yes. Add a question of your own — a short answer, a choice or a yes or no — and every answer appears in the reply export.

No. They open the invitation, answer, and can change the reply later from the same link until you close changes.

Plus-ones start switched on for a baby shower, and you decide the allowance — none, one or several — for everyone or for chosen guests.

Yes. The slots are a suggested question: rename them, add a later slot, or remove the question entirely. The attendance question is always asked.

They start switched on for exhibitions, one per guest, because visitors often bring someone. You can switch them off for the event.

Each guest has one reply they can change until replies close. The new answer replaces the old one and the change is kept, so your numbers stay current.

Yes. A private view suggests one question, whether a guest is attending as press; an exhibition adds visit-time slots and asks which works a guest would like to see.

No. Door check-in is a paid option, included in the plans that have it or added to a single event. Without it you still have every reply and the export.

Yes. A private view suggests a reply question asking whether a guest is attending as press; an exhibition suggests visit-time slots and asks which works a guest would like to see.

Yes. Place the work as a full background, or as a framed image that is shown whole and never cropped, and keep the words to a few lines.

No. The door is optional. Without it you still have the replies; with it you also know who arrived and when.

A private view suggests one reply question, whether a guest is attending as press. An exhibition also offers visit-time slots and asks which works a guest would like to see.

Yes, by default for private views, one per guest. Switch them off if the invitation is strictly for one person.

Each link belongs to one guest and carries that guest’s one reply. With door check-in, each pass admits once, so a forwarded pass does not bring in two people.

Yes. The invitation email and the reply page appear in English, Turkish, German, French or Spanish to suit the guest; the words you wrote stay exactly as written.

It is a paid option: included in the plans that have it, or added to a single event. Without it, your list still does the job at the door.

Paid places are activated with our team for eligible Agency members, on request. Invitations, replies and check-in work without it.

Each pass admits once. If guests need entry on several days, set up each day as its own event and invite guests to the days they chose.

Yes, with door check-in. Several phones scan at the same time, and every scan joins one count.

Yes. It starts as required, and you can make it optional, change the days, or remove it. The attendance question is always asked.

It is a paid option: included in the plans that have it, or added to a single event.

Yes. Set the event as hybrid, add the joining link, and ask each guest whether they attend in person or online. Remote attendees see the link on their guest page once the room is open.

A suggested reply question asks whether they have anything to add. Their answers appear with their reply and in the export, and you decide what goes on the running order.

Yes. Mark people by guest type — standard, VIP, speaker, staff and others — and filter the list and the invitations by type. Nobody needs an account to reply.

Most meetings do not. It is a paid option, included in the plans that have it or added to a single event, and useful for larger sessions or a building with a reception desk.

Paid places are activated with our team for eligible Agency members, on request. Invitations, replies and check-in work without it.

Yes, with door check-in. Several doors and rooms scan at once on ordinary phones, and all of them feed one live count.

They are off by default for conferences, because each delegate is invited by name. You can allow them if your event needs it.

Yes. They arrive as suggested questions; you decide whether each one is required, and you can add questions of your own.

Plus-ones are off by default for business events, because each guest is invited by name. You can switch them on for the event if you want colleagues to come along.

Filter the list to those who have not replied and send the invitation again. It uses the same link, and answers already given are not touched.

Paid places are activated with our team for eligible Agency members, on request. Invitations, replies and check-in work without them.

No. The badge name each guest gives comes out in the replies export, so your printer or badge supplier works from the names people actually chose.

Department arrives as a required suggested question. You can keep it required, make it optional, reword it or remove it.

Plus-ones are off by default for corporate events. For a family day or an evening with partners, switch them on for that event.

Filter the list to guests with no reply and send the invitation again. It is the same link, and the answers others have given stay untouched.

No. It keeps the record: with door check-in, the attendance export lists who arrived and when, which you can use to issue certificates yourself.

The reply tells you who wants the materials in advance; you send them the way you normally would. You can also say in the invitation where they will find them.

Filter the list to guests without a reply and send the invitation again. It uses the same link, and answers already given are kept.

No. Each guest has a personal link, and the invitation and reply page appear in their language — English, Turkish, German, French or Spanish.

No, there is no per-session capacity. The session answers come out in the export, so you can see the numbers and balance the groups yourself.

No. With door check-in, the attendance export shows who arrived and when, which you can use for your own certificates and records.

Yes. Each trainee has one reply they can change until replies close, and every change is kept.

It is a paid option: included in the plans that have it, or added to a single event. Invitations, replies and exports work without it.

There is no automatic cap. Invite the number of people the room holds, watch the replies, and invite someone new if a place frees up.

Yes. Add your own reply question alongside the suggested one; each answer comes out in its own column of the export.

Usually not. It is a paid option, included in the plans that have it or added to a single event, and useful when the workshop is large or held in a shared building.

Yes. The invitation email and the reply page appear in English, Turkish, German, French or Spanish; the words you wrote stay as you wrote them.

They start switched off, because press and partners are invited by name. Switch them on when the evening calls for it.

Paid places are activated with our team for eligible Agency members, on request. Invitations, replies and check-in work without it.

Yes. Add them to the guest list and only the new guests receive the invitation; nobody already invited gets it twice.

Yes. Each email is followed from queued to delivered and opened, and an address that bounces is suppressed automatically, so the next send does not try it again.

It is a paid option: included in the plans that have it, or added to a single event. Without it you still have every reply and the export.

No. Guests give a table preference and you plan the tables yourself. If your imported list carries a table or section column, door staff see it at check-in.

They start switched off, because gala places are usually counted one by one. Switch them on, one per guest, when the evening welcomes partners.

Paid places are activated with our team for eligible Agency members, on request. Invitations, replies and check-in work without it.

Yes, until replies close. The new answer replaces the old one, the change is kept, and the next export has it.

It is a paid option: included in the plans that have it, or added to a single event.

Plus-ones start switched off for dinners, because places at a table are counted. Switch them on, one per guest, when the evening welcomes partners.

Yes. The suggested questions can be edited, removed or joined by your own — whatever the menu needs. The attendance question is always asked.

Every answer comes out in the replies export as CSV or Excel, one column per question, so each count is one filter away in your spreadsheet.

Rarely. It is a paid option, included in the plans that have it or added to a single event. For a small table, your list is enough.

At a reception people come and go over hours. The suggested question gives the caterer and the door team a sense of the evening; you can reword it or remove it.

Yes. They start switched off; switch them on for everyone or for the guests you choose, and set how many each may bring.

Yes. The door keeps working offline and checks the admissions again once the connection returns.

The reply report counts every state, and with door check-in you also see arrivals by hour, turnout against replies and an attendance export.

Paid places are not something you switch on yourself. They are activated with our team for eligible Agency members, on request.

Venue events vary too much for one set to fit. The attendance question is always asked; add any others your night needs.

They start switched off, so the list is exactly the people invited. Switch them on, one per guest, when the night welcomes company.

Yes, with door check-in. Scanning keeps working offline, and admissions made offline are re-checked once the phone is back online.

It is a paid option: included in the plans that have it, or added to a single event. Without it, check names against your exported list.

No. It collects who each guest would like to meet and puts the answers in the export; your hosts make the introductions.

Yes. Both arrive as required suggested questions; you can make them optional, reword them or remove them.

Filter the list to guests without a reply and send the invitation again. It uses the same link, and answers already given are kept.

Paid places are activated with our team for eligible Agency members, on request. Invitations, replies and check-in work without them.

No. Each guest has their own link, and the guest page shows the details you wrote for the event, not the guest list.

A private event can be almost anything, so it starts with the attendance question only. Add the questions that fit your evening before you send.

A forwarded link still belongs to the guest it was made for, and at the door each code admits once.

No. They open the invitation, reply, and can change their answer from the same link until you close changes.

When none of the other types fits. The invitation, replies, guest list and door work the same way; you simply start without suggested questions.

If one comes close, choose it: it suggests questions for that kind of event. Suggestions are only a start, and you can edit, remove or add any of them.

No. They open the invitation, reply, and can change their answer later from the same link until you close changes.

Yes, on every plan: a CSV or Excel file with every answer, one column per question.

No. Each is written to be useful with any tool, or none. Where Winglark does the thing described, the guide says so at the end and links to the page that shows it.

When the practice changes or the product does. The date on each guide is the date it was last reviewed, not the date it was first published.

A spreadsheet works at any size for storing rows; it stops working the moment two people edit it or the moment it has to be sent from. Somewhere around a few hundred guests, the cleaning and the sending are better done by something that keeps one record per guest.

Mark them, do not remove them. A bounce is a fact about an address on a date, not about a person. Find another address or another channel first.

ListGuard reads every row as it is pasted or uploaded, maps the columns, flags duplicates and addresses that cannot receive mail, and shows you the result before anything reaches the event. Late names go through InvitePulse, which compares them with the guests already invited.

No. A code from the invitation, on a phone or on paper, is all a guest needs. The app, if there is one, is on the staff’s phones.

A scan and a glance at a name takes two or three seconds. The queue is set by how many devices you have at the busiest door in the first hour, not by the scanner.

GatePass gives every guest a QR code carrying an opaque token, runs on any phone, holds the list on the device for when the signal drops, explains a repeated scan on screen with the three choices above, supports several doors with named staff, and feeds the attendance report that names who promised and did not come.

It varies by event and by how well the list was cleaned; a first invitation to a warm list with one reminder typically hears back from most of it. Whatever the rate, the useful number is the gap between yes and attended, measured over your own events.

No. It is a courtesy, which is why the gap exists. Treat it as planning data, not a contract.

Every guest replies from their own link; the reply, plus-ones and the event type’s questions land on the guest record; the latest reply counts and the earlier ones stay; “no answer” is its own state; and the reporting page measures replies against who was scanned at the door, by name.

Email for the invitation, because it carries the design, the calendar entry and the personal link, and because it leaves a record. A messaging channel is fine for the reminder to people you know, with the same personal link.

For a company event, four to six weeks with a reminder at ten days. For anything guests travel to, longer. The reply deadline in the email should be a real date, a week before you need the numbers.

MailFlow sends from your own verified sender and domain and keeps a record per message from queued to delivered, bounced or suppressed. TemplateForge builds the invitation from blocks bound to the event, keeps every published version, and previews the real email before it goes.

Plan for the first forty minutes, when most guests arrive: three devices on the main door for four hundred people is comfortable, one on VIP, one on press. After the peak, one device per door.

The checklist is the same; the roles change. The agency owns the list and the sending, the company approves the invitation and reads the report, and the agency’s staff should see only your event, not their other clients’.

ListGuard cleans the list; TemplateForge and MailFlow build and send the invitation from your verified domain with a delivery record; InvitePulse handles late names; GatePass runs the doors with named staff, offline, with recorded approvals; the reporting page produces the report by name and segment. The for-teams page describes the roles; the security page states where data is processed and what is not in place yet.

No. A web page opened from a QR code reaches more of the room than an app, because nobody has to install anything. What matters is moderation, upvotes and telling askers what happened.

It depends on the room. Anonymous questions bring out the difficult ones; named questions suit internal events. Letting the asker choose often works best.

One attentive person handles most sessions of a few hundred people. For a town hall or a large conference keynote, add a second so the queue never sits unread.

LivePulse runs moderated Q&A from the guest’s phone with no app: nothing reaches the room until the team approves it, guests upvote approved questions once per phone, the question being answered can be pinned, and askers see whether theirs is waiting, shown, answered or not shown. Guests reach it from a QR code in the room or from their own event page, Companion.