Shift messages that replace the login with a link
Request links, confirmations, reminders and standby offers go out by SMS and email. Each one carries a signed personal link instead of a login screen. Sends are tracked and kept on the person's record, and a STOP reply is honoured.
- 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
Request invites, reminders, confirmations and standby offers each carry a signed link for one person and one purpose. Nobody sets up an account or resets a password; opening the link is all they do. Links expire on schedule, so an old invite stops working once its window has closed.
- One signed link per contact per period, and no passwords
- Links expire when requests close and are replaced each period
- Clicks are logged with device, browser and a fingerprint check
- An unfamiliar device on a known link is flagged for admin review
No request window is open on this page; the chronometer is shown without a time.
Templates per venue, per event and per channel
Invite, reminder, confirmation and claim messages each have their own SMS and email templates, set separately for each organisation, so your crew reads your wording. The person's name, the venue, the period and the link are filled in when the message is sent.
- Separate templates per organisation, per event, per channel
- Placeholders for name, venue, period and link
- Each message names your venue, in your words
- Sends go through one tracked queue, with retries
Delivery tracking and STOP opt-out on each send
Messages sit on the person's record and move through pending, sending, sent, delivered or failed, so you can see a failed send instead of wondering where it went. SMS is two-way. A reply to a text lands on the same record, and a STOP reply sets that person's opt-out at once. The opt-out is checked before each later send, not only at signup.
- Each person's messages in one place, by channel
- Delivery status tracked through to delivered or failed
- STOP opt-out checked when a message is queued and again when it's sent
- Failed sends show up in 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 text message and email, and the link is already tied to that person for the current period. They tap it and they're in.
What happens if someone texts STOP?
Their opt-out is set as soon as the STOP arrives. It's checked before each later send: once when a message is queued and again just before it goes out.
Can our venue use its own wording?
Yes. Templates for invites, reminders, confirmations and standby offers are set per organisation and per channel, and each message names your venue. Texts can also come from a sender set up for your organisation.
How do we know a message was delivered?
Each message is tracked through pending, sending, sent, delivered or failed, and threaded per contact. Recent failures are listed with a link to that person's message thread.
Will standby offers go out by SMS?
Yes, by SMS and email. Claim links, confirmations and reminders use the same tracked queue as other messages, so a failed attempt is retried rather than dropped.
See your messages in your own words
Send us a few details about your venue and we'll show you what your invites and confirmations would look like.