Appointment operations, without the drag

Your day,
perfectly slotted.

SlotWise brings bookings, customers, and staff schedules into one considered workspace — so service businesses can spend less time arranging the day and more time running it.

No double-bookingsTime-zone honestBuilt for one business

Salons · Studios · Repair shops · Consultants

Everything in its place

Run the day without running around.

Every screen is built around the same question: what does the day look like now, and what needs attention next?

A calendar that reads at a glance

Day, week, and month views with clear status colours, staff filters, and a mobile agenda. Your schedule should answer questions, not raise them.

Double-bookings are structurally impossible

Overlap protection lives in PostgreSQL, not a hopeful client check. Concurrent requests for the same slot end with exactly one booking.

Availability that tells the truth

Working hours, recorded time off, service duration, and past-time rules shape every offered slot — all in your business time zone.

Reports made from real visits

Revenue comes from completed appointment snapshots, so catalogue edits never rewrite history. Filter by date and export a safe CSV.

Times are displayed and validated in your configured business time zone.Every metric on your dashboard comes from your own database records.

A considered workflow

Set up once.
Run it daily.

No operational maze. Shape your business, then let the calendar carry the day.

Create your workspace
  1. 01

    Shape your catalogue

    Add the services you offer, their durations and prices, and the people who deliver them.

  2. 02

    Map the working week

    Set one clear interval per weekday and record time off. Availability updates the moment you save.

  3. 03

    Book, run, and review

    Create bookings from the calendar, move them through a considered status flow, and let the reports add up.

Guardrails, not good intentions

Your business rules, enforced below the UI.

SlotWise treats the database as the last line of defence. Even a crafted request cannot write around the booking rules.

  • Row-level security on every business table
  • Appointment writes locked behind security-definer functions
  • Tenant-safe composite foreign keys across every reference
  • Immutable service snapshots on each booking
appointments_no_overlap
-- The database has the final say
alter table appointments
add constraint appointments_no_overlap
exclude using gist (
  user_id with =,
  staff_id with =,
  tstzrange(start_at, end_at, '[)') with &&
)
where status in (
  'pending', 'confirmed', 'in_progress'
);
Cancelled slots free upBack-to-back is allowedConcurrent writes resolve safelyOwnership validated twice

Ready when you are

Give every hour a home.

Set up your business in minutes. Bring your services, your team, and your calendar into one clear place.