The texts Kadim sends
Every text Kadim can send, listed once. Tokens in braces, like {title}, are
filled in when the text goes out. Every text is kept to a single short message
wherever it can be.
Dates and times are written the way people say them, in UK time: Friday 3 July, and 1:15pm rather than 13:15. On the hour, it just says 1pm.
{link} is always a full web address, like https://www.kadim.co.uk/r/…, so
the phone turns it into something you can tap. It is the same address a
coordinator copies or shares on WhatsApp, so a link forwarded from a text and a
link shared from the rota page go to exactly the same place.
Every text about a duty you hold carries a link too, so you can act on it from the phone it lands on. It opens the roster for that duty, where you can see your slot and step back if you cannot make it. A private duty you accepted from an invitation opens your invitation instead, because a private roster has no public page.
A web address is long, though, and the texts that carry one are the longest Kadim sends. They may arrive as two or three messages joined together rather than one, especially in Arabic. That is normal, costs a little more to send, and changes nothing you have to do.
Everyday texts
| Text | What it says | When it's sent | Who gets it | What stops it |
|---|---|---|---|---|
| Sign-in code | Your Kadim verification code is {code}. It expires in {minutes} minutes. Never share it. |
You claim or sign in on a new device | The person signing in | Nothing to stop: it is only sent when you ask to sign in |
| Rota shared | Kadim: the {title} rota for Friday 3 July is ready. Pick your slots: {link} |
A coordinator texts the team a rota | Team volunteers with a mobile on record | Leaving the team |
| Skill call-out | Kadim: {title} needs help with {skill}. Details and sign up: {link} |
A coordinator posts a call-out for a skill | Volunteers who declared that skill | Leaving the team |
| Gap alert | Kadim: {role} on Friday 3 July 1:15pm reopened, unfilled. {link} |
A slot reopens close to the day | Your mosque's coordinators, one text each, never the volunteer team | Stepping down as a coordinator |
| Slot reminder | Kadim reminder: {role} at {title}, Friday 3 July at 1:15pm. {link} |
The day before a slot you hold | The volunteer who holds the slot | Releasing the slot |
| Duty assigned | Kadim: you are on {duty} at {title}, arrive by 1:15pm. Can't make it? {link} |
A coordinator assigns you a duty on the board | The assigned volunteer | Leaving the team |
| Slot time changed | Kadim: {role} at {title} now starts Friday 3 July at 1:15pm. {link} |
A coordinator changes the time of a slot you hold | The volunteers holding that slot | Releasing the slot, or leaving the team |
| Taken off a slot | Kadim: your coordinator has taken you off the {role} slot at {title} on Friday 3 July. |
A coordinator removes you from a slot | The volunteer removed | Releasing the slot, or leaving the team |
| Moved to another slot | Kadim: you are now {role} at {title}, Friday 3 July at 1:15pm. {link} |
A coordinator moves you to a different slot | The volunteer moved | Releasing the slot, or leaving the team |
| Rota cancelled | Kadim: {title} on Friday 3 July has been cancelled. You do not need to attend. Thank you. |
A coordinator cancels the whole rota | Everyone who claimed a slot | Releasing the slot, or leaving the team |
| Rota re-timed | Kadim: {title} on Friday 3 July now starts at 1:15pm. |
A coordinator changes the whole rota's time | Everyone who claimed a slot | Releasing the slot, or leaving the team |
| Rota digest | Kadim: {count} rotas published automatically: {summary}. Share them: {link} |
A standing schedule publishes due rotas (once a day) | The coordinator only | Pausing the standing schedule |
| Team thanks | JazakAllahu khairan for serving at {title}, from your coordinator and the whole team. |
A coordinator taps Thank the team | Everyone who served the rota | Leaving the team |
| DBS renewal reminder | Kadim: {name}, your DBS check expires soon. Please renew it so you can keep serving. Your safeguarding lead can help. |
A trustee sends a reminder from the compliance dashboard | The person whose check is expiring | A trustee sends this by hand, so ask the trustee |
A team-thanks text carries one extra private line when the person reaches a milestone (their tenth, twenty-fifth, fiftieth or hundredth time serving). It rides the same message; no extra text is sent.
The five middle rows, from Slot time changed to Rota re-timed, are courtesy texts: Kadim sends them only because a coordinator changed something about a slot you are actually holding. That is why two different things stop them. Releasing the slot is the direct one, because the text is addressed to whoever holds it; leaving the team stops them too, because Kadim only texts people who are still on the team. Either is enough on its own.
Note that this is not the same as the Slot reminder above, which only listens to the slot. A reminder is prepared when you claim, with your number copied onto it at that moment, so leaving the team does not call it back; releasing the slot is what silences it.
How to stop the texts
Kadim sends from the name Kadim rather than from a phone number. Sender names are one way only, so replying to a Kadim text reaches nobody and replying STOP does nothing at all.
What works is asking a coordinator to take you off the team and to release any slots you still hold, which is exactly what the last column above describes. See Stop the texts.
Two confirmations that are built but cannot be sent yet
Kadim can already recognise a texted STOP or START and act on it. Nothing can reach that machinery while the texts come from a sender name, so neither of the confirmations below is sendable today. They are listed for completeness, and they will start working if Kadim ever sends from a phone number that can receive a reply.
| Text | What it says | When it would be sent |
|---|---|---|
| Stop confirmed | You will not get any more texts from Kadim. Reply START if you change your mind. | You reply STOP |
| Start confirmed | Kadim texts are back on. Reply STOP at any time to stop them again. | You reply START |
Sign-in codes and safeguarding reminders are protected
Sign-in codes and DBS reminders travel on a reserved path, kept apart from routine broadcasts and reminders. A burst of ordinary texts can never crowd out or delay a sign-in code or a safeguarding reminder.