Loading Slotwise

Scheduling for solo professionals

Share one link. Invitees see only real openings in their own timezone, and the database makes double-booking impossible — even when two people click at the same moment.

Start scheduling free

No credit card required · Your invitees never sign up

Your month, once clients start booking.

How it works

Three steps, then it runs itself.

  1. Step 1

    Set the hours you actually have

    Weekly working hours, buffers before and after meetings, and one-off blocks for the days you're away.

    Mon
    9–5
    Tue
    9–5
    Wed
    9–5Focus
    Thu
    9–5
    Fri
    Unavailable
    15 min buffer · saved
  2. Step 2

    Share one link

    Your booking page lives at slotwise.app/your-name. No account needed for the people booking you.

    slotwise.app/you
    Email
    Message
    Website
  3. Step 3

    Get booked, not double-booked

    Invitees pick from valid slots only, in their own timezone, and the database refuses overlapping holds.

    1:00
    2:00Booked
    3:00
    PPriya2:00 PM
    DDele2:00 PM
    Conflict prevented
    Synced

Reliability

Two people. One slot. One winner.

Most schedulers check availability in application code, which leaves a gap between the check and the write. Slotwise closes it in the database: a Postgres exclusion constraint rejects any overlapping confirmed booking, so the race is settled by the storage engine.

The person who loses the race sees “That time is no longer available” — never a silent conflict you discover on the call.

Enforced in Postgres

exclude using gist (
  host_id   with =,
  busy_range with &&
) where (status = 'confirmed')
  • Timezone math handled with explicit UTC instants
  • Buffers applied before and after every meeting
  • Daylight-saving transitions covered by tests

Features

Everything a solo practice needs. Nothing it doesn’t.

2:00 PMPriya booked firstConfirmed
2:00 PMDele, same momentUnavailable
Settled in Postgres, not the app

Double-booking prevention

Enforced by a Postgres exclusion constraint, not a hopeful application check. Two simultaneous bookings cannot both win — the storage engine settles the race, not the request that happened to arrive first.

Weekly hoursActive
Client hours · 9:00–5:00
15 min buffer, both sides
Focus time · 2:00–4:00
Client hours · 9:00–5:00
15 min buffer, both sides
Focus time · 2:00–4:00

Availability that respects reality

Recurring weekly hours with buffer time on both sides, plus one-off blocks for vacations and focus days.

Your booking pageLive and shareable
slotwise.app/adaCopy

No account needed for the people booking you.

Copied to clipboard

Share it anywhere — email, text, your own site.

A booking page worth sharing

Only open slots, converted to the visitor's timezone.

Booking confirmedStrategy call · Tue 2:00 PM
invite.ics attached

Calendar invite sent to both sides.

Reminder scheduled

Sends automatically 24h before the call.

Confirmations and reminders

A calendar attachment on booking, then a reminder 24 hours before.

Today3 booked
9:00Marcus ReedNew
11:30Ada RossRepeat
2:00Priya NairNew
9:00Marcus ReedNew
11:30Ada RossRepeat
2:00Priya NairNew

A dashboard for the day ahead

Upcoming and past bookings with invitee names, emails, and notes — without digging through your inbox.

Fri, 10:00 AMwith Jordan Lee
Mon, 2:00 PMwith Sam Ortiz
RescheduleCancel

Self-serve cancellations

Cancel and reschedule links travel with every email, so changes don't turn into another thread.