Every send is a record
SwimWin does not send an email and forget it. Every message is a row: who it was for, which message it was, when it went, and what the provider said happened to it afterwards — delivered, bounced, complained.
That ledger is the answer to "we never got it", which is otherwise an argument nobody can win. See A family says the email never arrived.
Emails carry your club's branding
Transactional mail is sent per club, with the club's name, colour and wordmark — not SwimWin's. A family gets mail from their club.
What sends today
Registration received — the receipt a family gets after using the join form.
That is the honest list. One.
What is still to come
The rest of the Phase 1 transactional set:
- Invitation to set a password
- Waitlist offer, reminder and expiry
- Registration approved and registration declined
- Waiver needed
- Payment receipt and payment failed
- Membership activated
Until they land, telling the family is a manual step. Build it into your process: when you approve a registration, email them. When you make a waitlist offer, tell them. The screens will not do it for you yet.
Broadcasts are a different thing
Club-wide and per-squad announcements — the "practice is cancelled" message
sent to a chosen group — are a separate capability (send_broadcasts, held by
the owner, club admin and head coach) and are coming soon. The delivery
ledger was deliberately built first so that broadcasts inherit it rather than
inventing a second one.
For something urgent today, a site alert is the tool that exists: one banner, everybody who opens anything.
SMS
The plumbing is there for a second channel. Nothing sends over it yet.