Can it stop double-booking?

Yes. A booking exceeding a resource capacity is rejected, not flagged after saving.

Does it respect leave?

Yes. An employee resource cannot be booked on a day covered by an approved leave request.

Can I see my Outlook or Google calendar alongside?

Yes, connected through OAuth and overlaid in the same view.

Can customers book online?

Yes. A resource can be published to your storefront and booked into the same calendar.

Scheduling & Resources

Softbooq Go

Book people, rooms and equipment without double-booking any of them.

A calendar that knows each resource working hours, refuses a booking that exceeds capacity rather than warning about it, and turns a completed booking into a sale exactly once.

Start Free Trial See pricing

Booking things that have limits

A calendar without capacity is a shared document with colours.

Working hours per weekday, per resource

Each resource carries its own availability by day, so the calendar offers slots that exist rather than a uniform nine to five it will then let you break.

Double-booking refused, not flagged

Overlaps are counted against the resource capacity and rejected when it would be exceeded. A warning you can click past is not a constraint.

Recurring series you can edit forward

Change one occurrence, or this and every following one - which is what actually happens when a weekly slot moves mid-term.

Leave blocks a booking

An employee resource cannot be booked on a day covered by approved leave, because the two systems share the same records.

Outlook and Google overlaid

External commitments shown beside your bookings through OAuth, so nothing is scheduled over something the ERP could not see.

Turning time into money

The reason a scheduler belongs inside an ERP rather than beside one.

Bill a booking as a sale, once

A completed booking becomes a sale and its invoice, and the booking keeps the sale reference - so billing it twice is not possible.

Attendance, no-shows and occupancy

Who turned up, rolled into occupancy and revenue per resource, so you can tell a busy calendar from a profitable one.

Customers book you online

Resources marked available for online booking appear on your public storefront, taking bookings into the same calendar your staff work from.

The details that took the longest

Small decisions you only make after getting them wrong.

Every one of these is a specific behaviour, chosen for a specific reason. They are the difference between software that demos well and software that survives a year of month-ends.

Capacity is enforced, not advised

A booking beyond a resource capacity is rejected outright. Every scheduler warns; the ones that only warn are the ones where two engineers arrive at the same job because somebody clicked through the amber banner.

A booking can only be billed once

The sale reference is written back onto the booking, so the second attempt has something to check against. Without it, the same job gets invoiced twice by two people on the same afternoon.

Nothing is an island

What reaches Scheduling without anyone typing it again.

Every one of these is a real data path, not a promise of "full integration".

Sales

Billing a booking creates the sale and the invoice behind it

Inventory

Bookable services are items, priced from the same list

An employee on approved leave cannot be booked

CRM

Bookings are attached to the customer record

Public Portal

Bookable resources appear in your online shop

Before you ask

Questions people ask about Scheduling.

Can it stop double-booking?: Yes. A booking exceeding a resource capacity is rejected, not flagged after saving.
Does it respect leave?: Yes. An employee resource cannot be booked on a day covered by an approved leave request.
Can I see my Outlook or Google calendar alongside?: Yes, connected through OAuth and overlaid in the same view.
Can customers book online?: Yes. A resource can be published to your storefront and booked into the same calendar.