Timeslots.io

Collect availability for one meeting

Pick a timezone and a few slots, then send a test link and confirm how participants enter their name and see the overlap.

What it’s useful for

Timeslots keeps the first step small: pick candidate days and a meeting length. The official FAQ describes a shared heatmap, participant timezone switching and optional protection for response edits. It is a group-availability tool rather than a confirmed-appointment service.

Inside the product

• Choose days, meeting length and an event timezone before sharing a link.
• Participants answer by name without an account, according to the official FAQ.
• A response-editing password is optional; organizers receive a private management link.

Good to know

• Names are not authenticated identities. The FAQ recommends a password to prevent another person editing under the same name.
• The organizer’s management link is shown once and should be retained.
• The launch post names Claude Code, but its pseudonymous author was not independently linked to the website owner. Calendar sync and invitations were not verified.

The maker’s build notes

An original launch post links timeslots.io and says it was built with Claude Code, Next.js and Postgres. The live site credits Harry Wang. These are attributed public accounts; we have not independently established that the posting account and named owner are the same person.

A few more details

Sources & maker notes

Build details come from the maker’s linked account. vibeforthat has not independently audited the code or tested every product function.

• Timeslots — original maker launch post
• Timeslots product and FAQ