Skip to content

Winglark

Capabilities

MailFlow

Send invitations under your name — and know what happened to each one.

Every message keeps its own record, from the moment it is queued to the moment it is delivered, opened, bounced or held back — with the reason beside it.

Send, and know what arrived

Folded paper letters travelling along a line of light across a dark green ground.

The problem

Sent is not delivered.

Most invitation tools report one thing: that the message left. Whether it arrived, bounced, reached somebody who asked never to be written to, or was never attempted at all is left for the organiser to find out — usually when a guest says they were never invited.

And the sender matters. An invitation from an address nobody recognises is an invitation that is ignored or filtered away.

Signature scene

Sent is not delivered.

Five messages leave together. One is read, one is delivered and never opened, one bounces, one was never attempted because the address asked not to be written to, one is held for a person. Every one keeps its own record.

Five invented recipients, one batch. The lanes end where the messages actually ended.
  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
The life of one batch of invitations. The figures are the demo event’s.

How it works

How an invitation leaves, and how you know it arrived

  1. 01

    Choose who it comes from

    Send from your own sender and verified domain, or begin with the Winglark address, which shows your company’s name and sends replies to you.

  2. 02

    Check before sending

    A readiness check lists anything that stands between you and sending — a sender to confirm, a domain to verify — before a single message leaves.

  3. 03

    Send a batch

    Invitations leave as a batch for one event and one purpose: the invitation itself, an update, a cancellation, a confirmation.

  4. 04

    Follow every message

    Each message moves from queued to accepted, and then to delivered, opened, bounced, complained or deferred, as the delivery provider reports it.

  5. 05

    Act on what the record says

    Re-send one guest’s invitation, see why a message was held back, and keep addresses that bounced or complained out of future sends.

What is included

What is included

Your sender, your domain
Add senders for invitations, for confirmations or for both, and verify your own domain so that mail leaves under your name.
A ready address from the first day
Until your domain is verified, invitations can leave from the Winglark address, shown as your company via Winglark, with replies going to you.
A record for every message
Queued, accepted, delivered, opened, bounced, complained or deferred — each with its time and its reason.
Signed delivery reports
Delivery updates are accepted only when the provider has signed them, counted once, and never moved backwards.
Suppression that holds
A permanent bounce or a complaint keeps an address out of future sends. A complaint can never be released.
No accidental second send
Every message carries a key that stops the same invitation from being sent twice by a retry or a double click.

Why it matters

What changes on the day

  • You know who has not received it

    Before the event rather than after — so a phone call can fix what an email could not.

  • Your reputation stays yours

    Mail from a verified domain, to addresses that can receive it, is mail that keeps arriving.

  • A no stays a no

    An address that complained is never written to again, by anyone on your team.

Where it is used

Where it earns its place

  1. 01

    A conference with a registration deadline

    See which invitations bounced a week before and reach those people another way.

  2. 02

    A venue’s monthly programme

    Send from the venue’s own domain, so every month’s invitation is recognised.

  3. 03

    A private celebration

    Begin with the Winglark address today, and verify your own domain when it matters.

On each plan

The allowances published for each plan. The full comparison, with prices, is on the pricing page.

Compare all plans

On each plan
WhatStarterProfessionalAgency
Emails sent1,00015,00060,000
Invitations5005,000Unlimited

Questions

Do I need my own email provider?

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.

What does “delivered” mean here?

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.

Can I re-send an invitation?

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

Does it send SMS or WhatsApp?

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.

See it on your own event.

Winglark is in early access. Request access, a person reviews it, and an invitation to your workspace follows.

MailFlow — event invitation email delivery · Winglark