Open Bookings, then a booking page, to find the settings. Availability lives on the Availability tab and calendar choices on the Calendar tab.
Set when people can book
On the Availability tab you can set:
- Weekly hours - the days and time windows you are bookable.
- Date overrides - close a specific day or give it different hours.
- Scheduling rules - Slot every (min), Buffer before (min), Buffer after (min), Min notice (min), and Book up to (days out).
- Limits - Max bookings / day, Max bookings / week, and Max bookings / month, counted as a calendar period or a rolling window.
Pick your Your timezone on the Details tab. Invitees see times in their own time zone. Choose Save changes when you are done.
Connect a calendar
On the Bookings page, open Edit availability and calendars to reach Calendars:
- Connect Google Calendar - Formspring reads your busy times and writes confirmed bookings back to the calendar.
- Add feed - add a read-only iCal feed URL (with an optional label). Busy times are read from it, but nothing is written back.
A calendar marked Reconnect needed has lost access; reconnect it, or availability may stop. Use Disconnect to remove one.
On a booking page's Calendar tab you can choose which connected calendar to check, and optionally write events to several destination calendars.
How double bookings are prevented
- Times when you are busy on the connected calendar are never offered.
- Times that already have a confirmed or pending appointment on the page are removed.
- At the moment someone books, Formspring checks the slot again, so two people cannot take the same time even if they click together.
Team scheduling: hosts and routing
Open a page's Hosts & routing tab to share a page between people. Pick the kind of meeting (each option is explained under the picker):
| Kind | What happens |
|---|---|
| One host | One person takes every meeting. |
| Round robin | Each booking goes to the free host with the lowest load for their weight. The event is written to that host's own calendar. |
| Collective | Every required host attends. Invitees only see times when all of them are free. |
| Managed | Qualification rules send the booking to a host pool. |
Set Seats per time slot above 1 to make a group event: several invitees share one slot until the seats are gone.
For a collective meeting:
- Hosts without a pool always attend. Hosts that share a pool name rotate, and one member of each pool attends, chosen by lowest load.
- Tick Organizer on one host. The organizer owns the booking and the calendar event, and the other hosts are invited to it. Without a choice, the highest-priority host organizes.
- The meeting blocks every required host on all of their other booking pages, and it stays that way after a reschedule or for every occurrence of a recurring series.
- The video provider is chosen once per page under Details (meeting location).
Daily and weekly host limits count confirmed and pending bookings across all your pages, so an
open approval already uses up its place. Host limits, pools, the organizer, routing rules and the
fallback message can also be managed through the API (/bookings/pages/{page}/routing) and the
update_booking_routing MCP tool.
Route on what you know about the invitee
Routing rules read the invitee's booking answers and values the server knows. Turn on Also
route on the invitee's contact record to also read account_owner, lead_score, language,
country and territory from the contact with the same email in your workspace. Enable it only
when a system you trust writes those attributes: values a visitor can set themselves can be used
to steer their own route. The facts never travel in the page address.
If your calendar cannot be read
Formspring fails safe. If your calendar cannot be reached (for example the connection expired), the booking page offers no times at all and shows "Availability could not be loaded" with a Try again button. Nothing is booked. This is deliberate, so nobody is offered a time that clashes with a real event. Reconnect your calendar to restore your slots.
The page also never confirms a booking on an old answer: at the moment of booking, and when someone reschedules, Formspring reads your calendar again. A change in your calendar is picked up within the refresh time (five minutes by default) or immediately when the provider sends a change notification. Read-only iCal feeds are refreshed on a schedule and have no instant notification, so a change there can take a few minutes to appear.