Capabilities
ListGuardFind what is wrong with a guest list before anyone is invited.
Paste it or upload it as it is. Every row is read, corrected where that is safe, questioned where it is not — and nothing reaches an event until you have seen the result.
Clean the list before it costs you
The problem
A bad list is found at the door, unless it is found first.
Guest lists arrive as spreadsheets built by several people over several weeks: the same person twice under two spellings, a phone number without its country, a typo in an email domain, a column called “E-posta” in one tab and “Email” in the next.
Sent as they are, those errors become bounced invitations, duplicate entry codes and a queue at the door while somebody searches for a name that was entered twice. Fixing them by hand means reading every row, and nobody does.
Signature scene
Raw in. Clean out.
The list arrives as it was sent. Every finding is marked where it sits, with the original kept beside it — and what leaves is one list the event can run on.
| 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
How it works
From a raw file to a list an event can use
- 01
Bring the list as it is
Paste from a spreadsheet, or upload CSV, TSV, text or Excel. The file type is read from its contents, you choose the sheet, broken character encodings are repaired, and cells that start like a spreadsheet formula are neutralised.
- 02
Columns are recognised
Headers in English, Turkish, German, French or Spanish are matched to nineteen guest fields — names, email, phone, company, title, guest type, plus-ones, group, language and your own references. Two columns claiming the same field are refused rather than merged.
- 03
Every row is checked
Names, email addresses and phone numbers are normalised, with the original kept beside every proposed change. Addresses are checked for syntax, disposable and role addresses, and whether the domain can receive mail at all.
- 04
Duplicates and existing guests are found
Exact matches on email, phone or reference, and likely ones — a similar name at the same company, the same number written differently, an address one typo away. Rows that match somebody already on the event are marked as such.
- 05
You decide, then commit
Each row is usable, needs review or is rejected, always with the reason. Correct a row, decide it, or accept every safe correction at once — then save the result as a list, add it to one, or import it into an event. Until then it can be discarded without a trace.
What is included
What the check does
- Column matching in five languages
- A list built in Istanbul and a list built in Berlin arrive in the same shape, whatever the headers were called.
- Normalisation you can see
- Phone numbers become full international numbers, and an assumed country code is flagged rather than hidden. The source value never disappears.
- Honest email checks
- Syntax, disposable domains, role addresses and whether the domain accepts mail. A domain that cannot be checked sends the row to review; a mailbox is never claimed to be real.
- Duplicates, exact and likely
- Clear duplicates are separated from possible ones, so the only decisions left for a person are the ones that need one.
- Saved lists
- Keep a clean list for the next event: rename it, archive it, edit a member under the same rules, and filter by clean, missing, duplicate or risky entries.
- Contact details kept private
- Email addresses and phone numbers are masked for team members who are not allowed to see them.
Why it matters
What changes on the day
Fewer bounced invitations
Addresses that cannot receive mail are caught before sending — which also protects the reputation of the address you send from.
One code per person
A guest entered twice receives one invitation and one entry code, so the door never has to decide which one is real.
A list the team can trust
Every change is visible and every rejection has a reason, so nobody re-checks the spreadsheet in the week of the event.
How it connects to the rest of Winglark
- InvitePulseAdd guests after it has gone outNames that arrive after the invitations went out go through the same matching, against the guests already on the event.
- MailFlowSend, and know what arrivedA clean list is what makes delivery reliable: fewer bounces, and addresses that must not be written to kept out.
- Event typesThe guest fields an event type asks for are the fields a list is mapped onto.
Where it is used
Where it earns its place
- 01
A gala built from three departments’ spreadsheets
Merge the lists, see who appears in all three, and invite each person once.
- 02
A wedding list typed by two families
Two spellings of the same aunt become one guest — with the choice left to you.
- 03
A conference that returns every year
Last year’s attendees become a saved list, cleaned once and used again.
On each plan
The allowances published for each plan. The full comparison, with prices, is on the pricing page.
Questions
Does it confirm that an email address really exists?
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.
Will it change my data without asking?
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.
How large can a list be?
One upload can be up to 8 MB and 10,000 rows. A larger list can be brought in several parts.
Can I undo an import?
Before it is committed, an import can be discarded completely. After it is committed, guests can be archived and restored one at a time.
See it on your own event.
Winglark is in early access. Request access, a person reviews it, and an invitation to your workspace follows.