01 · The problem
A vote is one click wide.
A poll counts whoever happened to see it, which is exactly right for lunch and useless for the on-call rota. The moment the question is who is covering, who has actually confirmed, you need every named person's answer — and a tick has nowhere to put the condition that came with it. Read the four answers this poll had no way to record.
02 · What you need
Every answer, condition attached.
Slack settles a plain vote without us — reactions, Workflow Builder, a poll app, all fine. This kind you have to go and ask for, one person at a time, then hold four half-answers in your head while you work out which of them actually conflict. Ask them yourself and watch the morning go.
03 · How it runs
Someone has to go and ask each person. That's the job.
Set where the asking happens and what an answer gets checked against. Every step below rewrites itself to match, because the surface changes the words, never the work — and where a surface genuinely can't do something, it says so instead of quietly skipping it.
04 · Your numbers
You publish the rota with nobody assumed into it.
A rota built on nine of fifteen answers isn't part-right, it's wrong — the six you assumed into it are exactly where it breaks, on the Friday nobody agreed to cover. Move the sliders to your own team and read what the asking actually costs you.