Skip to content
CHRONOMANCER
Use case

Run your casual pool without a hundred-person group chat

A hundred names in one thread gets out of hand fast. Give each casual their own link, and let the roster's records show you who you can depend on.

Roster lifecycleCurrent · Allocating
  1. Draft
  2. Requesting
  3. Allocating
  4. Scheduled
  5. Revise
  6. Live
  7. 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.

Seven states · one verb at a timeRevise loops back from Scheduled and Live
Notch gauge11 of 18
Lit · allocatedHalf · reserveGhost · still open
ChronometerStanding by

No request window is open on this page; the chronometer is shown without a time.

Countdown and absolute time,in the tenant's own timezone

Instruments drawn on an example night. This site carries no customer data.

Each casual gets their own link

A shared group chat stops working once the pool is past a dozen or so people. Messages get buried, opt-outs get missed, and nobody can tell who saw the call for a given night. Chronomancer sends each contact a unique signed link by SMS and email. They open it and make their requests, with no app to install, no password and no thread to scroll back through.

  • One signed link per contact per period
  • Casuals don't install an app or log in
  • Opt-outs are respected automatically, per channel

Response tracking shows who never replies

Link opens, requests and non-responses all go on the record. You can see who opens the link and never requests, who requests and then doesn't show, and who turns up reliably without any fuss. Knowing that is what lets you manage a casual pool instead of guessing about it.

  • Response-rate reporting by roster and by contact
  • A reliability score that picks out your dependable people
  • Weighted to recent periods, so one bad run fades over time

From a full pool to a filled roster

STEP 01

Load your pool

Each casual is a contact with their own phone number, email and opt-out preferences.

STEP 02

Publish the period

Publishing sends a personal signed link to each contact by SMS and email.

STEP 03

Watch the responses

See who has opened the link, who has requested and who has gone quiet, as the replies come in.

STEP 04

Nudge the non-responders

Reminders go only to people who haven't replied, and only while the window is open.

STEP 05

Allocate by priority and reliability

Your most dependable people come to the top of a contested night, and the reserve holds the rest.

STEP 06

Let the score sort the next one

Attendance from this period goes into everyone's reliability score for the next.

No logins
FOR CASUALS, IN ANY PERIOD
SMS + email
WITH REPLIES AND STOP OPT-OUTS
Own link
FOR EACH CONTACT, SO NOBODY'S LOST IN A THREAD
What keeps a large casual pool easy to follow.

Questions about casual pools

Do casuals need to install an app to request work?

No. They get a signed link by SMS and email, open it in their phone's browser and make their requests. There's no app, account or password.

How do we know who's reliable in a pool this size?

Reliability is scored automatically each time a period completes, from attendance rate and hours fulfilment. Recent periods count more than older ones, and the result shows as a green, amber or red band.

What happens if someone opts out of SMS?

Opt-out is checked before each send, per channel. A contact who replies STOP stops getting texts at once, and that holds for every future roster.

Can we see who never responds to invites?

Yes. Response-rate reporting shows each roster's funnel (invited, opened, requested) and names the people who didn't respond, so you can follow up or let them drop away.

Get your casual pool off the group chat

Tell us how big your pool is and how you run it now, and we'll go through what it would look like in Chronomancer.