SMS rostering that replaces the login with a link
Bidding, confirmations, reminders and dropout claims all travel by two-way SMS and email. Every message is a unique signed link, not a login screen, and every send is tracked, threaded per person, and STOP-compliant.
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- Completed
Allocating. Requests are in and seats are being filled. Every roster sits at exactly one station, and each station names the one thing left to do.
No request window is open on this page; the chronometer is shown without a time.
Instruments drawn on an example night. This site carries no customer data.
A signed link instead of a password
Every bid invite, reminder, confirmation and dropout claim carries a fresh, signed link scoped to one contact and one purpose. There's no account to set up and no password to reset — opening the link is the whole interaction. Links expire on schedule, so an old bid invite can't be replayed once the window it belonged to has closed.
- One signed link per contact per period, no password anywhere
- Links expire at bid close and are rotated each period
- Every click logged: device, browser, and a fingerprint check
- An unfamiliar device on a known link flags for admin review
No request window is open on this page; the chronometer is shown without a time.
Templated per venue, per event, per channel
Invite, reminder, confirmation and claim messages are templated separately for SMS and email, and separately per organisation — so your wording, your sender identity, and your brand voice are what your crew actually see. Variables like the person's name, the venue, the period and the link drop in automatically at send time.
- Separate templates per organisation, per event, per channel
- Variable substitution for name, venue, period and link
- Per-venue sender identity — your crew never see a generic sender
- Reminders and confirmations are enqueued and sent automatically
Delivery tracking and STOP opt-out, on every send
Every message sits in one thread per contact, moving through pending, sending, sent, delivered or failed — so a failed send is visible immediately instead of quietly vanishing. Replying STOP to any SMS flips that person's opt-out flag straight away, and it's checked before every subsequent send, not just at signup.
- One threaded conversation per contact, across SMS and email
- Delivery status tracked through to delivered or failed
- STOP opt-out checked before every enqueue and every send
- Failed sends surface on your dashboard's needs-attention feed
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- Completed
Allocating. Requests are in and seats are being filled. Every roster sits at exactly one station, and each station names the one thing left to do.
Questions about communications
Do staff need to download anything to receive their link?
No. Links arrive by ordinary SMS and email — staff just tap the link that's already scoped to them for the current period.
What happens if someone texts STOP?
Their opt-out flag is set immediately from the inbound message, and it's checked before every future send, both when a message is queued and again right before it goes out.
Can our venue use its own wording and sender identity?
Yes — templates for invites, reminders, confirmations and claims are configured per organisation and per channel, and sends go out under your own sender identity, not a shared one.
How do we know if a message actually got delivered?
Every message is tracked through pending, sending, sent, delivered or failed, threaded per contact, so recent failures are visible and linked straight to that person's message thread.
Is SMS reliable enough for time-sensitive things like dropout claims?
Yes — claim links, confirmations and reminders all go through the same tracked send-and-retry queue as everything else, so a failed attempt is retried rather than silently dropped.
See your own templates in action
Tell us about your venue and your crew — we'll show you what your invites and confirmations would look like.