What stops fake requests
Checks that people don’t notice, and decisions that your team makes.
Send a request through the checks
Pick a request and see how far it gets. Real ones pass, fake ones stop at their check.
It passes every check and lands in “Requests”. A staff member approves or declines it, and the decision reaches the person by e-mail.
What each check does
The first four work on their own. The last two leave the decision to your team.
- A bot check, no puzzlesThe form checks that a person is on the other side, without making them solve puzzles or type distorted letters.
- Too many, too fast — it stopsSeries of requests from one place in a short time are slowed down, without getting in anyone else’s way.
- The e-mail is confirmed with a codeBefore the first request the person enters a code from their e-mail. The browser remembers the confirmation, so the next requests go through without a code.
- Only a few upcoming slots per personOne person can hold only a few upcoming slots at one place or specialist. You decide how many. For a new one they wait for one to pass or cancel an old one with the link in the e-mail.
- Suspicious cases are flagged, not blockedThe system flags unusual cases: many e-mails from one place, series of requests, mostly refusals. Your team decides. Nothing is blocked automatically.
- Your team can blockAn e-mail address stays blocked until you unblock it, an IP address for a while. The open requests of whoever is blocked are declined. Once a day a short summary arrives, if there are new cases.
What your team sees
The system sorts and flags. You decide.
- A “Requesters” page: who has made requests, how many times and what decisions they got.
- Suspicious cases, grouped by connected e-mails and addresses — for review, not for automatic action.
- Blocking an e-mail, or an IP address for a while. Before that you see which requests will be declined, and the action stays in the log.
- In a private system IP addresses are neither shown nor blocked — the network is already limited.
Three questions on the topic
What stops fake requests?
The form checks for bots, and the e-mail is confirmed with a code. One person can hold only a few upcoming slots at one place or specialist. Suspicious cases are flagged, but nothing is blocked automatically — your team decides, can block an e-mail or an IP address for a while, and gets a short summary once a day.
Do people need an account?
No. A name, an e-mail and a phone number are enough, and the e-mail is confirmed with a code — once per browser. The decision arrives by e-mail. If plans change, people cancel themselves with the link in the e-mail.
Can people cancel themselves?
Yes. Every e-mail about the request has a cancel link, valid until the slot begins. The cancellation shows in your team’s list.